From: Patrick Williams <patrick@stwcx.xyz>
To: Peter Yin <peteryin.openbmc@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@aj.id.au>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 5/5] ARM: dts: aspeed: Harma: Add spi-gpio
Date: Wed, 3 Jan 2024 06:17:10 -0600 [thread overview]
Message-ID: <ZZVQRgTe57G4Tc_w@heinlein.vulture-banana.ts.net> (raw)
In-Reply-To: <20240102044409.3810873-6-peteryin.openbmc@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1720 bytes --]
On Tue, Jan 02, 2024 at 12:44:09PM +0800, Peter Yin wrote:
> Add spi-gpio for tpm device.
>
> Signed-off-by: Peter Yin <peteryin.openbmc@gmail.com>
> ---
> .../dts/aspeed/aspeed-bmc-facebook-harma.dts | 21 +++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-harma.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-harma.dts
> index 36aad01dda20..25ae044cd176 100644
> --- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-harma.dts
> +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-harma.dts
> @@ -28,6 +28,8 @@ aliases {
> i2c29 = &imux29;
> i2c30 = &imux30;
> i2c31 = &imux31;
> +
> + spi1 = &spi_gpio;
> };
>
> chosen {
> @@ -67,6 +69,25 @@ led-2 {
> gpios = <&gpio0 124 GPIO_ACTIVE_HIGH>;
> };
> };
> +
> + spi_gpio: spi-gpio {
> + status = "okay";
> + compatible = "spi-gpio";
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + gpio-sck = <&gpio0 ASPEED_GPIO(Z, 3) GPIO_ACTIVE_HIGH>;
> + gpio-mosi = <&gpio0 ASPEED_GPIO(Z, 4) GPIO_ACTIVE_HIGH>;
> + gpio-miso = <&gpio0 ASPEED_GPIO(Z, 5) GPIO_ACTIVE_HIGH>;
> + num-chipselects = <1>;
> + cs-gpios = <&gpio0 ASPEED_GPIO(Z, 0) GPIO_ACTIVE_LOW>;
> +
> + tpmdev@0 {
> + compatible = "tcg,tpm_tis-spi";
Due to other pending changes, there is a request that all tpm_tis-spi
also contain a compatible with a chip vendor. Please add
"infineon,slb9670".
See https://lore.kernel.org/lkml/ZZTS0p1hdAchIbKp@heinlein.vulture-banana.ts.net/
for more context.
> + spi-max-frequency = <33000000>;
> + reg = <0>;
> + };
> + };
> };
>
> // HOST BIOS Debug
> --
> 2.25.1
>
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-01-03 12:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 4:44 [PATCH v1 0/5] Revise Meta(Facebook) Harma BMC(AST2600) Peter Yin
2024-01-02 4:44 ` [PATCH v1 1/5] ARM: dts: aspeed: Harma: Revise SGPIO line name Peter Yin
2024-01-02 4:44 ` [PATCH v1 2/5] ARM: dts: aspeed: Harma: mapping ttyS2 to UART4 Peter Yin
2024-01-02 4:44 ` [PATCH v1 3/5] ARM: dts: aspeed: Harma: Remove Vuart Peter Yin
2024-01-02 4:44 ` [PATCH v1 4/5] ARM: dts: aspeed: Harma: Add cpu power good line name Peter Yin
2024-01-02 4:44 ` [PATCH v1 5/5] ARM: dts: aspeed: Harma: Add spi-gpio Peter Yin
2024-01-03 12:17 ` Patrick Williams [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=ZZVQRgTe57G4Tc_w@heinlein.vulture-banana.ts.net \
--to=patrick@stwcx.xyz \
--cc=andrew@aj.id.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peteryin.openbmc@gmail.com \
--cc=robh+dt@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).