From: Adam Azuddin <azuddinadam@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
neil.armstrong@linaro.org, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, jesszhan0024@gmail.com,
airlied@gmail.com, simona@ffwll.ch, andersson@kernel.org,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] dt-bindings: display: panel: Add RAiO RA8875 display controller
Date: Sat, 7 Nov 2026 19:12:25 +0800 [thread overview]
Message-ID: <au8HmdyRnuFmSmKh@marchy> (raw)
In-Reply-To: <20261103-zippy-quantum-bat-98b5ed@quoll>
On Tue, Nov 03, 2026 at 11:49:07AM +0100, Krzysztof Kozlowski wrote:
> On Fri, Oct 30, 2026 at 04:37:35PM +0800, Adam Azuddin wrote:
> > The RA8875 is an SPI-connected TFT display controller by RAiO
> > Technology Inc. It supports display resolutions of up to 800x480.
> >
> > Assisted-by: LLM
>
> You can drop this.
>
Will drop.
> > + interrupts:
> > + description:
> > + INT# pin, active low. Signals RA8875 interrupt events such as touch
> > + panel, key scan, DMA, BTE and font access completion. Optional, since
> > + the host can poll the interrupt status register instead.
>
> Last sentence is not correct. What driver can do is here less relevant.
> Question is whether hardware datasheet allows interrupt being not
> connected.
>
Understood. I will drop the sentence referencing driver polling.
Thanks for the review.
Regards,
Adam
next prev parent reply other threads:[~2026-11-07 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 8:37 [PATCH v5 0/2] drm/tiny: Add RAiO RA8875 display controller driver support Adam Azuddin
2026-10-30 8:37 ` [PATCH v5 1/2] dt-bindings: display: panel: Add RAiO RA8875 display controller Adam Azuddin
2026-11-03 10:49 ` Krzysztof Kozlowski
2026-11-07 11:12 ` Adam Azuddin [this message]
2026-10-30 8:37 ` [PATCH v5 2/2] drm/tiny: Add RAiO RA8875 display controller driver Adam Azuddin
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=au8HmdyRnuFmSmKh@marchy \
--to=azuddinadam@gmail.com \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesszhan0024@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--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
all inboxes | Powered by JetHome®