Skip to content

RFC ARM: start to move SoC code into arch/arm/mach-*

Albert ARIBAUD u-boot 1 version New

Get series with b4
b4 am 20150201111144.3d30aa1a@lilith

Versions newest first

  1. v1 RFC Latest0 of 21 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 21 patches the cover letter announces are in this archive.

Reviews trailers per patch

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

Read the v1 thread

Cover letter [U-Boot] [RFC PATCH 0/21] ARM: start to move SoC code into arch/arm/mach-*

Hello Simon,

Quoted 11 lines · Simon Glass

Hi Albert,

Quoted 8 lines · Albert ARIBAUD

Hello Masahiro,

Quoted 3 lines · Masahiro Yamada

This series can be applied on the current u-boot/master (commit 37b608a52dcb133)

Quoted 6 lines
Quoted 3 lines

I'd rather not have all mach-* directories just below arch/arm/. Can't they be created under arch/arm/soc/ instead? That would give a cleaner structure IMO.

It does save a level and I am forever typing cpu/armv7 to get what feels like nowhere...

That can easily be solved (and tuned to personal taste) with CDPATH, eg.

uboot at lilith:~/src/u-boot-arm (master)$ export CDPATH=arch/arm/cpu:arch/arm uboot at lilith:~/src/u-boot-arm (master)$ cd armv
armv7/ armv8/
uboot at lilith:~/src/u-boot-arm (master)$ cd armv7 /home/uboot/src/u-boot-arm/arch/arm/cpu/armv7
uboot at lilith:~/src/u-boot-arm/arch/arm/cpu/armv7 (master)$

(the u-boot-friendly value of CDPATH can put in a u-boot_env.sh file to be sourced along with other u-boot related settings)

Quoted 1 line

this is what the kernel does and it does seem convenient.

Well, to me it does not really -- I'm ok with loads of mach-* subdirs under a commin parent dir, but what's the benefit of mixing mach-* dirs with non-mach-* ones?

Quoted 2 lines

Regards,
Simon

Amicalement,

Signature · 1 line
Albert.