From: "Rob Herring (Arm)" <robh@kernel.org>
To: Shubham Patil <shubhamsanjay.patil@amd.com>
Cc: Frank.Li@nxp.com, devicetree@vger.kernel.org,
radhey.shyam.pandey@amd.com, alexandre.belloni@bootlin.com,
conor+dt@kernel.org, krzk+dt@kernel.org,
linux-i3c@lists.infradead.org, michal.simek@amd.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: i3c: dw: Document missing optional core reset
Date: Wed, 22 Jul 2026 14:57:40 -0500 [thread overview]
Message-ID: <178475025970.1687978.1532465859692058077.robh@kernel.org> (raw)
In-Reply-To: <20260720073510.1869623-2-shubhamsanjay.patil@amd.com>
On Mon, 20 Jul 2026 13:05:09 +0530, Shubham Patil wrote:
> The DesignWare I3C master IP supports a core reset input, but the
> binding is missing the corresponding reset description.
>
> Document the optional reset property. Keep it optional because the
> reset line is integration-specific.
>
> Signed-off-by: Shubham Patil <shubhamsanjay.patil@amd.com>
> ---
> Changes in v2:
> - Updated commit description
> - Dropped reset-name from the binding
> ---
> Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2026-07-22 19:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 7:35 [PATCH v2 0/2] i3c: dw: Document optional core reset and drop redundant name Shubham Patil
2026-07-20 7:35 ` [PATCH v2 1/2] dt-bindings: i3c: dw: Document missing optional core reset Shubham Patil
2026-07-20 7:42 ` Pandey, Radhey Shyam
2026-07-20 7:43 ` sashiko-bot
2026-07-20 15:42 ` Frank Li
2026-07-22 19:57 ` Rob Herring (Arm) [this message]
2026-07-20 7:35 ` [PATCH v2 2/2] i3c: master: dw: Drop redundant core reset name Shubham Patil
2026-07-20 7:41 ` Pandey, Radhey Shyam
2026-07-20 7:45 ` sashiko-bot
2026-07-20 15:43 ` Frank Li
2026-07-30 14:33 ` [PATCH v2 0/2] i3c: dw: Document optional core reset and drop redundant name Alexandre Belloni
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=178475025970.1687978.1532465859692058077.robh@kernel.org \
--to=robh@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=radhey.shyam.pandey@amd.com \
--cc=shubhamsanjay.patil@amd.com \
/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