From: Rob Herring <robh@kernel.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org,
Thomas Zimmermann <tzimmermann@suse.de>,
imx@lists.linux.dev, linux-kernel@vger.kernel.org,
Maxime Ripard <mripard@kernel.org>,
dri-devel@lists.freedesktop.org, Simona Vetter <simona@ffwll.ch>,
David Airlie <airlied@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: Re: [PATCH 1/1] dt-bindings: display: convert himax,hx8357d.txt to yaml format
Date: Fri, 30 May 2025 09:02:45 -0500 [thread overview]
Message-ID: <20250530140245.GA1608370-robh@kernel.org> (raw)
In-Reply-To: <174854325819.3595451.10273154567966477690.robh@kernel.org>
On Thu, May 29, 2025 at 01:27:38PM -0500, Rob Herring (Arm) wrote:
>
> On Thu, 29 May 2025 12:48:21 -0400, Frank Li wrote:
> > Convert himax,hx8357d.txt to yaml format.
> >
> > Additional changes:
> > - add spi parent node in examples.
> > - ref to spi-peripheral-props.yaml.
> > - change himax,hx8357a to himax,hx8357 to align driver and existed dts.
> > - add himax,hx8369a and fallback to himax,hx8369.
> > - allow gpios-reset, spi-cpha and spi-cpol to align existed dts.
Fix the .dts files and drop gpios-reset. The kernel has a work-around
and I would assume it's been in place long enough to support
reset-gpios.
Rob
next prev parent reply other threads:[~2025-05-30 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 16:48 [PATCH 1/1] dt-bindings: display: convert himax,hx8357d.txt to yaml format Frank Li
2025-05-29 16:48 ` [PATCH 1/1] dt-bindings: display: convert himax, hx8357d.txt " Frank Li
2025-05-29 18:27 ` [PATCH 1/1] dt-bindings: display: convert himax,hx8357d.txt " Rob Herring (Arm)
2025-05-30 14:02 ` Rob Herring [this message]
2025-05-29 18:30 ` [PATCH 1/1] dt-bindings: display: convert himax, hx8357d.txt " kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2025-05-30 3:05 kernel test robot
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=20250530140245.GA1608370-robh@kernel.org \
--to=robh@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.