Devicetree
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Anand Tiwari <anand.tiwari@oss.qualcomm.com>
Cc: Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,  venkata.valluru@oss.qualcomm.com,
	vishnu.saini@oss.qualcomm.com,
	 Jessica Zhang <jesszhan0024@gmail.com>
Subject: Re: [PATCH 1/2] arm64: dts: qcom: hamoa-iot-evk: Add eDP display overlay
Date: Mon, 10 Aug 2026 08:11:12 -0500	[thread overview]
Message-ID: <annMk4RnQKl51Oug@baldur> (raw)
In-Reply-To: <anmKUoLFSDpgOjoE@hu-anantiwa-hyd.qualcomm.com>

On Mon, Aug 10, 2026 at 01:52:42PM +0530, Anand Tiwari wrote:
> On Fri, Aug 07, 2026 at 04:01:05PM -0500, Bjorn Andersson wrote:
> > On Fri, Aug 07, 2026 at 03:30:13PM +0530, Anand Tiwari wrote:
> > > On Thu, Aug 06, 2026 at 07:05:37PM -0500, Bjorn Andersson wrote:
> > > > On Thu, Aug 06, 2026 at 10:01:20PM +0530, Anand Tiwari wrote:
> > > > > Move the eDP panel configuration and related power, backlight, and pinctrl
> > > > > nodes into a separate overlay. Keep the base DTB suitable for headless
> > > > > variants and provide a composite DTB for headed variants.
> > > > 
> > > > To quote:
> > > > https://docs.kernel.org/process/submitting-patches.html#describe-your-changes
> > > > 
> > > > """
> > > > Describe your problem. Whether your patch is a one-line bug fix or 5000
> > > > lines of a new feature, there must be an underlying problem that
> > > > motivated you to do this work. Convince the reviewer that there is a
> > > > problem worth fixing and that it makes sense for them to read past the
> > > > first paragraph.
> > > > """
> > > > 
> > > > In fact, I'm not even able to guess what the problem you're fixing here.
> > > > 
> > > > Regards,
> > > > Bjorn
> > > >
> > > 
> > > The problem is that the base device trees currently describe the eDP
> > > display hardware unconditionally. However, Hamoa and Purwa IoT EVKs
> > > are also available in headless variants without an eDP panel.
> > > 
> > > With current base DTBs, headless variants are not stable where eDP panel is not
> > > physically connected with board and userspace is trying to use it.

If this is the configuration that is shipping, then it better be
stable...

> > > 
> > > This series fixes the inaccurate hardware description by keeping the
> > > base DTBs limited to hardware common to both variants and moving the
> > > eDP-specific nodes into separate overlays. The base DTB can therefore
> > > be used for headless variants, while the overlay is selected for
> > > headed variants.
> > >  
> > 
> > I see, then it seems your change does make sense. I don't understand why
> > you didn't explained this in the commit message though.
> >
> 
> I will update the commit msg with details, currently details added only in 
> series cover letter. 
> 
> > 
> > I further do not understand how it can be that nobody noticed that the
> > display was missing on their Hamoa EVK during the 11 months since I
> > merged the offending patch - this is completely unacceptable.
> > 
> > Regards,
> > Bjorn
> >
> 
> Internally, we have always required the eDP panel to be connected during 
> testing. In theory, this platform is expected to have a display attached 
> by default.
> 1. The only difference is that the eDP connector on this board is externally 
> accessible and can be disconnected quite easily.
> 2. Also, only the boards shipped to customers are delivered without an eDP 
> panel attached by default, which is why this requirement exists. 

In particular since you're shipping it without display, that is the
configuration that should be the dts (and that you should test...).

Common additional configurations can then be added as overlays - while
the developer can add their own overlays as needed.

Regards,
Bjorn

  reply	other threads:[~2026-08-10 13:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06 16:31 [PATCH 0/2] arm64: dts: qcom: Add eDP display overlays for hamoa and purwa IoT EVKs Anand Tiwari
2026-08-06 16:31 ` [PATCH 1/2] arm64: dts: qcom: hamoa-iot-evk: Add eDP display overlay Anand Tiwari
2026-08-06 16:55   ` sashiko-bot
2026-08-07  0:05   ` Bjorn Andersson
2026-08-07 10:00     ` Anand Tiwari
2026-08-07 21:01       ` Bjorn Andersson
2026-08-10  8:22         ` Anand Tiwari
2026-08-10 13:11           ` Bjorn Andersson [this message]
2026-08-10  9:04       ` Dmitry Baryshkov
2026-08-06 16:31 ` [PATCH 2/2] arm64: dts: qcom: purwa-iot-evk: " Anand Tiwari
2026-08-06 16:54   ` sashiko-bot
2026-08-07  0:06   ` Bjorn Andersson
2026-08-07  9:22 ` [PATCH 0/2] arm64: dts: qcom: Add eDP display overlays for hamoa and purwa IoT EVKs Dmitry Baryshkov
2026-08-07 10:36   ` Anand Tiwari

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=annMk4RnQKl51Oug@baldur \
    --to=andersson@kernel.org \
    --cc=anand.tiwari@oss.qualcomm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jesszhan0024@gmail.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=venkata.valluru@oss.qualcomm.com \
    --cc=vishnu.saini@oss.qualcomm.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