From: <Conor.Dooley@microchip.com>
To: <u.kleine-koenig@pengutronix.de>
Cc: <thierry.reding@gmail.com>, <lee.jones@linaro.org>,
<Daire.McNamara@microchip.com>, <linux-kernel@vger.kernel.org>,
<linux-pwm@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
<Conor.Dooley@microchip.com>
Subject: Re: [PATCH v3 0/2] Add support for Microchip's pwm fpga core
Date: Fri, 17 Jun 2022 13:13:11 +0000 [thread overview]
Message-ID: <13e546a2-37d8-f0a2-4651-d6ecf60de0ef@microchip.com> (raw)
In-Reply-To: <20220617130931.3rdaj4p3d54p4ynz@pengutronix.de>
On 17/06/2022 14:09, Uwe Kleine-König wrote:
> Hello,
>
> On Fri, Jun 17, 2022 at 11:50:13AM +0000, Conor.Dooley@microchip.com wrote:
>> On 17/06/2022 12:44, Conor Dooley wrote:
>>> Hey Uwe,
>>> Got a ~v2~ v3 for you...
>>> I added some comments explaining the calculations and a documentation link
>>> so hopefully things are a bit easier to follow.
>>>
>>> Code wise, I went through and sorted out a bunch of issues that cycling
>>> through the different periods/duties threw up. Along the way I found
>>> some other problems - especially with the longer periods which I have
>>> fixed. I also added a write to the sync register in the apply function,
>>> which will resolve to a NOP for channels without "shadow registers".
>>>
>>> Other than that, I managed to ditch the mchp_core_pwm_registers struct
>>> entirely but had to add a short delay before reading back the registers
>>> in order to compute the duty.
>>>
>>> Thanks,
>>> Conor.
>>
>> *sigh* yet again I forgot to mention the potential maintainers conflict
>> with spi-next..
>
> I'm not a maintainer of a very active subsystem where MAINTAINER
> conflicts are normal, but my expectation up to now was that conflicts in
> that file are quite usual and trivial to resolve such that mentioning
> these isn't very important.
>
Yeah, I figured such conflicts were rather normal but felt like it was
better to say it just in case.
Thanks,
Conor.
prev parent reply other threads:[~2022-06-17 13:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 11:44 Conor Dooley
2022-06-17 11:44 ` [PATCH v3 1/2] pwm: add microchip soft ip corePWM driver Conor Dooley
2022-07-01 9:51 ` Uwe Kleine-König
2022-07-01 17:56 ` Conor.Dooley
2022-06-17 11:44 ` [PATCH v3 2/2] MAINTAINERS: add pwm to PolarFire SoC entry Conor Dooley
2022-07-01 12:56 ` Uwe Kleine-König
2022-06-17 11:50 ` [PATCH v3 0/2] Add support for Microchip's pwm fpga core Conor.Dooley
2022-06-17 13:09 ` Uwe Kleine-König
2022-06-17 13:13 ` Conor.Dooley [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=13e546a2-37d8-f0a2-4651-d6ecf60de0ef@microchip.com \
--to=conor.dooley@microchip.com \
--cc=Daire.McNamara@microchip.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=thierry.reding@gmail.com \
--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
all inboxes | Powered by JetHome®