Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1674528 > unrolled thread

Re: [PATCH v3 01/17] mfd: madera: Add register definitions for Cirrus Logic Madera codecs

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH v3 01/17] mfd: madera: Add register definitions for  Cirrus Logic Madera codecs Richard Fitzgerald <rf@opensource.wolfsonmicro.com> - 2017-06-26 10:40 +0200
    Re: [PATCH v3 01/17] mfd: madera: Add register definitions for  Cirrus Logic Madera codecs Mark Brown <broonie@kernel.org> - 2017-06-28 21:30 +0200
      Re: [PATCH v3 01/17] mfd: madera: Add register definitions for  Cirrus Logic Madera codecs Richard Fitzgerald <rf@opensource.wolfsonmicro.com> - 2017-06-29 11:20 +0200
        Re: [PATCH v3 01/17] mfd: madera: Add register definitions for  Cirrus Logic Madera codecs Mark Brown <broonie@kernel.org> - 2017-06-30 14:40 +0200

#1674528 — Re: [PATCH v3 01/17] mfd: madera: Add register definitions for Cirrus Logic Madera codecs

On Mon, 2017-06-05 at 11:07 +0100, Lee Jones wrote:
> On Fri, 02 Jun 2017, Richard Fitzgerald wrote:
> 
> > This patch adds a header file of register definitions for Cirrus
> > Logic "Madera" class codecs. These codecs are all based off a common
> > set of hardware IP so have a common register map (with a few minor
> > device-to-device variations). These are complex devices with a large
> > number of features and so have a correspondingly large register set.
> > The registers.h file has been auto-generated from the hardware register
> > definitions, stripped down to only registers we need to access from
> > the driver
> > 
> > Signed-off-by: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
> > ---
> > Changes since V2:
> > - Used new field names for IRQ1_STATUS_33 register
> > 
> >  MAINTAINERS                          |   10 +
> >  include/linux/mfd/madera/registers.h | 8832 ++++++++++++++++++++++++++++++++++
> 
> Crikey!
> 
> For my own reference:
>   Acked-for-MFD-by: Lee Jones <lee.jones@linaro.org>
>   

Can I suggest that you take this patch into the mfd tree? Other
subsystem maintainers will have to base on that but it avoids me keeping
emailing out nearly 9000 lines of register definitions each time I do an
update to the other patches in the chain.

[toc] | [next] | [standalone]

#1677107

[Multipart message — attachments visible in raw view] — view raw

On Mon, Jun 26, 2017 at 09:33:38AM +0100, Richard Fitzgerald wrote:
> On Mon, 2017-06-05 at 11:07 +0100, Lee Jones wrote:

> > For my own reference:
> >   Acked-for-MFD-by: Lee Jones <lee.jones@linaro.org>

> Can I suggest that you take this patch into the mfd tree? Other
> subsystem maintainers will have to base on that but it avoids me keeping
> emailing out nearly 9000 lines of register definitions each time I do an
> update to the other patches in the chain.

Yes, please!  It also helps other maintainers see that the early bits of
the series we depend on are making progress.

[toc] | [prev] | [next] | [standalone]

#1677546

On Wed, 2017-06-28 at 20:26 +0100, Mark Brown wrote:
> On Mon, Jun 26, 2017 at 09:33:38AM +0100, Richard Fitzgerald wrote:
> > On Mon, 2017-06-05 at 11:07 +0100, Lee Jones wrote:
> 
> > > For my own reference:
> > >   Acked-for-MFD-by: Lee Jones <lee.jones@linaro.org>
> 
> > Can I suggest that you take this patch into the mfd tree? Other
> > subsystem maintainers will have to base on that but it avoids me keeping
> > emailing out nearly 9000 lines of register definitions each time I do an
> > update to the other patches in the chain.
> 
> Yes, please!  It also helps other maintainers see that the early bits of
> the series we depend on are making progress.

I guess taking all the MFD code when Lee is happy with it would also be
acceptable? There's several multi-thousand-line files in there too.

There are build dependencies between the subsystems but I don't know how
the maintainers prefer to deal with that - keep the patches as a set or
cross-merge branches.

[toc] | [prev] | [next] | [standalone]

#1678767

[Multipart message — attachments visible in raw view] — view raw

On Thu, Jun 29, 2017 at 10:11:34AM +0100, Richard Fitzgerald wrote:

> There are build dependencies between the subsystems but I don't know how
> the maintainers prefer to deal with that - keep the patches as a set or
> cross-merge branches.

It's good to at least have the option to have the code in the subsystem
tree so that any API changes in the subsystem can update the new code.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web