Re: [PATCH v6 1/5] spi: dt-bindings: Add spi-device-addr peripheral property
Mark Brown <[email protected]>
| Newsgroups | org.kernel.vger.linux-spi,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-doc,org.kernel.vger.linux-iio,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Jul 16, 2026 at 11:22:19AM +0200, Nuno Sá wrote: > On Wed, Jul 15, 2026 at 02:37:12PM +0100, Mark Brown wrote: > > You still need to work out how the ID appears in the byte stream that > > gets sent to/from the device, that's way more information than just a > > number and not something the byte stream SPI offers is going to cope > > well with. > Not sure if I'm following you. Those ID pins just become something you > need to set on the spi_xfer. Or in Janani case, she's using regmap > reg_base in order to set the right thing depending on the address. I > would image this is always something that peripherals need to address in > terms of how the message/stream needs to be set. So my understanding is > that this should be pretty much transparent for the spi core. Oh, isn't that just multi-pin chip selects then: https://patch.msgid.link/[email protected]
signature.asc
(application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmpYzl4ACgkQJNaLcl1U h9D8uwf/exdzBvd6yn5UOVsD3+eaC/9G057ZONDF38P6m/7xH6Op5HHszAyQ7FMU nl8OpLnOpeI2aMd/h9AyhIEGi+411pwP0nrlS2+gt8FJL3WMIBeMTUrPF98WBUZF 5SiwiZV3QjPdSzc4pvNyvoBiupU9hdCi+IU+DcigvAKpTuHUPeGiYCszSYYWJrIx rNU1J6vaKM3djX8KLx5jBUfQaG9JhPfkdsh66Up4JXZUnnJ5cEtWhX4C4xLj2QAj ln2pWsJmKmvmxp4Mv7xO3GT0QpFf+O06SUoK5sMGrCFQiQvjaf/ZVAwBI8Xo1/F8 TDTiVu0iQHtarysr3vp+C3EOt3TtxA== =Pfy7 -----END PGP SIGNATURE-----