From: George Stark <gnstark@salutedevices.com>
To: <ukleinek@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <neil.armstrong@linaro.org>,
<khilman@baylibre.com>, <jbrunet@baylibre.com>,
<martin.blumenstingl@googlemail.com>, <hkallweit1@gmail.com>
Cc: <linux-pwm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-amlogic@lists.infradead.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <kernel@salutedevices.com>,
George Stark <gnstark@salutedevices.com>
Subject: [PATCH v4 0/3] pwm: meson: add pwm support for A1
Date: Thu, 11 Jul 2024 02:41:13 +0300 [thread overview]
Message-ID: <20240710234116.2370655-1-gnstark@salutedevices.com> (raw)
Add support for Amlogic meson A1 SoC family PWM
Changes in v2:
add patch with optional power-domains to pwm bindings;
fix syntax in a1 bindigns patch:
- use enum over const for amlogic,meson-a1-pwm beacuse adding more devices here
are expected
- leave only base compatible amlogic,meson-s4-pwm in check section
dt_binding_check and dtbs_check run ok now;
previous version: [1]
Changes in v3:
squash power-domains patch into main bindigns patch
add conditional to bindings that power-domains property is required only for a1
previous version: [2]
Changes in v4:
split bindings patch into power-domains patch and new compatible patch
previous version: [3]
[1] https://lore.kernel.org/lkml/20240701130113.433169-3-gnstark@salutedevices.com/T/
[2] https://lore.kernel.org/lkml/20240701172016.523402-1-gnstark@salutedevices.com/T/
[3] https://lore.kernel.org/lkml/20240702123425.584610-1-gnstark@salutedevices.com/T/
George Stark (3):
dt-bindings: pwm: amlogic: Add optional power-domains
dt-bindings: pwm: amlogic: Add new bindings for meson A1 PWM
arm64: dts: meson: a1: add definitions for meson PWM
.../devicetree/bindings/pwm/pwm-amlogic.yaml | 17 ++
arch/arm64/boot/dts/amlogic/meson-a1.dtsi | 215 ++++++++++++++++++
2 files changed, 232 insertions(+)
--
2.25.1
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2024-07-10 23:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 23:41 George Stark [this message]
2024-07-10 23:41 ` [PATCH v4 1/3] dt-bindings: pwm: amlogic: Add optional power-domains George Stark
2024-07-10 23:41 ` [PATCH v4 2/3] dt-bindings: pwm: amlogic: Add new bindings for meson A1 PWM George Stark
2024-07-12 12:52 ` Rob Herring
2024-07-12 15:12 ` George Stark
2024-07-25 14:08 ` Conor Dooley
2024-09-10 8:01 ` Uwe Kleine-König
2024-09-10 16:08 ` Conor Dooley
2024-07-10 23:41 ` [PATCH v4 3/3] arm64: dts: meson: a1: add definitions for meson PWM George Stark
2024-09-11 21:58 ` George Stark
2024-07-18 13:09 ` [PATCH v4 0/3] pwm: meson: add pwm support for A1 George Stark
2024-07-19 7:20 ` Uwe Kleine-König
2024-07-19 11:22 ` George Stark
2024-09-12 9:29 ` (subset) " 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=20240710234116.2370655-1-gnstark@salutedevices.com \
--to=gnstark@salutedevices.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hkallweit1@gmail.com \
--cc=jbrunet@baylibre.com \
--cc=kernel@salutedevices.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=ukleinek@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