[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <159078636491.21150.10991273309807336688.b4-ty@kernel.org>
Date: Fri, 29 May 2020 22:06:20 +0100
From: Mark Brown <broonie@...nel.org>
To: Serge Semin <Sergey.Semin@...kalelectronics.ru>,
Rob Herring <robh+dt@...nel.org>
Cc: Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
Feng Tang <feng.tang@...el.com>, linux-kernel@...r.kernel.org,
Serge Semin <fancer.lancer@...il.com>,
linux-mips@...r.kernel.org,
Georgy Vlasov <Georgy.Vlasov@...kalelectronics.ru>,
Arnd Bergmann <arnd@...db.de>, linux-spi@...r.kernel.org,
Ramil Zaripov <Ramil.Zaripov@...kalelectronics.ru>,
devicetree@...r.kernel.org, Rob Herring <robh@...nel.org>,
Alexey Malahov <Alexey.Malahov@...kalelectronics.ru>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: Re: [PATCH v7] dt-bindings: spi: Convert DW SPI binding to DT schema
On Fri, 29 May 2020 21:25:43 +0300, Serge Semin wrote:
> Modern device tree bindings are supposed to be created as YAML-files
> in accordance with dt-schema. This commit replaces two DW SPI legacy
> bare text bindings with YAML file. As before the bindings file states
> that the corresponding dts node is supposed to be compatible either
> with generic DW APB SSI controller or with Microsemi/Amazon/Renesas/Intel
> vendors-specific controllers, to have registers, interrupts and clocks
> properties. Though in case of Microsemi version of the controller
> there must be two registers resources specified. Properties like
> clock-names, reg-io-width, cs-gpio, num-cs, DMA and slave device
> sub-nodes are optional.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: Convert DW SPI binding to DT schema
commit: 164c05f03ffabe36564cb8959c1fad7c56f294dd
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
Powered by blists - more mailing lists