Re: [PATCH v7 2/7] dt-bindings: iio: adc: microchip,mcp3564: Add spi-device-addr

[Janani Sunil]

On 8/1/26 03:41, Jonathan Cameron wrote:
> On Thu, 30 Jul 2026 19:02:08 +0100
> Conor Dooley <conor@xxxxxxxxxx> wrote:
>
> > On Thu, Jul 30, 2026 at 12:09:29AM +0100, Jonathan Cameron wrote:
> > > On Wed, 29 Jul 2026 21:47:45 +0100
> > > Conor Dooley <conor@xxxxxxxxxx> wrote:
> > >    
> > > > On Tue, Jul 28, 2026 at 10:17:19PM +0100, Jonathan Cameron wrote:
> > > > > On Tue, 28 Jul 2026 17:00:55 +0100
> > > > > Conor Dooley <conor@xxxxxxxxxx> wrote:
> > > > >      
> > > > > > On Sat, Jul 25, 2026 at 11:07:39PM +0100, Jonathan Cameron wrote:
> > > > > > > On Sat, 25 Jul 2026 15:57:07 -0500
> > > > > > > David Lechner <dlechner@xxxxxxxxxxxx> wrote:
> > > > > > >        
> > > > > > > > On 7/22/26 2:54 AM, Janani Sunil wrote:
> > > > > > > > > Add the generic spi-device-addr property to the binding and deprecate
> > > > > > > > > the existing vendor specific microchip,hw-device-address property.
> > > > > > > > >
> > > > > > > > > Signed-off-by: Janani Sunil <janani.sunil@xxxxxxxxxx>
> > > > > > > > > ---
> > > > > > > > >   .../devicetree/bindings/iio/adc/microchip,mcp3564.yaml         | 10 ++++++++--
> > > > > > > > >   1 file changed, 8 insertions(+), 2 deletions(-)
> > > > > > > > >
> > > > > > > > > diff --git a/Documentation/devicetree/bindings/iio/adc/microchip,mcp3564.yaml b/Documentation/devicetree/bindings/iio/adc/microchip,mcp3564.yaml
> > > > > > > > > index 675319276197..de1ea289e7f5 100644
> > > > > > > > > --- a/Documentation/devicetree/bindings/iio/adc/microchip,mcp3564.yaml
> > > > > > > > > +++ b/Documentation/devicetree/bindings/iio/adc/microchip,mcp3564.yaml
> > > > > > > > > @@ -80,6 +80,7 @@ properties:
> > > > > > > > >       $ref: /schemas/types.yaml#/definitions/uint32
> > > > > > > > >       minimum: 0
> > > > > > > > >       maximum: 3
> > > > > > > > > +    deprecated: true
> > > > > > > > >       description:
> > > > > > > > >         The address is set on a per-device basis by fuses in the factory,
> > > > > > > > >         configured on request. If not requested, the fuses are set for 0x1.
> > > > > > > > > @@ -91,6 +92,12 @@ properties:
> > > > > > > > >         clocking of the device address (BITS[7:6] - top two bits of COMMAND BYTE
> > > > > > > > >         which is first one on the wire).
> > > > > > > > >   
> > > > > > > > > +  spi-device-addr:
> > > > > > > > > +    maxItems: 1
> > > > > > > > Does it not make sense to all for more than once device connected
> > > > > > > > to the same CS here? I would expect maxItems to be 4 to match the
> > > > > > > > number of possible addresses.
> > > > > > > >        
> > > > > > > I think for this part their isn't a reason to aggregate.
> > > > > > > No magic accesses that touch them all at once.  So this hits
> > > > > > > exactly the point you raised about how we set the address for
> > > > > > > more than one of them.
> > > > > > No David is actually right here, and maxitems should be 4.
> > > > > > Setting the address for multiple was already discussed I thought, with
> > > > > > the property being an array and each compatible being used to determine
> > > > > > the "stride" between entries based on the number of supported channels?
> > > > > I don't think that applies for this device or at least to do so
> > > > > is a major driver rewrite, not a simple binding change.  Probably we'd
> > > > Whether or not it is a big driver change, the binding should represent
> > > > what the hardware is capable of.
> > > >    
> > > > > just add a bus and hang the 4 instances off it. They are running on own
> > > > > timing etc so we can't grab data across all of them in any sort of
> > > > > synchronous way - the clocks will probably drift over time etc.
> > > > Did I miss something about the ADI devices in this thread where they
> > > > have some multicast ability to read all devices at once? I thought that
> > > > that was a different series where each device had dedicated mosi and
> > > > miso lines, rather than the shared ones here. I didn't think the ad5529r
> > > > did anything special from my reading of the datasheet but I'm not the
> > > > expert in this area!
> > > It's a DAC so other way around but yes they have exactly that in the section:
> > > https://www.analog.com/media/en/technical-documentation/data-sheets/ad5529r.pdf
> > >
> > > 	Register Details: Hotpath DAC registermap.
> > >
> > > The is a brief description earlier of the whole feature that might
> > > serve for this discussion:
> > >
> > > "DAC HOTPATH
> > > The DAC hotpath is a dedicated register region that optimizes
> > > DAC updates in multidevice configurations where several AD5529R
> > > devices share a common SPI bus. It reduces the number of SPI
> > > frames required to write DAC data and supports synchronized
> > > output updates across devices. In single device systems, the hotpath
> > > offers no advantage over the standard register map and can be
> > > disregarded."
> > >
> > > As an example
> > > MULTI DEVICE SW LDAC MODE 0 REGISTER
> > > "This register sends a software LDAC update to the selected devices
> > > that share the SPI lines but have different addresses, using the ID0
> > > and ID1 pins. The selection is done on a per-device basis corresponding
> > > to the configured bit field."
> > >
> > > This one triggers all selected DACs (there is bit corresponding to
> > > each address) to update in sync. (Lets put aside normal systems
> > > where an LDAC gpio is wired to multiple devices as that is a whole
> > > different problem).
> > >
> > >
> > > It is this part that is driving the suggestion of having
> > > a combined device representation for multiple physical devices.
> > > In practice it is very similar to chained devices where we do that
> > > already in that a longer access sequence is used to talk to multiple
> > > devices at once.
> > Ah I see. I definitely missed this section.
> >
> > > Those SPI messages do not carry the address (or they are ignored - I didn't
> > > dig into the mechanism).
> > It's definitely hard to tell this at a glance, nor does it really
> > matter.
> >
> > > > > They are independent devices (think of them using spi-device-address
> > > > > like an i2c address) -  so why have one DT node for up to 4 of
> > > > > them?  Note this is different from the AD5529R where the design
> > > > > is intended for them to operate as one single larger device.
> > > > I don't buy this argument, I just don't see what differs between the
> > > > devices. The microchip datasheet I read talked about using 3 devices to
> > > > measure 3 phase power setups (I think that's what it was) which is, in
> > > > my book, evidence that they're not just intended to be used
> > > > independently.
> > > Sure but that could just as easily be done with normal SPI and 3 chip
> > > selects. For these devices there is no broadcast write magic (I think
> > > anyway!)
> > I don't think there's any magic, and yes I do buy the argument that it
> > could be done normally.
> > Quite frankly, I don't know why the device works like this other than
> > pin saving. Probably some customer asked for it rather than there being
> > a generic use case.
> >
> > > > That said, the more this discussion goes on, the more I think that
> > > > merging the devices into a single node is a mistake. Logically there may
> > > > be one device, but really there are one to four devices. Doing the
> > > > logical device thing is nice maybe for software but I no longer think
> > > > that it represents the hardware correctly. I know this will cause
> > > > problems with registration of devices in the SPI core, but we need to
> > > > pick one representation for these devices that fits in all usecases
> > > > and with the things brought up in the other mail I am having a lot of
> > > > doubts.
> > > This wasn't about use cases as such but the broadcast like facilities the
> > > ADI parts have which to me smell like the main reason you'd put them on
> > > a single bus and use this feature in the first place - you are making
> > > one big DAC from multiple chips.
> > No, I think the use case bit is important. The representation (in dt)
> > shouldn't change because someone wants to use the device as one big dac
> > or 4 smaller dacs. The multicast thing does certainly lend a lot of
> > weight to treating the dacs as one device, so I guess that would be the
> > designated representation for this dac.
> > But then I don't see why the microchip devices couldn't be dealt with in
> > the same way, even if they don't have multicast, in order to create a
> > single consistent way of describing the devices.
> How about we kick this down the road. Leave the two microchip devices
> alone for now with their vendor binding (which we have to carry on supporting
> anyway) and just do the AD part.  For future devices we can push towards
> that model if they have such a device-address feature.
>
> I don't mind changing the microchip parts in principle, but it is going
> to be a non trivial change and I'd certainly be nervous to make it without test
> parts
>
> Of course if anyone does mix parts we have to think again.
>
> Jonathan

Hi All,

Based on the discussion for v8, I plan to:

1) Drop the Microchip-related patches from this series
2) Keep the spi-device-addr property and the AD5529R binding/driver and represent AD5529R sharing one CS as one device using the address array.

This would reduce v8 into just three patches related to the AD5529r.

Please let me know if I missed anything.

Regards,
Jan