From: Simon Glass <sjg@chromium.org>
To: Billy Tsai <billy_tsai@aspeedtech.com>
Cc: Ryan Chen <ryan_chen@aspeedtech.com>,
Chia-Wei Wang <chiawei_wang@aspeedtech.com>,
Aspeed BMC SW team <BMC-SW@aspeedtech.com>,
Joel Stanley <joel@jms.id.au>,
Ramon Fried <rfried.dev@gmail.com>,
dylan_hung@aspeedtech.com, dan.sneddon@microchip.com,
Alper Nebi Yasak <alpernebiyasak@gmail.com>,
U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH 1/3] pwm: Add Aspeed ast2600 PWM support
Date: Fri, 11 Mar 2022 19:43:46 -0700 [thread overview]
Message-ID: <CAPnjgZ2LS96XaNdgEbux9j2P9amkFRf_k3_GG8m7sMAMmVxJVQ@mail.gmail.com> (raw)
In-Reply-To: <20220308030407.17197-2-billy_tsai@aspeedtech.com>
On Mon, 7 Mar 2022 at 20:02, Billy Tsai <billy_tsai@aspeedtech.com> wrote:
>
> This patch add the support of PWM controller which can be found at aspeed
> ast2600 soc. The pwm supoorts up to 16 channels and it's part function
> of multi-function device "pwm-tach controller".
>
> Signed-off-by: Billy Tsai <billy_tsai@aspeedtech.com>
> ---
> drivers/pwm/Kconfig | 8 ++
> drivers/pwm/Makefile | 1 +
> drivers/pwm/pwm-aspeed.c | 251 +++++++++++++++++++++++++++++++++++++++
> 3 files changed, 260 insertions(+)
> create mode 100644 drivers/pwm/pwm-aspeed.c
Reviewed-by: Simon Glass <sjg@chromium.org>
next prev parent reply other threads:[~2022-03-12 2:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 3:04 [PATCH 0/3] Support pwm driver for aspeed ast26xx Billy Tsai
2022-03-08 3:04 ` [PATCH 1/3] pwm: Add Aspeed ast2600 PWM support Billy Tsai
2022-03-12 2:43 ` Simon Glass [this message]
2022-03-14 0:20 ` ChiaWei Wang
2022-03-26 2:46 ` Tom Rini
2022-03-08 3:04 ` [PATCH 2/3] pinctrl: Add the pinctrl setting for PWM Billy Tsai
2022-03-12 2:43 ` Simon Glass
2022-03-14 0:20 ` ChiaWei Wang
2022-03-26 2:46 ` Tom Rini
2022-03-08 3:04 ` [PATCH 3/3] ARM: dts: ast2600: Add PWM to device tree Billy Tsai
2022-03-12 2:43 ` Simon Glass
2022-03-14 0:21 ` ChiaWei Wang
2022-03-26 2:46 ` Tom Rini
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=CAPnjgZ2LS96XaNdgEbux9j2P9amkFRf_k3_GG8m7sMAMmVxJVQ@mail.gmail.com \
--to=sjg@chromium.org \
--cc=BMC-SW@aspeedtech.com \
--cc=alpernebiyasak@gmail.com \
--cc=billy_tsai@aspeedtech.com \
--cc=chiawei_wang@aspeedtech.com \
--cc=dan.sneddon@microchip.com \
--cc=dylan_hung@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=rfried.dev@gmail.com \
--cc=ryan_chen@aspeedtech.com \
--cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.