[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <22d74656-3243-82be-8475-6ed72eaaf35b@microchip.com>
Date: Thu, 15 Sep 2022 07:03:17 +0000
From: <Conor.Dooley@...rochip.com>
To: <u.kleine-koenig@...gutronix.de>
CC: <thierry.reding@...il.com>, <robh+dt@...nel.org>,
<krzysztof.kozlowski+dt@...aro.org>,
<Daire.McNamara@...rochip.com>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-pwm@...r.kernel.org>,
<linux-riscv@...ts.infradead.org>
Subject: Re: [PATCH v10 2/4] riscv: dts: fix the icicle's #pwm-cells
On 14/09/2022 20:59, Uwe Kleine-König wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> there are no phandles on that PWM, so there is nothing that needs a
> followup adaption.
> Reviewed-by: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
Hey Uwe,
Thanks for checking the pwm consumers :)
I assume you going to take the corresponding binding change via
either pwm-fixes or pwm-for-next, I think you can take the dts too, I
don't think the dependency I previously thought existed exists.
For that purpose:
Acked-by: Conor Dooley <conor.dooley@...rochip.com>
Thanks,
Conor.
Powered by blists - more mailing lists