Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 3 May 2023 06:51:30 -0500
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
Message-ID: <20230503115130.c7m4a7crub7kmfjw@gluten>
References: <20230503091218.25899-1-vaishnav.a@ti.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20230503091218.25899-1-vaishnav.a@ti.com>
Precedence: bulk

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