linux-rtc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: "Neil Armstrong" <neil.armstrong@linaro.org>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Kevin Hilman" <khilman@baylibre.com>,
	"Jerome Brunet" <jbrunet@baylibre.com>,
	"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
	"Alessandro Zummo" <a.zummo@towertech.it>,
	"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	"Thierry Reding" <thierry.reding@gmail.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Marc Zyngier" <maz@kernel.org>,
	"Linus Walleij" <linus.walleij@linaro.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"open list:ARM/Amlogic Meson..."
	<linux-amlogic@lists.infradead.org>,
	linux-pwm@vger.kernel.org, linux-rtc@vger.kernel.org,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH 0/8] soc: amlogic: switch bindings to yaml and adjust some dtbs's
Date: Tue, 24 Jan 2023 10:20:40 +0100	[thread overview]
Message-ID: <2aaa347b-da29-67e8-56e9-959de708e426@gmail.com> (raw)
In-Reply-To: <0e48405a-d4e7-92a8-339f-4be2f4ec1378@linaro.org>

On 24.01.2023 08:16, Neil Armstrong wrote:
> Hi Heiner,
> 
> Le 23/01/2023 à 22:22, Heiner Kallweit a écrit :
>> At first adjust some existing dtbs's so that they pass dtbs_check
>> after switching bindings to yaml.
> 
> Thanks for this patchset, but please drop patches 1, 3 & 4, and take
> in account the existing compatible usage in your new bindings like
> I did in my conversion patchset.
> 
> While we did remove some bad compatibles we introduced a few years ago,
> now the GXBB, GXL & GXM are now stable a aew LTS releases now and
> a few other projects uses them as-is (U-Boot, BSDs, ...) so changing
> the compatibles isn't an option anymore... and we can't know which
> one they use and how the implementation behaves we must document
> the existing usage without breaking any potential users (including linux).
> 
I wasn't aware of this. Thanks for the hint.
So I'll rework the schemas to cover current usage of compatible strings.

> Thanks,
> Neil
> 
Heiner
> 
> 
>>
>> Then switch further Amlogic Meson bindings to yaml.
>> Tested with make targets dt_binding_check and dtbs_check.
>>
>> Heiner Kallweit (8):
>>    arm64: dts: meson-gx: Remove invalid pwm compatible
>>    arm64: dts: amlogic: Fix non-compliant SD/SDIO node names
>>    arm64: dts: meson-gx: Set only one compatible string for mmc
>>    arm64: dts: amlogic: Remove invalid compatible string
>>      amlogic,meson-gpio-intc
>>    dt-bindings: rtc: Add Amlogic Meson vrtc controller binding
>>    dt-bindings: pwm: Add Amlogic Meson PWM binding
>>    dt-bindings: interrupt-controller: Add Amlogic Meson GPIO interrupt
>>      controller binding
>>    dt-bindings: pinctrl: Add Amlogic Meson pinctrl binding
>>
>>   .../amlogic,meson-gpio-intc.txt               |  38 ------
>>   .../amlogic,meson-gpio-intc.yaml              |  72 +++++++++++
>>   .../pinctrl/amlogic,meson-pinctrl.yaml        | 121 ++++++++++++++++++
>>   .../bindings/pinctrl/meson,pinctrl.txt        |  94 --------------
>>   .../devicetree/bindings/pwm/pwm-amlogic.yaml  |  61 +++++++++
>>   .../devicetree/bindings/pwm/pwm-meson.txt     |  29 -----
>>   .../bindings/rtc/amlogic,meson-vrtc.yaml      |  50 ++++++++
>>   .../bindings/rtc/rtc-meson-vrtc.txt           |  22 ----
>>   arch/arm64/boot/dts/amlogic/meson-axg.dtsi    |   5 +-
>>   .../boot/dts/amlogic/meson-g12-common.dtsi    |   7 +-
>>   arch/arm64/boot/dts/amlogic/meson-gx.dtsi     |  15 +--
>>   arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi   |   3 +-
>>   arch/arm64/boot/dts/amlogic/meson-gxl.dtsi    |   3 +-
>>   arch/arm64/boot/dts/amlogic/meson-s4.dtsi     |   3 +-
>>   arch/arm64/boot/dts/amlogic/meson-sm1.dtsi    |   3 +-
>>   15 files changed, 320 insertions(+), 206 deletions(-)
>>   delete mode 100644 Documentation/devicetree/bindings/interrupt-controller/amlogic,meson-gpio-intc.txt
>>   create mode 100644 Documentation/devicetree/bindings/interrupt-controller/amlogic,meson-gpio-intc.yaml
>>   create mode 100644 Documentation/devicetree/bindings/pinctrl/amlogic,meson-pinctrl.yaml
>>   delete mode 100644 Documentation/devicetree/bindings/pinctrl/meson,pinctrl.txt
>>   create mode 100644 Documentation/devicetree/bindings/pwm/pwm-amlogic.yaml
>>   delete mode 100644 Documentation/devicetree/bindings/pwm/pwm-meson.txt
>>   create mode 100644 Documentation/devicetree/bindings/rtc/amlogic,meson-vrtc.yaml
>>   delete mode 100644 Documentation/devicetree/bindings/rtc/rtc-meson-vrtc.txt
>>
> 
> 


  reply	other threads:[~2023-01-24  9:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23 21:22 [PATCH 0/8] soc: amlogic: switch bindings to yaml and adjust some dtbs's Heiner Kallweit
2023-01-23 21:23 ` [PATCH 1/8] arm64: dts: meson-gx: Remove invalid pwm compatible Heiner Kallweit
2023-01-23 21:24 ` [PATCH 2/8] arm64: dts: amlogic: Fix non-compliant SD/SDIO node names Heiner Kallweit
2023-01-24  7:17   ` Neil Armstrong
2023-01-23 21:25 ` [PATCH 3/8] arm64: dts: meson-gx: Set only one compatible string for mmc Heiner Kallweit
2023-01-23 21:27 ` [PATCH 4/8] arm64: dts: amlogic: Remove invalid compatible string amlogic,meson-gpio-intc Heiner Kallweit
2023-01-23 21:28 ` [PATCH 5/8] dt-bindings: rtc: Add Amlogic Meson vrtc controller binding Heiner Kallweit
2023-01-25 19:19   ` Rob Herring
2023-01-23 21:29 ` [PATCH 6/8] dt-bindings: pwm: Add Amlogic Meson PWM binding Heiner Kallweit
2023-01-24  1:22   ` Rob Herring
2023-01-25 19:22   ` Rob Herring
2023-01-23 21:30 ` [PATCH 7/8] dt-bindings: interrupt-controller: Add Amlogic Meson GPIO interrupt controller binding Heiner Kallweit
2023-01-24  1:22   ` Rob Herring
2023-01-24  7:03     ` Heiner Kallweit
2023-01-25 16:46       ` Rob Herring
2023-01-23 21:30 ` [PATCH 8/8] dt-bindings: pinctrl: Add Amlogic Meson pinctrl binding Heiner Kallweit
2023-01-24  1:22   ` Rob Herring
2023-01-24  7:14     ` Heiner Kallweit
2023-01-24  7:16 ` [PATCH 0/8] soc: amlogic: switch bindings to yaml and adjust some dtbs's Neil Armstrong
2023-01-24  9:20   ` Heiner Kallweit [this message]
2023-01-26  7:40   ` Uwe Kleine-König
2023-01-24  8:22 ` (subset) " Neil Armstrong
2023-01-25 22:24 ` [PATCH v2] dt-bindings: rtc: Convert Amlogic Meson vrtc controller binding Heiner Kallweit
2023-01-30 17:09   ` Rob Herring
2023-02-09 22:16   ` (subset) " Alexandre Belloni
2023-06-22  7:57 ` [PATCH 0/8] soc: amlogic: switch bindings to yaml and adjust some dtbs's Neil Armstrong

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=2aaa347b-da29-67e8-56e9-959de708e426@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@bootlin.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=maz@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=thierry.reding@gmail.com \
    --cc=u.kleine-koenig@pengutronix.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;
as well as URLs for NNTP newsgroup(s).