Re: [PATCH v2 0/3] pwm: add pwm AO on meson gx

[Jeremy Kerr <jk@ozlabs.org>]

[-- Attachment #1: Type: text/plain, Size: 2795 bytes --]

Hi all,

I'm just on a short holiday at the moment, but will check this out when I'm back home, early next week.

Cheers,


Jeremy

On 6 July 2017 5:17:43 pm AWST, Thierry Reding <thierry.reding@gmail.com> wrote:
>On Thu, Jul 06, 2017 at 11:02:20AM +0200, Jerome Brunet wrote:
>> On Thu, 2017-07-06 at 08:59 +0200, Thierry Reding wrote:
>> > On Thu, Jun 08, 2017 at 02:24:13PM +0200, Jerome Brunet wrote:
>> > > The pwms found in the AO domain of the meson gx family have
>different
>> > > clock sources than the ones found in the EE domain. The AO pwms
>only
>> > > have 2 connected clock input which are clk81 and the crytal.
>> > > 
>> > > This patchset adds the necessary compatible and the clock data
>for it.
>> > > 
>> > > Changes since v1: [0]
>> > > * Correct clock source order for gxbb pwm ao. Documenation shows
>xtal as
>> > >   source #1 while it is actually source #0
>> > > * Add patch 3 to fix pwm calculation. Issue while testing pwm
>with clk81
>> > >   as clock source.
>> > > 
>> > >
>[0]:  https://lkml.kernel.org/r/20170607133013.4766-1-jbrunet@baylibre.com
>> > > 
>> > > Jerome Brunet (3):
>> > >   dt-bindings: pwm: meson: add comptabible for gxbb ao pwms
>> > >   pwm: meson: add compatible for the gxbb ao pwms
>> > >   pwm: meson: improve pwm calculation precision.
>> > > 
>> > >  .../devicetree/bindings/pwm/pwm-meson.txt          |  4 +-
>> > >  drivers/pwm/pwm-meson.c                            | 47
>+++++++++++++++++
>> > > -----
>> > >  2 files changed, 41 insertions(+), 10 deletions(-)
>> > 
>> > For some reason the Author field keeps getting set to:
>> > 
>> > 	jbrunet <jbrunet@baylibre.com>
>> > 
>> > It seems like the headers are correct, so maybe this is patchwork
>> > messing things up?
>> 
>> And it strikes again ... :(
>> I already had the issue with https://patchwork.kernel.org a few month
>ago.
>> I have contacted the kernel.org helpdesk about it and here is the
>explanation:
>> 
>> "Patchwork treats users and patch submitters slightly differently, so
>once your
>> entry is created upon first patch submission, it sticks forever. I've
>adjusted
>> your entry manually per your request."
>> 
>> So my very first patch on the ML must have been malformed somehow.
>> 
>> > 
>> > Anyway, I've applied the series and manually fixed up the Author
>field.
>> 
>> Thanks a lot for this ! 
>> Any idea who I may contact to get this "manual adjustment" done on
>https://patch
>> work.ozlabs.org/ ?
>
>I /think/ Jeremy Kerr (To'ed) would be a good person to contact about
>this.
>
>Jeremy, anything you can do about this?
>
>Thanks,
>Thierry

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 4019 bytes --]