| Message ID | 20220707065800.261269-7-william.zhang@broadcom.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | [RESEND,1/8] ARM: debug: bcmbca: Replace ARCH_BCM_63XX with ARCH_BCMBCA | expand |
On 7/6/22 23:57, William Zhang wrote: > Prepare for the BCM63138 ARCH_BCM_63XX migration to ARCH_BCMBCA. Make > SPI_BCM63XX_HSSPI depending on ARCH_BCMBCA. > > Signed-off-by: William Zhang <william.zhang@broadcom.com> Acked-by: Florian Fainelli <f.fainelli@gmail.com> There is no cover letter for this 8 patch series :/ it is not clear to me whether each subsystem maintainer will be in a position to merge these patches individually, yet still have all 8 (7 of them actually, see comment to patch 1) land in 5.20. Alternatively, we can merge these patches through the Broadcom ARM SoC pull request(s) to ensure they all land at the same time.
On Wed, 6 Jul 2022 23:57:58 -0700, William Zhang <william.zhang@broadcom.com> wrote: > Prepare for the BCM63138 ARCH_BCM_63XX migration to ARCH_BCMBCA. Make > SPI_BCM63XX_HSSPI depending on ARCH_BCMBCA. > > Signed-off-by: William Zhang <william.zhang@broadcom.com> > --- Applied to https://github.com/Broadcom/stblinux/commits/drivers/next, thanks! -- Florian
On Sun, Jul 10, 2022 at 07:11:31PM -0700, Florian Fainelli wrote: > On Wed, 6 Jul 2022 23:57:58 -0700, William Zhang <william.zhang@broadcom.com> wrote: > > Prepare for the BCM63138 ARCH_BCM_63XX migration to ARCH_BCMBCA. Make > > SPI_BCM63XX_HSSPI depending on ARCH_BCMBCA. > Applied to https://github.com/Broadcom/stblinux/commits/drivers/next, thanks! I was rather hoping for an answer on what the situation with dependencies was here...
On 7/11/22 03:45, Mark Brown wrote: > On Sun, Jul 10, 2022 at 07:11:31PM -0700, Florian Fainelli wrote: >> On Wed, 6 Jul 2022 23:57:58 -0700, William Zhang <william.zhang@broadcom.com> wrote: >>> Prepare for the BCM63138 ARCH_BCM_63XX migration to ARCH_BCMBCA. Make >>> SPI_BCM63XX_HSSPI depending on ARCH_BCMBCA. > >> Applied to https://github.com/Broadcom/stblinux/commits/drivers/next, thanks! > > I was rather hoping for an answer on what the situation with > dependencies was here... Each patch is independent from one another and there are not dependencies on the Broadcom arm-soc tree(s) other than for CONFIG_ARCH_BCMBCA which was introduced with v5.19 with b32c613b3fda3e1c26119609f1ad6b19178f82f5. That said, I prefer to take all patches via the Broadcom arm-soc tree(s) to ensure a timely inclusion for our upcoming v5.20 pull request, and ensure that all drivers are converted in one release cycle. If you want to give me your Acked-by or that I drop this and take it via the spi tree, please let me know. Thanks!
On Mon, Jul 11, 2022 at 09:04:39AM -0700, Florian Fainelli wrote: > Each patch is independent from one another and there are not dependencies on > the Broadcom arm-soc tree(s) other than for CONFIG_ARCH_BCMBCA which was > introduced with v5.19 with b32c613b3fda3e1c26119609f1ad6b19178f82f5. That > said, I prefer to take all patches via the Broadcom arm-soc tree(s) to > ensure a timely inclusion for our upcoming v5.20 pull request, and ensure > that all drivers are converted in one release cycle. > If you want to give me your Acked-by or that I drop this and take it via the > spi tree, please let me know. Acked-by: Mark Brown <broonie@kernel.org>
On 7/11/22 09:09, Mark Brown wrote: > On Mon, Jul 11, 2022 at 09:04:39AM -0700, Florian Fainelli wrote: > >> Each patch is independent from one another and there are not dependencies on >> the Broadcom arm-soc tree(s) other than for CONFIG_ARCH_BCMBCA which was >> introduced with v5.19 with b32c613b3fda3e1c26119609f1ad6b19178f82f5. That >> said, I prefer to take all patches via the Broadcom arm-soc tree(s) to >> ensure a timely inclusion for our upcoming v5.20 pull request, and ensure >> that all drivers are converted in one release cycle. > >> If you want to give me your Acked-by or that I drop this and take it via the >> spi tree, please let me know. > > Acked-by: Mark Brown <broonie@kernel.org> Thanks, FWIW, I had amended that patch with your ACked-by before sending it to the arm-soc maintainers.
diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig index 2d034459e79f..8e550269d488 100644 --- a/drivers/spi/Kconfig +++ b/drivers/spi/Kconfig @@ -183,7 +183,7 @@ config SPI_BCM63XX config SPI_BCM63XX_HSSPI tristate "Broadcom BCM63XX HS SPI controller driver" - depends on BCM63XX || BMIPS_GENERIC || ARCH_BCM_63XX || COMPILE_TEST + depends on BCM63XX || BMIPS_GENERIC || ARCH_BCMBCA || COMPILE_TEST help This enables support for the High Speed SPI controller present on newer Broadcom BCM63XX SoCs.
Prepare for the BCM63138 ARCH_BCM_63XX migration to ARCH_BCMBCA. Make SPI_BCM63XX_HSSPI depending on ARCH_BCMBCA. Signed-off-by: William Zhang <william.zhang@broadcom.com> --- drivers/spi/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)