From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: MarshallZhan-wiwynn <marshall_zhan@wiwynn.com>,
patrick@stwcx.xyz, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH dev 6.6 v3] ARM: dts: aspeed: yosemite4: add I3C config in DTS
Date: Mon, 17 Feb 2025 11:14:56 +1030 [thread overview]
Message-ID: <24d2d411365004f11498777501da54d6a9c6e758.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20250214011556.1891113-1-marshall_zhan@wiwynn.com>
Hi Marshall,
On Fri, 2025-02-14 at 09:15 +0800, MarshallZhan-wiwynn wrote:
> Set I3C config in yosemite4 DTS.
>
> Test plan:
> Tested pass with aspeed I3C patches and I3C hub driver.
Can you please expand the commit message to provide details? This
statement is quite vague, and I don't find it terribly helpful as it
stands. Which aspeed patches? What tests?
>
> Signed-off-by: MarshallZhan-wiwynn <marshall_zhan@wiwynn.com>
> ---
> .../aspeed/aspeed-bmc-facebook-yosemite4.dts | 88
> +++++++++++++++++++
> 1 file changed, 88 insertions(+)
>
> diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-
> yosemite4.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-
> yosemite4.dts
> index ab4904cf2c0e..3f98e67674d0 100644
> --- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite4.dts
> +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite4.dts
> @@ -1317,6 +1317,94 @@ eeprom@50 {
> };
> };
>
>
...
> &adc0 {
> status = "okay";
> pinctrl-0 = <&pinctrl_adc0_default &pinctrl_adc1_default
> --
> 2.25.1
>
> WIWYNN PROPRIETARY
> This email (and any attachments) contains proprietary or confidential
> information and is for the sole use of its intended recipient. Any
> unauthorized review, use, copying or distribution of this email or
> the content of this email is strictly prohibited. If you are not the
> intended recipient, please notify the sender and delete this email
> immediately.
Please avoid including these confidentiality clauses:
https://subspace.kernel.org/etiquette.html#do-not-include-confidentiality-disclaimers
Andrew
next prev parent reply other threads:[~2025-02-17 0:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 1:15 [PATCH dev 6.6 v3] ARM: dts: aspeed: yosemite4: add I3C config in DTS MarshallZhan-wiwynn
2025-02-17 0:44 ` Andrew Jeffery [this message]
2025-02-17 1:01 ` Andrew Jeffery
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=24d2d411365004f11498777501da54d6a9c6e758.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marshall_zhan@wiwynn.com \
--cc=patrick@stwcx.xyz \
--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