linux-pwm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Binbin Zhou <zhoubinbin@loongson.cn>
To: "Binbin Zhou" <zhoubb.aaron@gmail.com>,
	"Huacai Chen" <chenhuacai@loongson.cn>,
	"Uwe Kleine-König" <ukleinek@kernel.org>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Conor Dooley" <conor+dt@kernel.org>
Cc: Huacai Chen <chenhuacai@kernel.org>,
	loongson-kernel@lists.loongnix.cn, linux-pwm@vger.kernel.org,
	devicetree@vger.kernel.org, Binbin Zhou <zhoubinbin@loongson.cn>
Subject: [PATCH v1 0/6] dt-bindings: pwm: Cleanup pwm-cells required twice
Date: Tue, 30 Apr 2024 15:32:01 +0800	[thread overview]
Message-ID: <cover.1714450308.git.zhoubinbin@loongson.cn> (raw)

Hi all:

When I was submitting the Loongson PWM dt-binding, Rob reminded me that
the pwm-cells property was already required in pwm.yaml and did not need
to be repeated.

This patchset attempts to clean up the required pwm-cells attribute twice.

Thanks.

Binbin Zhou (6):
  dt-bindings: pwm: bcm2835: Do not require pwm-cells twice
  dt-bindings: pwm: google,cros-ec: Do not require pwm-cells twice
  dt-bindings: pwm: marvell,pxa: Do not require pwm-cells twice
  dt-bindings: pwm: mediatek,mt2712: Do not require pwm-cells twice
  dt-bindings: pwm: mediatek,pwm-disp: Do not require pwm-cells twice
  dt-bindings: pwm: snps,dw-apb-timers: Do not require pwm-cells twice

 Documentation/devicetree/bindings/pwm/google,cros-ec-pwm.yaml    | 1 -
 Documentation/devicetree/bindings/pwm/marvell,pxa-pwm.yaml       | 1 -
 Documentation/devicetree/bindings/pwm/mediatek,mt2712-pwm.yaml   | 1 -
 Documentation/devicetree/bindings/pwm/mediatek,pwm-disp.yaml     | 1 -
 Documentation/devicetree/bindings/pwm/pwm-bcm2835.yaml           | 1 -
 .../devicetree/bindings/pwm/snps,dw-apb-timers-pwm2.yaml         | 1 -
 6 files changed, 6 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-04-30  7:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30  7:32 Binbin Zhou [this message]
2024-04-30  7:32 ` [PATCH v1 1/6] dt-bindings: pwm: bcm2835: Do not require pwm-cells twice Binbin Zhou
2024-04-30  7:32 ` [PATCH v1 2/6] dt-bindings: pwm: google,cros-ec: " Binbin Zhou
2024-04-30  7:32 ` [PATCH v1 3/6] dt-bindings: pwm: marvell,pxa: " Binbin Zhou
2024-04-30  7:32 ` [PATCH v1 4/6] dt-bindings: pwm: mediatek,mt2712: " Binbin Zhou
2024-04-30  7:32 ` [PATCH v1 5/6] dt-bindings: pwm: mediatek,pwm-disp: " Binbin Zhou
2024-04-30  7:32 ` [PATCH v1 6/6] dt-bindings: pwm: snps,dw-apb-timers: " Binbin Zhou
2024-04-30 16:58 ` [PATCH v1 0/6] dt-bindings: pwm: Cleanup pwm-cells required twice Conor Dooley
2024-04-30 17:16 ` Rob Herring
2024-05-01  9:58 ` Uwe Kleine-König
2024-05-07  5:32   ` Binbin Zhou

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=cover.1714450308.git.zhoubinbin@loongson.cn \
    --to=zhoubinbin@loongson.cn \
    --cc=chenhuacai@kernel.org \
    --cc=chenhuacai@loongson.cn \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=loongson-kernel@lists.loongnix.cn \
    --cc=robh+dt@kernel.org \
    --cc=ukleinek@kernel.org \
    --cc=zhoubb.aaron@gmail.com \
    /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).