Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Vaishnav Achath <vaishnav.a@ti.com>
Cc: <kristo@kernel.org>, <vigneshr@ti.com>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<u-kumar1@ti.com>
Subject: Re: [PATCH 0/4] arm64: dts: ti: Describe flash partitions for J7 platforms
Date: Wed, 3 May 2023 06:51:30 -0500	[thread overview]
Message-ID: <20230503115130.c7m4a7crub7kmfjw@gluten> (raw)
In-Reply-To: <20230503091218.25899-1-vaishnav.a@ti.com>

On 14:42-20230503, Vaishnav Achath wrote:
> This series adds flash partition description through DT, currently
> the flash partitions for J7 platforms is described through the mtdparts
> commandline parameter passed from bootloader, this requires maintenance
> of the partition information in a mtdparts string which is error prone.
> 
> Once the flash partitions are described through DT, the support for
> mtdparts can be removed for these platforms from u-boot also.
> 
> Vaishnav Achath (4):
>   arm64: dts: ti: k3-j721e-som: Describe OSPI flash partition info
>   arm64: dts: ti: k3-j721e-som: Describe QSPI flash partition info
>   arm64: dts: ti: k3-j721e-sk: Describe OSPI flash partition info
>   arm64: dts: ti: k3-j7200-som: Describe OSPI and Hyperflash partition
>     info
> 
>  arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi   | 72 +++++++++++++++++++
>  .../dts/ti/k3-j721e-common-proc-board.dts     | 46 ++++++++++++
>  arch/arm64/boot/dts/ti/k3-j721e-sk.dts        | 46 ++++++++++++
>  arch/arm64/boot/dts/ti/k3-j721e-som-p0.dtsi   | 46 ++++++++++++
>  4 files changed, 210 insertions(+)

Please address the feedback in [1] prior to adding the partitions? and
could you ensure it is done for all the impacted k3 SoCs?


[1] https://lore.kernel.org/all/f5861b8b-637a-e127-2945-8994a472015a@ti.com/

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2023-05-03 11:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03  9:12 [PATCH 0/4] arm64: dts: ti: Describe flash partitions for J7 platforms Vaishnav Achath
2023-05-03  9:12 ` [PATCH 1/4] arm64: dts: ti: k3-j721e-som: Describe OSPI flash partition info Vaishnav Achath
2023-05-03  9:12 ` [PATCH 2/4] arm64: dts: ti: k3-j721e-som: Describe QSPI " Vaishnav Achath
2023-05-03  9:12 ` [PATCH 3/4] arm64: dts: ti: k3-j721e-sk: Describe OSPI " Vaishnav Achath
2023-05-03  9:12 ` [PATCH 4/4] arm64: dts: ti: k3-j7200-som: Describe OSPI and Hyperflash " Vaishnav Achath
2023-05-03 11:51 ` Nishanth Menon [this message]
2023-05-04  5:39   ` [PATCH 0/4] arm64: dts: ti: Describe flash partitions for J7 platforms 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=20230503115130.c7m4a7crub7kmfjw@gluten \
    --to=nm@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=robh+dt@kernel.org \
    --cc=u-kumar1@ti.com \
    --cc=vaishnav.a@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