mbox series

[v2,0/2] Add support for texas dac121c081 to the dac5571 driver

Message ID 42db911c-5eba-0511-3e8c-8011a2a5b44a@axentia.se (mailing list archive)
Headers show
Series Add support for texas dac121c081 to the dac5571 driver | expand

Message

Peter Rosin April 25, 2022, 8:46 p.m. UTC
Hi!

The new chip works much like the other chips supported by the driver, so
this is just adding another compatible to the list.

Chenages since v1:
- Guenter Roeck noticed elsewhere that my mail setup was botched and
  that my patches were clobbered. Hopefully fixed. *blush*
- added tags from Sean Nyekjaer and Rob Herring

Cheers,
Peter

Peter Rosin (2):
  dt-bindings: iio: ti-dac5571: Add ti,dac121c081
  iio: dac: ti-dac5571: add support for ti,dac121c081

 Documentation/devicetree/bindings/iio/dac/ti,dac5571.yaml | 1 +
 drivers/iio/dac/Kconfig                                   | 2 +-
 drivers/iio/dac/ti-dac5571.c                              | 3 +++
 3 files changed, 5 insertions(+), 1 deletion(-)

Comments

Jonathan Cameron April 28, 2022, 7:44 p.m. UTC | #1
On Mon, 25 Apr 2022 22:46:30 +0200
Peter Rosin <peda@axentia.se> wrote:

> Hi!
> 
> The new chip works much like the other chips supported by the driver, so
> this is just adding another compatible to the list.
> 
> Chenages since v1:
> - Guenter Roeck noticed elsewhere that my mail setup was botched and
>   that my patches were clobbered. Hopefully fixed. *blush*
> - added tags from Sean Nyekjaer and Rob Herring

Applied.  Thanks

Jonathan

> 
> Cheers,
> Peter
> 
> Peter Rosin (2):
>   dt-bindings: iio: ti-dac5571: Add ti,dac121c081
>   iio: dac: ti-dac5571: add support for ti,dac121c081
> 
>  Documentation/devicetree/bindings/iio/dac/ti,dac5571.yaml | 1 +
>  drivers/iio/dac/Kconfig                                   | 2 +-
>  drivers/iio/dac/ti-dac5571.c                              | 3 +++
>  3 files changed, 5 insertions(+), 1 deletion(-)
>
Jonathan Cameron May 1, 2022, 6:03 p.m. UTC | #2
On Thu, 28 Apr 2022 20:44:39 +0100
Jonathan Cameron <jic23@kernel.org> wrote:

> On Mon, 25 Apr 2022 22:46:30 +0200
> Peter Rosin <peda@axentia.se> wrote:
> 
> > Hi!
> > 
> > The new chip works much like the other chips supported by the driver, so
> > this is just adding another compatible to the list.
> > 
> > Chenages since v1:
> > - Guenter Roeck noticed elsewhere that my mail setup was botched and
> >   that my patches were clobbered. Hopefully fixed. *blush*
> > - added tags from Sean Nyekjaer and Rob Herring  
> 
> Applied.  Thanks

Backed out temporarily because they have crossed with a fix (that I'd
forgotten about) and were requiring a non trivial merge in linux-next.

https://patchwork.kernel.org/project/linux-iio/patch/20220324234340.32402-1-laurent.pinchart@ideasonboard.com/

Hopefully that will get resolved in my upstream fairly soon and I can
fix this one up whilst applying it myself.

Thanks,

Jonathan



> 
> Jonathan
> 
> > 
> > Cheers,
> > Peter
> > 
> > Peter Rosin (2):
> >   dt-bindings: iio: ti-dac5571: Add ti,dac121c081
> >   iio: dac: ti-dac5571: add support for ti,dac121c081
> > 
> >  Documentation/devicetree/bindings/iio/dac/ti,dac5571.yaml | 1 +
> >  drivers/iio/dac/Kconfig                                   | 2 +-
> >  drivers/iio/dac/ti-dac5571.c                              | 3 +++
> >  3 files changed, 5 insertions(+), 1 deletion(-)
> >   
>
Peter Rosin May 12, 2022, 8:59 a.m. UTC | #3
HI!

2022-05-01 at 20:03, Jonathan Cameron wrote:
> On Thu, 28 Apr 2022 20:44:39 +0100
> Jonathan Cameron <jic23@kernel.org> wrote:
> 
>> On Mon, 25 Apr 2022 22:46:30 +0200
>> Peter Rosin <peda@axentia.se> wrote:
>>
>>> Hi!
>>>
>>> The new chip works much like the other chips supported by the driver, so
>>> this is just adding another compatible to the list.
>>>
>>> Chenages since v1:
>>> - Guenter Roeck noticed elsewhere that my mail setup was botched and
>>>   that my patches were clobbered. Hopefully fixed. *blush*
>>> - added tags from Sean Nyekjaer and Rob Herring  
>>
>> Applied.  Thanks
> 
> Backed out temporarily because they have crossed with a fix (that I'd
> forgotten about) and were requiring a non trivial merge in linux-next.
> 
> https://patchwork.kernel.org/project/linux-iio/patch/20220324234340.32402-1-laurent.pinchart@ideasonboard.com/
> 
> Hopefully that will get resolved in my upstream fairly soon and I can
> fix this one up whilst applying it myself.

Looks like it might be time to bring this one in from the cold?

Cheers,
Peter
Jonathan Cameron May 12, 2022, 1:02 p.m. UTC | #4
On Thu, 12 May 2022 10:59:48 +0200
Peter Rosin <peda@axentia.se> wrote:

> HI!
> 
> 2022-05-01 at 20:03, Jonathan Cameron wrote:
> > On Thu, 28 Apr 2022 20:44:39 +0100
> > Jonathan Cameron <jic23@kernel.org> wrote:
> >   
> >> On Mon, 25 Apr 2022 22:46:30 +0200
> >> Peter Rosin <peda@axentia.se> wrote:
> >>  
> >>> Hi!
> >>>
> >>> The new chip works much like the other chips supported by the driver, so
> >>> this is just adding another compatible to the list.
> >>>
> >>> Chenages since v1:
> >>> - Guenter Roeck noticed elsewhere that my mail setup was botched and
> >>>   that my patches were clobbered. Hopefully fixed. *blush*
> >>> - added tags from Sean Nyekjaer and Rob Herring    
> >>
> >> Applied.  Thanks  
> > 
> > Backed out temporarily because they have crossed with a fix (that I'd
> > forgotten about) and were requiring a non trivial merge in linux-next.
> > 
> > https://patchwork.kernel.org/project/linux-iio/patch/20220324234340.32402-1-laurent.pinchart@ideasonboard.com/
> > 
> > Hopefully that will get resolved in my upstream fairly soon and I can
> > fix this one up whilst applying it myself.  
> 
> Looks like it might be time to bring this one in from the cold?

Nearly.  I have a pull request out to Greg. Once he's taken that
I'll fastforward the togreg branch to include the fix and
can then apply this.

Jonathan

> 
> Cheers,
> Peter
Jonathan Cameron May 22, 2022, 11:57 a.m. UTC | #5
On Thu, 12 May 2022 14:02:32 +0100
Jonathan Cameron <Jonathan.Cameron@Huawei.com> wrote:

> On Thu, 12 May 2022 10:59:48 +0200
> Peter Rosin <peda@axentia.se> wrote:
> 
> > HI!
> > 
> > 2022-05-01 at 20:03, Jonathan Cameron wrote:  
> > > On Thu, 28 Apr 2022 20:44:39 +0100
> > > Jonathan Cameron <jic23@kernel.org> wrote:
> > >     
> > >> On Mon, 25 Apr 2022 22:46:30 +0200
> > >> Peter Rosin <peda@axentia.se> wrote:
> > >>    
> > >>> Hi!
> > >>>
> > >>> The new chip works much like the other chips supported by the driver, so
> > >>> this is just adding another compatible to the list.
> > >>>
> > >>> Chenages since v1:
> > >>> - Guenter Roeck noticed elsewhere that my mail setup was botched and
> > >>>   that my patches were clobbered. Hopefully fixed. *blush*
> > >>> - added tags from Sean Nyekjaer and Rob Herring      
> > >>
> > >> Applied.  Thanks    
> > > 
> > > Backed out temporarily because they have crossed with a fix (that I'd
> > > forgotten about) and were requiring a non trivial merge in linux-next.
> > > 
> > > https://patchwork.kernel.org/project/linux-iio/patch/20220324234340.32402-1-laurent.pinchart@ideasonboard.com/
> > > 
> > > Hopefully that will get resolved in my upstream fairly soon and I can
> > > fix this one up whilst applying it myself.    
> > 
> > Looks like it might be time to bring this one in from the cold?  
> 
> Nearly.  I have a pull request out to Greg. Once he's taken that
> I'll fastforward the togreg branch to include the fix and
> can then apply this.

Now we are good. Applied to the togreg branch of iio.git and added the
tweak needed to provide data in the of_device_id table.

Unfortunately timing is against me this time, and unless the merge window
is delayed this is now 5.20 material.

Thanks,

Jonathan

> 
> Jonathan
> 
> > 
> > Cheers,
> > Peter  
>