From: Thierry Reding <thierry.reding@gmail.com>
To: Fabien Parent <fparent@baylibre.com>
Cc: linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-pwm@vger.kernel.org, matthias.bgg@gmail.com,
robh+dt@kernel.org, lee.jones@linaro.org,
u.kleine-koenig@pengutronix.de
Subject: Re: [PATCH 0/5] Add PWM support for MT8183 EVB
Date: Wed, 11 Nov 2020 21:27:34 +0100 [thread overview]
Message-ID: <20201111202734.GL6125@ulmo> (raw)
In-Reply-To: <20201019140705.1518822-1-fparent@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 375 bytes --]
On Mon, Oct 19, 2020 at 04:07:00PM +0200, Fabien Parent wrote:
> This patch series adds PWM to MT8183 EVB. MT8183 has 4 PWM channels.
>
> Fabien Parent (5):
> dt-bindings: pwm: pwm-mediatek: Add documentation for MT8183 SoC
> pwm: pwm-mediatek: always use bus clock
> pwm: pwm-mediatek: Add MT8183 SoC support
Applied these three patches, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-11-11 20:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 14:07 [PATCH 0/5] Add PWM support for MT8183 EVB Fabien Parent
2020-10-19 14:07 ` [PATCH 1/5] dt-bindings: pwm: pwm-mediatek: Add documentation for MT8183 SoC Fabien Parent
2020-10-19 14:31 ` Matthias Brugger
2020-10-26 13:38 ` Rob Herring
2020-10-19 14:07 ` [PATCH 2/5] pwm: pwm-mediatek: always use bus clock Fabien Parent
2020-10-19 14:27 ` Matthias Brugger
2020-10-19 14:07 ` [PATCH 3/5] pwm: pwm-mediatek: Add MT8183 SoC support Fabien Parent
2020-10-19 14:30 ` Matthias Brugger
2020-10-19 14:07 ` [PATCH 4/5] arm64: dts: mediatek: mt8183: add pwm node Fabien Parent
2020-10-19 14:07 ` [PATCH 5/5] arm64: dts: mediatek: mt8183-evb: add PWM support Fabien Parent
2020-11-11 20:27 ` Thierry Reding [this message]
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=20201111202734.GL6125@ulmo \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=fparent@baylibre.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--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).