From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Delphine CC Chiu <Delphine_CC_Chiu@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 v1 1/2] Revise mux and hardware in yosemite4 dts
Date: Fri, 26 Apr 2024 10:21:45 +0930 [thread overview]
Message-ID: <f355ad1adb96cd8398c4ac81d1c72df289a2aaf0.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20240425060626.2558515-2-Delphine_CC_Chiu@wiwynn.com>
On Thu, 2024-04-25 at 14:06 +0800, Delphine CC Chiu wrote:
> ARM: dts: aspeed: yosemite4:
This should be in the patch subject, not the body of the commit
message.
> Change hardware configuration, consequently modifying the mux in the dts.
Perhaps "We have a new iteration of the hardware design, so update the
devicetree to match."?
>
> Signed-off-by: Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com>
Overall it feels a bit untidy updating the description of distinct
devices in the one patch.
> ---
> .../aspeed/aspeed-bmc-facebook-yosemite4.dts | 78 ++++++++++++++-----
> 1 file changed, 58 insertions(+), 20 deletions(-)
>
> 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 64075cc41d92..e45293762316 100644
> --- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite4.dts
> +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite4.dts
> @@ -433,16 +433,14 @@ eeprom@51 {
> reg = <0x51>;
> };
>
> - i2c-mux@71 {
> - compatible = "nxp,pca9846";
> + i2c-mux@74 {
> + compatible = "nxp,pca9546";
> #address-cells = <1>;
> #size-cells = <0>;
> -
> - idle-state = <0>;
> i2c-mux-idle-disconnect;
> - reg = <0x71>;
> + reg = <0x74>;
>
> - i2c@0 {
> + inux30: i2c@0{
'inux'? 'imux'?
> #address-cells = <1>;
> #size-cells = <0>;
> reg = <0>;
> @@ -450,26 +448,46 @@ i2c@0 {
> adc@1f {
> compatible = "ti,adc128d818";
> reg = <0x1f>;
> - ti,mode = /bits/ 8 <2>;
> + ti,mode = /bits/ 8 <1>;
> };
>
> pwm@20{
> - compatible = "max31790";
> - reg = <0x20>;
> + compatible = "maxim,max31790";
This looks like a change motivated by binding validation or a driver
change rather than hardware design :)
> #address-cells = <1>;
> #size-cells = <0>;
> + reg = <0x20>;
> + channel@4 {
> + reg = <4>;
> + sensor-type = "TACH";
> + };
> +
> + channel@5 {
> + reg = <5>;
> + sensor-type = "TACH";
> + };
> };
>
> gpio@22{
> compatible = "ti,tca6424";
> reg = <0x22>;
> + gpio-controller;
> + #gpio-cells = <2>;
> };
>
> - pwm@23{
> - compatible = "max31790";
> - reg = <0x23>;
> + pwm@2f{
> + compatible = "maxim,max31790";
Again here
Andrew
next prev parent reply other threads:[~2024-04-26 0:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 6:06 [PATCH v1 0/2] Update yosemite4 dts for nct7363 and hardware Delphine CC Chiu
2024-04-25 6:06 ` [PATCH v1 1/2] Revise mux and hardware in yosemite4 dts Delphine CC Chiu
2024-04-26 0:51 ` Andrew Jeffery [this message]
2024-04-25 6:06 ` [PATCH v1 2/2] Add nct7363 " Delphine CC Chiu
2024-04-26 0:59 ` 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=f355ad1adb96cd8398c4ac81d1c72df289a2aaf0.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=Delphine_CC_Chiu@wiwynn.com \
--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=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;
as well as URLs for NNTP newsgroup(s).