| Message ID | 20230207065826.285013-1-william.zhang@broadcom.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | spi: bcm63xx-hsspi: driver and doc updates | expand |
On Mon, 06 Feb 2023 22:58:11 -0800, William Zhang wrote: > This patch series include the accumulative updates and fixes for the > driver from Broadcom. It also added a new driver for the updated SPI > controller found in the new BCMBCA SoC. The device tree document is > converted to yaml format and updated accordingly. > > Changes in v3: > - Clean up spi-controller.yaml and update the example > - Drop the generic compatible string brcm,bcmbca-hsspi from the document > and dts files > - Port the cs_change and cs_off logic from SPI core > spi_transfer_one_message function to both controller drivers. > - Factor dummy cs workaround into a function, adjust the logic for > different xfer modes and fine tune message level in bcm63xx-hsspi > controller driver > - Replace hard-coded opcode with SPINOR_OP definition > - Add a new patch to export export spi_transfer_cs_change_delay_exec > function in the spi core > - Add a new patch to include compatible string brcm,bcmbca-hsspi-v1.0 in > bcm63xx-hsspi controller driver > - Minor coding style fix in bcmbca-hsspi controller driver > - Add Acked-by and Reviewed-by tag > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [01/15] dt-bindings: spi: Convert bcm63xx-hsspi bindings to json-schema commit: fff948a44b44a628c81294af5498226cb66a2594 [02/15] dt-bindings: spi: Add bcmbca-hsspi controller support commit: 0ba979f995324417fd773881bc5a39910a9f2362 [03/15] ARM: dts: broadcom: bcmbca: Add spi controller node (no commit info) [04/15] arm64: dts: broadcom: bcmbca: Add spi controller node (no commit info) [05/15] spi: bcm63xx-hsspi: Add new compatible string support commit: 99d7428ac94bf67d6e9df81dd3b4bf3046196ad6 [06/15] spi: bcm63xx-hsspi: Endianness fix for ARM based SoC commit: 85a84a61699990db6a025b5073f337f49933a875 [07/15] spi: bcm63xx-hsspi: Add polling mode support commit: 50a6620dd1fbc810476422a965b041f1839f8eac [08/15] spi: export spi_transfer_cs_change_delay_exec function (no commit info) [09/15] spi: bcm63xx-hsspi: Handle cs_change correctly (no commit info) [10/15] spi: bcm63xx-hsspi: Fix multi-bit mode setting (no commit info) [11/15] spi: bcm63xx-hsspi: Add prepend mode support (no commit info) [12/15] spi: spi-mem: Allow controller supporting mem_ops without exec_op (no commit info) [13/15] spi: bcm63xx-hsspi: Disable spi mem dual io read op support (no commit info) [14/15] spi: bcmbca-hsspi: Add driver for newer HSSPI controller (no commit info) [15/15] MAINTAINERS: Add entry for Broadcom Broadband SoC HS SPI drivers (no commit info) 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
On 2/9/23 09:18, Mark Brown wrote: > On Mon, 06 Feb 2023 22:58:11 -0800, William Zhang wrote: >> This patch series include the accumulative updates and fixes for the >> driver from Broadcom. It also added a new driver for the updated SPI >> controller found in the new BCMBCA SoC. The device tree document is >> converted to yaml format and updated accordingly. >> >> Changes in v3: >> - Clean up spi-controller.yaml and update the example >> - Drop the generic compatible string brcm,bcmbca-hsspi from the document >> and dts files >> - Port the cs_change and cs_off logic from SPI core >> spi_transfer_one_message function to both controller drivers. >> - Factor dummy cs workaround into a function, adjust the logic for >> different xfer modes and fine tune message level in bcm63xx-hsspi >> controller driver >> - Replace hard-coded opcode with SPINOR_OP definition >> - Add a new patch to export export spi_transfer_cs_change_delay_exec >> function in the spi core >> - Add a new patch to include compatible string brcm,bcmbca-hsspi-v1.0 in >> bcm63xx-hsspi controller driver >> - Minor coding style fix in bcmbca-hsspi controller driver >> - Add Acked-by and Reviewed-by tag >> >> [...] > > Applied to > > https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next > > Thanks! > > [01/15] dt-bindings: spi: Convert bcm63xx-hsspi bindings to json-schema > commit: fff948a44b44a628c81294af5498226cb66a2594 > [02/15] dt-bindings: spi: Add bcmbca-hsspi controller support > commit: 0ba979f995324417fd773881bc5a39910a9f2362 > [03/15] ARM: dts: broadcom: bcmbca: Add spi controller node > (no commit info) > [04/15] arm64: dts: broadcom: bcmbca: Add spi controller node > (no commit info) Usually we have SoC maintainers pick up the DTS patches affecting the platforms they cover to avoid conflicts... I suppose that is fine.
On Thu, Feb 09, 2023 at 10:34:34AM -0800, Florian Fainelli wrote: > On 2/9/23 09:18, Mark Brown wrote: > > [03/15] ARM: dts: broadcom: bcmbca: Add spi controller node > > (no commit info) > > [04/15] arm64: dts: broadcom: bcmbca: Add spi controller node > > (no commit info) > Usually we have SoC maintainers pick up the DTS patches affecting the > platforms they cover to avoid conflicts... I suppose that is fine. Hence the "no commit info" - there's no commit for those changes.
On 2/9/23 10:36, Mark Brown wrote: > On Thu, Feb 09, 2023 at 10:34:34AM -0800, Florian Fainelli wrote: >> On 2/9/23 09:18, Mark Brown wrote: > >>> [03/15] ARM: dts: broadcom: bcmbca: Add spi controller node >>> (no commit info) >>> [04/15] arm64: dts: broadcom: bcmbca: Add spi controller node >>> (no commit info) > >> Usually we have SoC maintainers pick up the DTS patches affecting the >> platforms they cover to avoid conflicts... I suppose that is fine. > > Hence the "no commit info" - there's no commit for those changes. Did not I get tripped over this before, yes I did! OK, I will go hide in that corner other there. Thanks!