From: Vaishnav Achath <vaishnav.a@ti.com> To: <nm@ti.com>, <afd@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>, <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org> Cc: <devicetree@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>, <u-kumar1@ti.com>, <vaishnav.a@ti.com> Subject: [PATCH 0/4] arm64: dts: ti: j721e: Add HyperFlash support Date: Fri, 5 May 2023 19:44:03 +0530 [thread overview] Message-ID: <20230505141407.15134-1-vaishnav.a@ti.com> (raw) This series adds hyperflash support for J721E. J721E SoC has HyperBus and OSPI controller muxed within the FSS subsystem and the J721E SoM has a 64 MiB S28 OSPI flash and a 64 MiB Hyperflash present which is muxed externally also. * Patch 1/4 adds the hyperbus controller nodes and fixes DT compile warnings. * Patch 2/4 adds the hyperflash support in the SoM DTS. * Patch 3 and 4/4 enables the pinmux for external mux that selects between hyperflash or OSPI NOR flash, this is done for J7200 and J721E platforms since it is required in U-Boot and helps keep the DT in sync. Patch 1/4 depends on the following patch: https://lore.kernel.org/all/20230424184810.29453-1-afd@ti.com/ Patch 3 depends on the below fix for pinmux offsets in J7200: https://lore.kernel.org/all/20230419040007.3022780-2-u-kumar1@ti.com/ Bootlog and basic hyperflash erase-write-read test: https://gist.github.com/vaishnavachath/be652108f3e360f1e2d41b499df844ef Thanks and Regards, Vaishnav Vaishnav Achath (4): arm64: dts: ti: k3-j721e-mcu-wakeup: Add HyperBus node arm64: dts: ti: k3-j721e-som-p0: Add HyperFlash node arm64: dts: ti: k3-j7200-common-proc-board: Add OSPI/Hyperflash select pinmux arm64: dts: ti: k3-j721e-common-proc-board: Add OSPI/Hyperflash select pinmux .../dts/ti/k3-j7200-common-proc-board.dts | 11 ++++++ .../dts/ti/k3-j721e-common-proc-board.dts | 11 ++++++ .../boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 25 +++++++++++-- arch/arm64/boot/dts/ti/k3-j721e-som-p0.dtsi | 35 +++++++++++++++++++ 4 files changed, 80 insertions(+), 2 deletions(-) -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Vaishnav Achath <vaishnav.a@ti.com> To: <nm@ti.com>, <afd@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>, <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org> Cc: <devicetree@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>, <u-kumar1@ti.com>, <vaishnav.a@ti.com> Subject: [PATCH 0/4] arm64: dts: ti: j721e: Add HyperFlash support Date: Fri, 5 May 2023 19:44:03 +0530 [thread overview] Message-ID: <20230505141407.15134-1-vaishnav.a@ti.com> (raw) This series adds hyperflash support for J721E. J721E SoC has HyperBus and OSPI controller muxed within the FSS subsystem and the J721E SoM has a 64 MiB S28 OSPI flash and a 64 MiB Hyperflash present which is muxed externally also. * Patch 1/4 adds the hyperbus controller nodes and fixes DT compile warnings. * Patch 2/4 adds the hyperflash support in the SoM DTS. * Patch 3 and 4/4 enables the pinmux for external mux that selects between hyperflash or OSPI NOR flash, this is done for J7200 and J721E platforms since it is required in U-Boot and helps keep the DT in sync. Patch 1/4 depends on the following patch: https://lore.kernel.org/all/20230424184810.29453-1-afd@ti.com/ Patch 3 depends on the below fix for pinmux offsets in J7200: https://lore.kernel.org/all/20230419040007.3022780-2-u-kumar1@ti.com/ Bootlog and basic hyperflash erase-write-read test: https://gist.github.com/vaishnavachath/be652108f3e360f1e2d41b499df844ef Thanks and Regards, Vaishnav Vaishnav Achath (4): arm64: dts: ti: k3-j721e-mcu-wakeup: Add HyperBus node arm64: dts: ti: k3-j721e-som-p0: Add HyperFlash node arm64: dts: ti: k3-j7200-common-proc-board: Add OSPI/Hyperflash select pinmux arm64: dts: ti: k3-j721e-common-proc-board: Add OSPI/Hyperflash select pinmux .../dts/ti/k3-j7200-common-proc-board.dts | 11 ++++++ .../dts/ti/k3-j721e-common-proc-board.dts | 11 ++++++ .../boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 25 +++++++++++-- arch/arm64/boot/dts/ti/k3-j721e-som-p0.dtsi | 35 +++++++++++++++++++ 4 files changed, 80 insertions(+), 2 deletions(-) -- 2.17.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-05-05 14:14 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-05 14:14 Vaishnav Achath [this message] 2023-05-05 14:14 ` [PATCH 0/4] arm64: dts: ti: j721e: Add HyperFlash support Vaishnav Achath 2023-05-05 14:14 ` [PATCH 1/4] arm64: dts: ti: k3-j721e-mcu-wakeup: Add HyperBus node Vaishnav Achath 2023-05-05 14:14 ` Vaishnav Achath 2023-05-05 14:14 ` [PATCH 2/4] arm64: dts: ti: k3-j721e-som-p0: Add HyperFlash node Vaishnav Achath 2023-05-05 14:14 ` Vaishnav Achath 2023-05-05 14:14 ` [PATCH 3/4] arm64: dts: ti: k3-j7200-common-proc-board: Add OSPI/Hyperflash select pinmux Vaishnav Achath 2023-05-05 14:14 ` Vaishnav Achath 2023-05-05 14:14 ` [PATCH 4/4] arm64: dts: ti: k3-j721e-common-proc-board: " Vaishnav Achath 2023-05-05 14:14 ` Vaishnav Achath 2023-05-13 12:35 ` [PATCH 0/4] arm64: dts: ti: j721e: Add HyperFlash support Vaishnav Achath
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=20230505141407.15134-1-vaishnav.a@ti.com \ --to=vaishnav.a@ti.com \ --cc=afd@ti.com \ --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+dt@kernel.org \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.