From: Vaishnav Achath <vaishnav.a@ti.com>
To: "Kumar, Udit" <u-kumar1@ti.com>, <nm@ti.com>, <vigneshr@ti.com>,
<kristo@kernel.org>, <robh@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<s-vadapalli@ti.com>
Subject: Re: [PATCH 2/2] arm64: dts: ti: k3-j722s-evm: Enable OSPI NOR support
Date: Mon, 19 Feb 2024 13:53:13 +0530 [thread overview]
Message-ID: <09853939-e623-42f1-bf80-1938161d1136@ti.com> (raw)
In-Reply-To: <0ca01a1b-8956-40dd-8286-77276e021633@ti.com>
Hi Udit,
On 19/02/24 11:25, Kumar, Udit wrote:
> Hi Vaishnav
>
> On 2/16/2024 7:25 PM, Vaishnav Achath wrote:
>> J722S EVM has S28HS512T 64 MiB Octal SPI NOR flash connected
>> to the OSPI interface, add support for the flash and describe
>> the partition information as per bootloader.
>>
>> Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
>> ---
>> arch/arm64/boot/dts/ti/k3-j722s-evm.dts | 79 +++++++++++++++++++++++++
>> 1 file changed, 79 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-j722s-evm.dts
>> b/arch/arm64/boot/dts/ti/k3-j722s-evm.dts
>> index 9e12a6e9111f..b1c6499c0c9d 100644
>> --- a/arch/arm64/boot/dts/ti/k3-j722s-evm.dts
>> +++ b/arch/arm64/boot/dts/ti/k3-j722s-evm.dts
>> @@ -169,6 +169,23 @@ J722S_IOPAD(0x015c, PIN_INPUT, 0) /* (AD25)
>> MDIO0_MDIO */
>> >;
>> };
>> + ospi0_pins_default: ospi0-default-pins {
>> + pinctrl-single,pins = <
>> + J722S_IOPAD(0x0000, PIN_OUTPUT, 0) /* (P23) OSPI0_CLK */
>> + J722S_IOPAD(0x002c, PIN_OUTPUT, 0) /* (M25) OSPI0_CSn0 */
>> + J722S_IOPAD(0x000c, PIN_INPUT, 0) /* (L25) OSPI0_D0 */
>> + J722S_IOPAD(0x0010, PIN_INPUT, 0) /* (N24) OSPI0_D1 */
>> + J722S_IOPAD(0x0014, PIN_INPUT, 0) /* (N25) OSPI0_D2 */
>> + J722S_IOPAD(0x0018, PIN_INPUT, 0) /* (M24) OSPI0_D3 */
>> + J722S_IOPAD(0x001c, PIN_INPUT, 0) /* (N21) OSPI0_D4 */
>> + J722S_IOPAD(0x0020, PIN_INPUT, 0) /* (N22) OSPI0_D5 */
>> + J722S_IOPAD(0x0024, PIN_INPUT, 0) /* (P21) OSPI0_D6 */
>> + J722S_IOPAD(0x0028, PIN_INPUT, 0) /* (N20) OSPI0_D7 */
>> + J722S_IOPAD(0x0008, PIN_INPUT, 0) /* (P22) OSPI0_DQS */
>
>
> Could you check, Pin name in comments
>
> For example, Schematic says L22 is for OSPI0_DQS , but comments says P22
>
> However offsets are good .
Thanks for the review, I will fix this in the next revision.
>
>> + >;
>> + bootph-all;
>> + };
>> +
>> rgmii1_pins_default: rgmii1-default-pins {
>> pinctrl-single,pins = <
>> J722S_IOPAD(0x014c, PIN_INPUT, 0) /* (AC25) RGMII1_RD0 */
>> @@ -290,6 +307,68 @@ exp1: gpio@23 {
>> };
>> };
>> +&ospi0 {
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&ospi0_pins_default>;
>> + status = "okay";
>> +
>> + flash@0 {
>> + compatible = "jedec,spi-nor";
>> + reg = <0x0>;
>> + spi-tx-bus-width = <8>;
>> + spi-rx-bus-width = <8>;
>> + spi-max-frequency = <25000000>;
>> + cdns,tshsl-ns = <60>;
>> + cdns,tsd2d-ns = <60>;
>> + cdns,tchsh-ns = <60>;
>> + cdns,tslch-ns = <60>;
>> + cdns,read-delay = <4>;
>> + bootph-all;
>> +
>> + partitions {
>> + compatible = "fixed-partitions";
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> +
>> + partition@0 {
>> + label = "ospi.tiboot3";
>> + reg = <0x00 0x80000>;
>> + };
>
>
> I suggest to keep 1MB to accommodate future size increase
>
For J722S, the maximum loadable SPL size is 0x7e000, images larger than
these cannot be loaded by ROM, increasing the size here will not give
any benefit, planning to keep as-is if there are no objections.
Thanks and Regards,
Vaishnav
>> +
>> + partition@80000 {
>> + label = "ospi.tispl";
>> + reg = <0x80000 0x200000>;
>> + };
>> +
>> + partition@280000 {
>> + label = "ospi.u-boot";
>> + reg = <0x280000 0x400000>;
>> + };
>> +
>> + partition@680000 {
>> + label = "ospi.env";
>> + reg = <0x680000 0x40000>;
>> + };
>> +
>> + partition@6c0000 {
>> + label = "ospi.env.backup";
>> + reg = <0x6c0000 0x40000>;
>> + };
>> +
>> + partition@800000 {
>> + label = "ospi.rootfs";
>> + reg = <0x800000 0x37c0000>;
>> + };
>> +
>> + partition@3fc0000 {
>> + label = "ospi.phypattern";
>> + reg = <0x3fc0000 0x40000>;
>> + };
>> + };
>> + };
>> +
>> +};
>> +
>> &sdhci1 {
>> /* SD/MMC */
>> vmmc-supply = <&vdd_mmc1>;
next prev parent reply other threads:[~2024-02-19 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 13:55 [PATCH 0/2] Add OSPI and Ethernet support on J722S EVM Vaishnav Achath
2024-02-16 13:55 ` [PATCH 1/2] arm64: dts: ti: k3-j722s-evm: Enable CPSW3G RGMII1 Vaishnav Achath
2024-02-16 13:55 ` [PATCH 2/2] arm64: dts: ti: k3-j722s-evm: Enable OSPI NOR support Vaishnav Achath
2024-02-19 5:55 ` Kumar, Udit
2024-02-19 8:23 ` Vaishnav Achath [this message]
2024-02-19 8:45 ` Kumar, Udit
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=09853939-e623-42f1-bf80-1938161d1136@ti.com \
--to=vaishnav.a@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=u-kumar1@ti.com \
--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
all inboxes | Powered by JetHome®