From: Nishanth Menon <nm@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Aswath Govindraju <a-govindraju@ti.com>,
Lokesh Vutla <lokeshvutla@ti.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-am642-evm: Add support for SPI EEPROM
Date: Tue, 9 Mar 2021 08:54:26 -0600 [thread overview]
Message-ID: <20210309145426.tgt7ltlh22slygfm@santa> (raw)
In-Reply-To: <c06a39c5-88eb-1e6d-4ae2-796981db1e71@ti.com>
On 20:18-20210309, Vignesh Raghavendra wrote:
>
>
> On 3/1/21 11:35 AM, Aswath Govindraju wrote:
> > Add pinmux details and device tree node for the EEPROM attached to SPI0
> > module in main domain.
> >
> > Signed-off-by: Aswath Govindraju <a-govindraju@ti.com>
> > ---
>
> Reviewed-by: Vignesh Raghavendra <vigneshr@ti.com>
>
> Regards
> Vignesh
>
> >
> > This patch depends on,
> > https://patchwork.kernel.org/project/linux-arm-kernel/patch/20210301055109.17626-3-a-govindraju@ti.com/
Can you drop this dependency and rebase on top of my -next branch or
linux-next ? I am not able to apply the patch directly and would like to
avoid hand modifying the patch.
> >
> > arch/arm64/boot/dts/ti/k3-am642-evm.dts | 22 ++++++++++++++++++++++
> > 1 file changed, 22 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/ti/k3-am642-evm.dts b/arch/arm64/boot/dts/ti/k3-am642-evm.dts
> > index bfd849a29655..bc5bd7f896ab 100644
> > --- a/arch/arm64/boot/dts/ti/k3-am642-evm.dts
> > +++ b/arch/arm64/boot/dts/ti/k3-am642-evm.dts
> > @@ -139,6 +139,15 @@
> > AM64X_IOPAD(0x02a8, PIN_OUTPUT, 0) /* (E19) USB0_DRVVBUS */
> > >;
> > };
> > +
> > + main_spi0_pins_default: main-spi0-pins-default {
> > + pinctrl-single,pins = <
> > + AM64X_IOPAD(0x0210, PIN_INPUT, 0) /* (D13) SPI0_CLK */
> > + AM64X_IOPAD(0x0208, PIN_OUTPUT, 0) /* (D12) SPI0_CS0 */
> > + AM64X_IOPAD(0x0214, PIN_OUTPUT, 0) /* (A13) SPI0_D0 */
> > + AM64X_IOPAD(0x0218, PIN_INPUT, 0) /* (A14) SPI0_D1 */
> > + >;
> > + };
> > };
> >
> > &main_uart0 {
> > @@ -245,6 +254,19 @@
> > pinctrl-0 = <&main_usb0_pins_default>;
> > };
> >
> > +&main_spi0 {
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&main_spi0_pins_default>;
> > + ti,pindir-d0-out-d1-in = <1>;
> > + eeprom@0 {
> > + compatible = "microchip,93lc46b";
> > + reg = <0>;
> > + spi-max-frequency = <1000000>;
> > + spi-cs-high;
> > + data-size = <16>;
> > + };
> > +};
> > +
> > &sdhci0 {
> > /* emmc */
> > bus-width = <8>;
> >
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2021-03-09 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 6:05 [PATCH] arm64: dts: ti: k3-am642-evm: Add support for SPI EEPROM Aswath Govindraju
2021-03-09 14:48 ` Vignesh Raghavendra
2021-03-09 14:54 ` Nishanth Menon [this message]
2021-03-09 15:25 ` Aswath Govindraju
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=20210309145426.tgt7ltlh22slygfm@santa \
--to=nm@ti.com \
--cc=a-govindraju@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).