From: Krzysztof Kozlowski <krzk@kernel.org>
To: dongxuyang@eswincomputing.com, p.zabel@pengutronix.de,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: ningyu@eswincomputing.com, linmin@eswincomputing.com,
huangyifeng@eswincomputing.com, pinkesh.vaghela@einfochips.com
Subject: Re: [PATCH v4 0/2] Add driver support for ESWIN eic7700 SoC reset controller
Date: Tue, 15 Jul 2025 17:47:04 +0200 [thread overview]
Message-ID: <56192a5d-406a-494a-9f32-409e2c1d69bc@kernel.org> (raw)
In-Reply-To: <20250715121427.1466-1-dongxuyang@eswincomputing.com>
On 15/07/2025 14:14, dongxuyang@eswincomputing.com wrote:
> From: Xuyang Dong <dongxuyang@eswincomputing.com>
>
> Updates:
>
> dt-bindings: reset: eswin: Documentation for eic7700 SoC
> v3 -> v4:
> 1. Remove register offsets in dt-bindings.
> 2. Changed the const value of "#reset-cells" from 2 to 1.
> Because the offsets were removed from dt-bindings. There are
> only IDs. And removed the description of it.
> 3. Modify copyright year from 2024 to 2025.
> 4. Redefined the IDs in the dt-bindings and used these to build a
> reset array in reset driver. Ensure that the reset register and
> reset value corresponding to the IDs are correct.
> Link to v3: https://lore.kernel.org/all/20250624103212.287-1-dongxuyang@eswincomputing.com/
This leads to clock patchset, not reset.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-07-15 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 12:14 dongxuyang
2025-07-15 12:15 ` [PATCH v4 1/2] dt-bindings: reset: eswin: Documentation for eic7700 SoC dongxuyang
2025-07-15 15:49 ` Krzysztof Kozlowski
2025-07-15 12:15 ` [PATCH v4 2/2] reset: eswin: Add eic7700 reset driver dongxuyang
2025-07-15 13:37 ` Philipp Zabel
2025-07-15 15:47 ` Krzysztof Kozlowski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56192a5d-406a-494a-9f32-409e2c1d69bc@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dongxuyang@eswincomputing.com \
--cc=huangyifeng@eswincomputing.com \
--cc=krzk+dt@kernel.org \
--cc=linmin@eswincomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ningyu@eswincomputing.com \
--cc=p.zabel@pengutronix.de \
--cc=pinkesh.vaghela@einfochips.com \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®