From: Thierry Reding <thierry.reding@gmail.com>
To: Aidan MacDonald <aidanmacdonald.0x0@gmail.com>
Cc: paul@crapouillou.net, robh+dt@kernel.org,
linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: timer: Add PWM compatible for X1000 SoC
Date: Fri, 22 Apr 2022 17:54:42 +0200 [thread overview]
Message-ID: <YmLPwtJYRE+qI2oJ@orome> (raw)
In-Reply-To: <20220224234133.15708-1-aidanmacdonald.0x0@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
On Thu, Feb 24, 2022 at 11:41:33PM +0000, Aidan MacDonald wrote:
> The PWM hardware on the X1000 SoC is almost identical to other
> Ingenic SoCs, so it can be used with only minor driver changes.
>
> Signed-off-by: Aidan MacDonald <aidanmacdonald.0x0@gmail.com>
> ---
> It seems Thierry picked up the driver patch separately (thanks for
> that) so here's the DTS changes on their own. Would've uploaded a
> v2 sooner but I was busy the past couple weeks and couldn't spend
> any time on kernel stuff. I guess this isn't a v2 per se, but for
> completeness:
>
> v1: https://lore.kernel.org/linux-mips/20220209231141.20184-1-aidanmacdonald.0x0@gmail.com/
>
> Documentation/devicetree/bindings/timer/ingenic,tcu.yaml | 1 +
> 1 file changed, 1 insertion(+)
Looks like I also somehow ended up applying this snippet, though
possibly from the earlier patch.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-04-22 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 23:41 [PATCH v2 1/2] dt-bindings: timer: Add PWM compatible for X1000 SoC Aidan MacDonald
2022-02-24 23:41 ` [PATCH v2 2/2] mips: dts: ingenic: x1000: Add PWM device tree node Aidan MacDonald
2022-04-22 16:12 ` Thierry Reding
2022-04-22 17:53 ` Paul Cercueil
2022-04-22 15:54 ` 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=YmLPwtJYRE+qI2oJ@orome \
--to=thierry.reding@gmail.com \
--cc=aidanmacdonald.0x0@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=paul@crapouillou.net \
--cc=robh+dt@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 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.