From: <Conor.Dooley@microchip.com>
To: <heiko@sntech.de>, <airlied@linux.ie>, <daniel@ffwll.ch>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<thierry.reding@gmail.com>, <sam@ravnborg.org>,
<Eugeniy.Paltsev@synopsys.com>, <vkoul@kernel.org>,
<lgirdwood@gmail.com>, <broonie@kernel.org>,
<fancer.lancer@gmail.com>, <daniel.lezcano@linaro.org>,
<palmer@dabbelt.com>, <palmer@rivosinc.com>,
<linux-riscv@lists.infradead.org>
Cc: <tglx@linutronix.de>, <paul.walmsley@sifive.com>,
<aou@eecs.berkeley.edu>, <masahiroy@kernel.org>,
<damien.lemoal@opensource.wdc.com>, <geert@linux-m68k.org>,
<niklas.cassel@wdc.com>, <dillon.minfei@gmail.com>,
<jee.heng.sia@intel.com>, <joabreu@synopsys.com>,
<dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <dmaengine@vger.kernel.org>,
<alsa-devel@alsa-project.org>, <linux-spi@vger.kernel.org>,
<mail@conchuod.ie>
Subject: Re: [PATCH v2 01/16] dt-bindings: display: convert ilitek,ili9341.txt to dt-schema
Date: Tue, 28 Jun 2022 16:49:13 +0000 [thread overview]
Message-ID: <66f41fc5-9d9a-6c45-b0db-de33cc2b4051@microchip.com> (raw)
In-Reply-To: <22692709.6Emhk5qWAg@diego>
On 28/06/2022 16:04, Heiko Stübner wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Am Dienstag, 28. Juni 2022, 17:00:56 CEST schrieb Heiko Stübner:
>> Hi Conor,
>>
>> Am Montag, 27. Juni 2022, 21:39:49 CEST schrieb Conor Dooley:
>>> From: Conor Dooley <conor.dooley@microchip.com>
>>>
>>> A dt-schema binding for the Ilitek ili9341 was created as
>>> panel/ilitek,ili9341.yaml but the txt binding was ignored in the
>>> process. Move the remaining items in the txt binding to the yaml one &
>>> delete it.
>>>
>>> The example in the txt binding has a spi-max-frequency which disagrees
>>> with the yaml replacement (and its own documentation) so change that to
>>> conform with the binding. There are no users in tree of the Adafruit
>>> yx240qv29 to check against.
>>>
>>> Link: https://cdn-learn.adafruit.com/assets/assets/000/046/879/original/SPEC-YX240QV29-T_Rev.A__1_.pdf
>>> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
>>
>> in your v1 you already got a [0]
>> Reviewed-by: Rob Herring <robh@kernel.org>
>> for this patch
>>
>> Looking at the diffstat, which didn't change, you should
>> include such tags in followup revisions, to prevent
>> reviewers from double efforts.
>
> and now I see that the review actually happened _after_ v2 was send ;-)
;) you had me scratching my head for a moment!
>
>
>> [0] https://lore.kernel.org/r/20220627232054.GA3155668-robh@kernel.org
>>
>>> ---
>>> .../bindings/display/ilitek,ili9341.txt | 27 -----------
>>> .../display/panel/ilitek,ili9341.yaml | 48 +++++++++++++------
>>> 2 files changed, 34 insertions(+), 41 deletions(-)
>>> delete mode 100644 Documentation/devicetree/bindings/display/ilitek,ili9341.txt
>>>
>>> diff --git a/Documentation/devicetree/bindings/display/ilitek,ili9341.txt b/Documentation/devicetree/bindings/display/ilitek,ili9341.txt
>>> deleted file mode 100644
>>> index 169b32e4ee4e..000000000000
>>> --- a/Documentation/devicetree/bindings/display/ilitek,ili9341.txt
>>> +++ /dev/null
>>> @@ -1,27 +0,0 @@
>>> -Ilitek ILI9341 display panels
>>> -
>>> -This binding is for display panels using an Ilitek ILI9341 controller in SPI
>>> -mode.
>>> -
>>> -Required properties:
>>> -- compatible: "adafruit,yx240qv29", "ilitek,ili9341"
>>> -- dc-gpios: D/C pin
>>> -- reset-gpios: Reset pin
>>> -
>>> -The node for this driver must be a child node of a SPI controller, hence
>>> -all mandatory properties described in ../spi/spi-bus.txt must be specified.
>>> -
>>> -Optional properties:
>>> -- rotation: panel rotation in degrees counter clockwise (0,90,180,270)
>>> -- backlight: phandle of the backlight device attached to the panel
>>> -
>>> -Example:
>>> - display@0{
>>> - compatible = "adafruit,yx240qv29", "ilitek,ili9341";
>>> - reg = <0>;
>>> - spi-max-frequency = <32000000>;
>>> - dc-gpios = <&gpio0 9 GPIO_ACTIVE_HIGH>;
>>> - reset-gpios = <&gpio0 8 GPIO_ACTIVE_HIGH>;
>>> - rotation = <270>;
>>> - backlight = <&backlight>;
>>> - };
>>> diff --git a/Documentation/devicetree/bindings/display/panel/ilitek,ili9341.yaml b/Documentation/devicetree/bindings/display/panel/ilitek,ili9341.yaml
>>> index 6058948a9764..94ca92878434 100644
>>> --- a/Documentation/devicetree/bindings/display/panel/ilitek,ili9341.yaml
>>> +++ b/Documentation/devicetree/bindings/display/panel/ilitek,ili9341.yaml
>>> @@ -23,6 +23,7 @@ properties:
>>> - enum:
>>> # ili9341 240*320 Color on stm32f429-disco board
>>> - st,sf-tc240t-9370-t
>>> + - adafruit,yx240qv29
>>> - const: ilitek,ili9341
>>>
>>> reg: true
>>> @@ -47,31 +48,50 @@ properties:
>>> vddi-led-supply:
>>> description: Voltage supply for the LED driver (1.65 .. 3.3 V)
>>>
>>> -additionalProperties: false
>>> +unevaluatedProperties: false
>>>
>>> required:
>>> - compatible
>>> - reg
>>> - dc-gpios
>>> - - port
>>> +
>>> +if:
>>> + properties:
>>> + compatible:
>>> + contains:
>>> + enum:
>>> + - st,sf-tc240t-9370-t
>>> +then:
>>> + required:
>>> + - port
>>>
>>> examples:
>>> - |+
>>> + #include <dt-bindings/gpio/gpio.h>
>>> spi {
>>> #address-cells = <1>;
>>> #size-cells = <0>;
>>> panel: display@0 {
>>> - compatible = "st,sf-tc240t-9370-t",
>>> - "ilitek,ili9341";
>>> - reg = <0>;
>>> - spi-3wire;
>>> - spi-max-frequency = <10000000>;
>>> - dc-gpios = <&gpiod 13 0>;
>>> - port {
>>> - panel_in: endpoint {
>>> - remote-endpoint = <&display_out>;
>>> - };
>>> - };
>>> - };
>>> + compatible = "st,sf-tc240t-9370-t",
>>> + "ilitek,ili9341";
>>> + reg = <0>;
>>> + spi-3wire;
>>> + spi-max-frequency = <10000000>;
>>> + dc-gpios = <&gpiod 13 0>;
>>> + port {
>>> + panel_in: endpoint {
>>> + remote-endpoint = <&display_out>;
>>> + };
>>> + };
>>> + };
>>> + display@1{
>>> + compatible = "adafruit,yx240qv29", "ilitek,ili9341";
>>> + reg = <1>;
>>> + spi-max-frequency = <10000000>;
>>> + dc-gpios = <&gpio0 9 GPIO_ACTIVE_HIGH>;
>>> + reset-gpios = <&gpio0 8 GPIO_ACTIVE_HIGH>;
>>> + rotation = <270>;
>>> + backlight = <&backlight>;
>>> };
>>> + };
>>> ...
>>>
>>
>>
>
>
>
>
next prev parent reply other threads:[~2022-06-28 16:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 19:39 [PATCH v2 00/16] Canaan devicetree fixes Conor Dooley
2022-06-27 19:39 ` [PATCH v2 01/16] dt-bindings: display: convert ilitek,ili9341.txt to dt-schema Conor Dooley
2022-06-28 15:00 ` Heiko Stübner
2022-06-28 15:04 ` Heiko Stübner
2022-06-28 16:49 ` Conor.Dooley [this message]
2022-06-27 19:39 ` [PATCH v2 02/16] dt-bindings: display: panel: allow ilitek,ili9341 in isolation Conor Dooley
2022-06-27 19:39 ` [PATCH v2 03/16] ASoC: dt-bindings: convert designware-i2s to dt-schema Conor Dooley
2022-06-27 19:39 ` [PATCH v2 04/16] spi: dt-bindings: dw-apb-ssi: update spi-{r,t}x-bus-width Conor Dooley
2022-06-27 20:21 ` Serge Semin
2022-06-28 15:26 ` Rob Herring
2022-06-27 19:39 ` [PATCH v2 05/16] dt-bindings: dma: add Canaan k210 to Synopsys DesignWare DMA Conor Dooley
2022-06-27 21:34 ` Serge Semin
2022-06-27 22:23 ` Conor.Dooley
2022-06-27 19:39 ` [PATCH v2 06/16] dt-bindings: timer: add Canaan k210 to Synopsys DesignWare timer Conor Dooley
2022-06-27 21:13 ` Serge Semin
2022-06-27 21:18 ` Conor Dooley
2022-06-27 19:39 ` [PATCH v2 07/16] dt-bindings: memory-controllers: add canaan k210 sram controller Conor Dooley
2022-06-27 19:39 ` [PATCH v2 08/16] riscv: dts: canaan: fix the k210's memory node Conor Dooley
2022-06-27 19:39 ` [PATCH v2 09/16] riscv: dts: canaan: add a specific compatible for k210's dma Conor Dooley
2022-06-27 19:39 ` [PATCH v2 10/16] riscv: dts: canaan: add a specific compatible for k210's timers Conor Dooley
2022-06-27 19:39 ` [PATCH v2 11/16] riscv: dts: canaan: fix mmc node names Conor Dooley
2022-06-27 19:40 ` [PATCH v2 12/16] riscv: dts: canaan: fix kd233 display spi frequency Conor Dooley
2022-06-27 19:40 ` [PATCH v2 13/16] riscv: dts: canaan: use custom compatible for k210 i2s Conor Dooley
2022-06-27 19:40 ` [PATCH v2 14/16] riscv: dts: canaan: remove spi-max-frequency from controllers Conor Dooley
2022-06-27 19:40 ` [PATCH v2 15/16] riscv: dts: canaan: fix bus {ranges,reg} warnings Conor Dooley
2022-06-27 19:40 ` [PATCH v2 16/16] riscv: dts: canaan: build all devicetress if SOC_CANAAN Conor Dooley
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=66f41fc5-9d9a-6c45-b0db-de33cc2b4051@microchip.com \
--to=conor.dooley@microchip.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=airlied@linux.ie \
--cc=alsa-devel@alsa-project.org \
--cc=aou@eecs.berkeley.edu \
--cc=broonie@kernel.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=daniel.lezcano@linaro.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dillon.minfei@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=fancer.lancer@gmail.com \
--cc=geert@linux-m68k.org \
--cc=heiko@sntech.de \
--cc=jee.heng.sia@intel.com \
--cc=joabreu@synopsys.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=mail@conchuod.ie \
--cc=masahiroy@kernel.org \
--cc=niklas.cassel@wdc.com \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).