The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: barnabas.czeman@mainlining.org
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
	Jessica Zhang <quic_jesszhan@quicinc.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: display: panel: Add BOE TD4320
Date: Tue, 29 Apr 2025 08:13:56 +0200	[thread overview]
Message-ID: <5a5e97f1-6ae1-46d2-a602-613e1b550ba5@kernel.org> (raw)
In-Reply-To: <d838dc2006c52bf6099767a2805ad826@mainlining.org>

On 28/04/2025 20:13, barnabas.czeman@mainlining.org wrote:
>>
>>> +
>>> +required:
>>> +  - compatible
>>> +  - reg
>>> +  - reset-gpios
>>
>> No supplies? This looks really incomplete.
> It works without supplies because BL is enabling them and there is no 
> qpnp-lcdb driver yet.

If something enables the supplies, means they exist. Binding must be
complete. Otherwise how bootloader using this binding can enable
supplies, if you do not allow them in the DTS the bootloader is going to
use?

> I do not see worth to add them at them moment but I can if you want.
>>
>>
>> Best regards,
>> Krzysztof


Best regards,
Krzysztof

  reply	other threads:[~2025-04-29  6:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-27  9:11 [PATCH 0/2] BOE TD4320 panel Barnabás Czémán
2025-04-27  9:11 ` [PATCH 1/2] dt-bindings: display: panel: Add BOE TD4320 Barnabás Czémán
2025-04-28  9:22   ` Krzysztof Kozlowski
2025-04-28 18:13     ` barnabas.czeman
2025-04-29  6:13       ` Krzysztof Kozlowski [this message]
2025-04-27  9:11 ` [PATCH 2/2] drivers: gpu: drm: " Barnabás Czémán

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=5a5e97f1-6ae1-46d2-a602-613e1b550ba5@kernel.org \
    --to=krzk@kernel.org \
    --cc=airlied@gmail.com \
    --cc=barnabas.czeman@mainlining.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=quic_jesszhan@quicinc.com \
    --cc=robh@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    /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