From: Krzysztof Kozlowski <krzk@kernel.org>
To: Frese <freseenzo@gmail.com>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Noralf Trønnes" <noralf@tronnes.org>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Jessica Zhang" <jesszhan0024@gmail.com>,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: display: panel: mipi-dbi-spi: add sitronix,st7789v-tft28
Date: Wed, 16 Sep 2026 08:13:29 +0200 [thread overview]
Message-ID: <e061856c-f630-4978-b991-ea19cd23999b@kernel.org> (raw)
In-Reply-To: <f8fbfb26a60bd664bb4c436acfa541b5e4976916.camel@gmail.com>
On 13/09/2026 22:42, Frese wrote:
> Hi Krzysztof,
>
> Thanks for the review, this is one of my first kernel contributions,
> so please bear with me.
>
> This panel is a generic hobbyist module, wired via jumpers to a stock
> Raspberry Pi 4B, not soldered onto any fixed product like
> saef,sftc154b (Anbernic RG-Nano) or shineworld,lh133k (LXA boards).
> Mainline has no Raspberry Pi overlay tree, so there's no in-tree
> consumer to add. I noticed sainsmart18 currently has no in-tree
> consumer either, though it was added as part of the original binding's
> example, so I'm not sure that's a strong precedent. Would a
> documentation example, or an out-of-tree overlay demonstrating the
> tested wiring, be an acceptable alternative here?
>
> Vendor prefix was already fixed in v2 (sitronix,st7789v-tft28) —
> sorry the subject change broke Patchwork's series detection.
We usually do not document bindings for hardware just because it exists.
Binding needs a user and one patch means there is no user.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-09-16 6:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 20:33 Enzo Frese
2026-09-13 9:34 ` Krzysztof Kozlowski
2026-09-13 20:42 ` Frese
2026-09-16 6:13 ` Krzysztof Kozlowski [this message]
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=e061856c-f630-4978-b991-ea19cd23999b@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freseenzo@gmail.com \
--cc=jesszhan0024@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=noralf@tronnes.org \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®