Skip to content

RISC-V: kconfig.socs cleanup, part 1

Conor Dooley linux-arm-kernel linux-riscv soc 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest7 patches 11 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/7RISC-V: introduce ARCH_FOO kconfig aliases for SOC_FOO symbolsarch/riscv/Kconfig.socs+21 -07 replies
2/7RISC-V: kconfig.socs: convert usage of SOC_CANAAN to ARCH_CANAANarch/riscv/Kconfig.socs+5 -50 replies
3/7RISC-V: kbuild: convert all use of SOC_FOO to ARCH_FOOarch/riscv/Makefile arch/riscv/boot/dts/Makefile arch/riscv/boot/dts/canaan/Makefile +3 more+16 -162 replies
4/7RISC-V: stop selecting SIFIVE_PLIC at the SoC levelarch/riscv/Kconfig arch/riscv/Kconfig.socs+1 -50 replies
5/7RISC-V: stop selecting the PolarFire SoC clock driverarch/riscv/Kconfig.socs+0 -12 replies
6/7RISC-V: stop selecting SiFive clock and serial drivers directlyarch/riscv/Kconfig.socs+0 -40 replies
7/7RISC-V: stop directly selecting drivers for SOC_CANAANarch/riscv/Kconfig.socs+0 -30 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH v1 0/7] RISC-V: kconfig.socs cleanup, part 1

From: Conor Dooley <[email protected]>

Hey all,

Following on from my RFC series a little bit ago, I'm back again with an attempted conversion of our SOC_FOO symbols to a more uniform ARCH_FOO. Last time around, I had about 30 patches [0], but here I have a more modest offering.

Patch 1 adds stubs, that ideally would be applied for v6.2-rc1 (but after week 1, see the note in that patch for more), which would allow for converting drivers etc over a release cycle (or more) while allowing everything else to keep working in the meantime.

Christoph Hellwig & Damien voiced some objections in the original thread, hopefully the gradual conversion assuages Damien's concerns about breaking defconfigs - but I am not sure what to do about Christoph's dislike of the ARCH_FOO stuff. A change the world approach is unlikely to be well received & introducing "duplicate" symbols for cross-arch vendors would surely be similarly well received? I don't mind doing it, but my instinct is that that is a futile use of time.

The rest of this series contains v6.3 material, converting SOC_FOO usages in arch/riscv to ARCH_FOO.

Thanks,
Conor.

[0] - https://lore.kernel.org/linux-riscv/[email protected]/

CC Arnd Bergmann <[email protected]>
CC Christoph Hellwig <[email protected]>
CC Conor.Dooley <[email protected]>
CC Damien Le Moal <[email protected]>
CC Emil Renner Berthing <[email protected]>
CC Geert Uytterhoeven <[email protected]>
CC Heiko Stuebner <[email protected]>
CC Palmer Dabbelt <[email protected]>
CC Samuel Holland <[email protected]>

Conor Dooley (7):
RISC-V: introduce ARCH_FOO kconfig aliases for SOC_FOO symbols
RISC-V: kconfig.socs: convert usage of SOC_CANAAN to ARCH_CANAAN
RISC-V: kbuild: convert all use of SOC_FOO to ARCH_FOO
RISC-V: stop selecting SIFIVE_PLIC at the SoC level
RISC-V: stop selecting the PolarFire SoC clock driver
RISC-V: stop selecting SiFive clock and serial drivers directly
RISC-V: stop directly selecting drivers for SOC_CANAAN

 arch/riscv/Kconfig                     |  1 +
 arch/riscv/Kconfig.socs                | 44 +++++++++++++++-----------
 arch/riscv/Makefile                    |  2 +-
 arch/riscv/boot/dts/Makefile           |  2 +-
 arch/riscv/boot/dts/canaan/Makefile    | 14 ++++----
 arch/riscv/boot/dts/microchip/Makefile |  8 ++---
 arch/riscv/boot/dts/sifive/Makefile    |  4 +--
 arch/riscv/boot/dts/starfive/Makefile  |  2 +-
 8 files changed, 43 insertions(+), 34 deletions(-)
Signature · 7 lines
2.37.2


_______________________________________________
linux-riscv mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv