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: Ricky CX Wu <ricky.cx.wu.wiwynn@gmail.com>,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/2] ARM: dts: aspeed: yosemite4: Add gpio pca9506 for CPLD IOE
Date: Thu, 12 Sep 2024 11:40:48 +0930 [thread overview]
Message-ID: <ccef1d90b9a7eb343e99afa2c6cd6ea7407b0541.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20240910054751.2943217-3-Delphine_CC_Chiu@wiwynn.com>
On Tue, 2024-09-10 at 13:47 +0800, Delphine CC Chiu wrote:
> From: Ricky CX Wu <ricky.cx.wu.wiwynn@gmail.com>
>
> We use CPLD to emulate gpio pca9506 I/O expander on each server
> boards.
> Therefore, add pca9506 to probe driver for the CPLD I/O expander.
I think it might be best if you add your own compatible to the list in
the gpio-pca95xx binding just in case there are some behavioural quirks
of your CPLD implementation? Not sure if this should be
"facebook,pca9506" or "wywinn,pca9506", but assuming facebook, from
there you can specify
compatible = "facebook,pca9506", "nxp,pca9506";
This allows you to add the quirks to the driver as required in the
future through the more-specific compatible.
Andrew
next prev parent reply other threads:[~2024-09-12 2:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 5:47 [PATCH v1 0/2] Yosemite4: Add devices on I2C buses to server boards Delphine CC Chiu
2024-09-10 5:47 ` [PATCH v1 1/2] ARM: dts: aspeed: yosemite4: Revise to use adm1281 on Medusa board Delphine CC Chiu
2024-09-10 5:47 ` [PATCH v1 2/2] ARM: dts: aspeed: yosemite4: Add gpio pca9506 for CPLD IOE Delphine CC Chiu
2024-09-12 2:10 ` Andrew Jeffery [this message]
2024-09-13 2:08 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2024-09-13 3:26 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2024-09-16 3:05 ` Andrew Jeffery
2024-09-18 1:53 ` Ricky CX Wu/WYHQ/Wiwynn
2024-09-18 1:55 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2024-09-19 1:59 ` [PATCH v1 0/2] Yosemite4: Add devices on I2C buses to server boards 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=ccef1d90b9a7eb343e99afa2c6cd6ea7407b0541.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=ricky.cx.wu.wiwynn@gmail.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;
as well as URLs for NNTP newsgroup(s).