On Mon, 29 Jul 2024 19:02:23 +0100 Mark Brown <broonie@xxxxxxxxxx> wrote: > On Sat, 29 Jun 2024 16:04:00 -0300, Marcelo Schmitt wrote: > > This patch series extends the SPI bitbang, gpio, and spi-engine controllers to > > support configurable MOSI line idle states. > > It then introduces the ad4000 driver which uses the MOSI idle configuration to > > provide improved support for the AD4000 series of ADCs. > > Documentation is added describing the new extension to the SPI protocol. > > The currently supported wiring modes for AD4000 devices were documented under > > IIO documentation directory. > > > > [...] > > Applied to > > https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next > > Thanks! > > [1/7] spi: Enable controllers to extend the SPI protocol with MOSI idle configuration > commit: f58872f45c36ded048bccc22701b0986019c24d8 > [2/7] spi: bitbang: Implement support for MOSI idle state configuration > commit: 320f6693097bf89d67f9cabad24a2b911e23073f > [3/7] spi: spi-gpio: Add support for MOSI idle state configuration > commit: 927d382c7efbcc2206c31fa2f672fa264c0f1d5b > [4/7] spi: spi-axi-spi-engine: Add support for MOSI idle configuration > commit: a62073f4b2164028fc7c5ae45ceba10c9326cd91 Hi Mark, Any chance of a tag + you seem to have also picked up the ADC dt binding. Patch 5/7. dt-bindings: iio: adc: Add AD4000 which I'm assuming was not intentional. I think I only need the definition of SPI_MOSI_IDLE_HIGH for 5-7 to build fine. If needed, I can use a local value for that in the driver and we can follow up with a patch using the main define once the trees come together upstream. Jonathan > > All being well this means that it will be integrated into the linux-next > tree (usually sometime in the next 24 hours) and sent to Linus during > the next merge window (or sooner if it is a bug fix), however if > problems are discovered then the patch may be dropped or reverted. > > You may get further e-mails resulting from automated or manual testing > and review of the tree, please engage with people reporting problems and > send followup patches addressing any issues that are reported if needed. > > If any updates are required or you are submitting further changes they > should be sent as incremental updates against current git, existing > patches will not be replaced. > > Please add any relevant lists and maintainers to the CCs when replying > to this mail. > > Thanks, > Mark >
