From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: linux-pwm@vger.kernel.org, baylibre-upstreaming@groups.io,
linux-kernel@vger.kernel.org, thierry.reding@gmail.com,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/3] pwm: meson: Add clock source configuration for Meson G12A
Date: Sat, 27 Apr 2019 22:29:21 +0200 [thread overview]
Message-ID: <CAFBinCB9WS650JpuyGyjjOE=LNbChOdhAyb+qJMYWGosyMUa=w@mail.gmail.com> (raw)
In-Reply-To: <20190423133646.5705-3-narmstrong@baylibre.com>
On Tue, Apr 23, 2019 at 3:37 PM Neil Armstrong <narmstrong@baylibre.com> wrote:
>
> For the PWM controller in the Meson G12A SoC, the EE domain and AO domain
> have different clock sources. This patch tries to describe them in the
> DT compatible data. The two AO PWM controller has different clock source,
> but the first AO controller (A & B) can reuse the AXG parents name.
>
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2019-04-27 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 13:36 [PATCH v2 0/3] pwm: Add support for Amlogic Meson G12A Neil Armstrong
2019-04-23 13:36 ` [PATCH v2 1/3] dt-bindings: pwm: Update bindings for the Meson G12A Family Neil Armstrong
2019-04-27 20:28 ` Martin Blumenstingl
2019-05-01 20:01 ` Rob Herring
2019-04-23 13:36 ` [PATCH v2 2/3] pwm: meson: Add clock source configuration for Meson G12A Neil Armstrong
2019-04-27 20:29 ` Martin Blumenstingl [this message]
2019-04-23 13:36 ` [PATCH v2 3/3] arm64: dts: meson-g12a: Add PWM nodes Neil Armstrong
2019-05-08 22:42 ` Kevin Hilman
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='CAFBinCB9WS650JpuyGyjjOE=LNbChOdhAyb+qJMYWGosyMUa=w@mail.gmail.com' \
--to=martin.blumenstingl@googlemail.com \
--cc=baylibre-upstreaming@groups.io \
--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=narmstrong@baylibre.com \
--cc=thierry.reding@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).