Re: [PATCH v2 0/2] arm64: dts: qcom: Add RPi 7-inch DSI panel overlays for Monaco/Lemans EVK

[Shashank Maurya]

On Thu, Sep 10, 2026 at 02:35:41PM -0500, Bjorn Andersson wrote:
> On Mon, Sep 07, 2026 at 12:03:52PM +0530, Shashank Maurya wrote:
> > Add device tree overlays to enable support for the Raspberry Pi 7-inch
> > DSI touchscreen panel on Qualcomm Monaco and Lemans EVK platforms.
> > 
> > The overlays configure the panel on the primary DSI interface using
> > a 2-lane DSI connection and instantiate the panel MCU on the
> > corresponding touchscreen I2C bus for each platform. The changes
> > allow the Raspberry Pi 7-inch display to be used as an external
> > display option on both EVKs without affecting the default platform
> > configuration.
> > 
> > ---
> > To: Bjorn Andersson <andersson@xxxxxxxxxx>
> > To: Konrad Dybcio <konradybcio@xxxxxxxxxx>
> > To: Rob Herring <robh@xxxxxxxxxx>
> > To: Krzysztof Kozlowski <krzk+dt@xxxxxxxxxx>
> > To: Conor Dooley <conor+dt@xxxxxxxxxx>
> > To: Florian Fainelli <florian.fainelli@xxxxxxxxxxxx>
> > To: Broadcom internal kernel review list <bcm-kernel-feedback-list@xxxxxxxxxxxx>
> > Cc: linux-arm-msm@xxxxxxxxxxxxxxx
> > Cc: devicetree@xxxxxxxxxxxxxxx
> > Cc: linux-kernel@xxxxxxxxxxxxxxx
> > Cc: linux-rpi-kernel@xxxxxxxxxxxxxxxxxxx
> > Cc: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx
> > 
> > ---
> > Shashank Maurya (2):
> >       arm64: dts: qcom: monaco-evk: Add Raspberry Pi 7-inch DSI panel overlay
> >       arm64: dts: qcom: lemans-evk: Add Raspberry Pi 7-inch DSI panel overlay
> > 
> >  arch/arm64/boot/dts/qcom/Makefile                  |  4 ++
> >  .../dts/qcom/lemans-evk-raspberrypi-dsi-7inch.dtso | 83 ++++++++++++++++++++++
> >  .../dts/qcom/monaco-evk-raspberrypi-dsi-7inch.dtso | 82 +++++++++++++++++++++
> >  3 files changed, 169 insertions(+)
> > ---
> > base-commit: ed2647532a225739e86c7f236a2ce82764ec2772
> > change-id: 20260907-rpi_dts_overlay-58088ffce047
> > prerequisite-message-id: <20260907-rpi_reg-v2-0-0c59aa60d31f@xxxxxxxxxxxxxxxx>
> 
> The two dts patches in this series clearly relates to those two
> regulator patches, which has received change requests.
> 
> I would have sent the 4 patches together in a series, but as you didn't
> you sent this series with unmet dependencies.
> 
> All I can do now is reject this series as well. Please send v2 once the
> driver changes has been merged and you have validated this again.
> 
> Regards,
> Bjorn
> 
> > prerequisite-patch-id: 5212bf185b35c36ed8857a67f29e60386d59ac60
> > prerequisite-patch-id: 056a90b913170106a6f8c1feb2366ee83c4375b9
> > 
> > Best regards,
> > --  
> > Shashank Maurya <shashank.maurya@xxxxxxxxxxxxxxxx>
> > 

Hi Bjorn,

Thanks for the review.

The regulator patches and DTS patches are targeting different maintainer trees 
and therefore were developed and submitted from separate workspaces. While the
DTS changes depend on the regulator updates, the two sets of patches cannot 
realistically be carried in a single series because they are reviewed and 
merged through different paths.

I submitted the DTS series separately to start the review process in parallel,
but I understand your concern about the unresolved dependency.

Regards,
Shashank