config ARCH_BCM2835
bool "Broadcom BCM2835 family"
- depends on ARCH_MULTI_V6 || ARCH_MULTI_V7
+ depends on ARCH_MULTI_V6 || ARCH_MULTI_V7 || ARM64
Humm, what does that achieve?
Nothing ;)
Slipped through unnoticed, I'll drop it.
quoted
+config ARCH_BCM
+ bool "Broadcom SoC Support"
+ help
+ This enables support for Broadcom ARM based SoC chips
menuconfig maybe?
There isn't any in arch/arm64/Kconfig.platforms right now, so I didn't
feel like introducing one. Also the dependency should have pretty much
the same effect ...
quoted
+config ARCH_BCM2835
+ bool "Broadcom BCM2835 family"
+ depends on ARCH_BCM
+ select ARCH_REQUIRE_GPIOLIB
+ select CLKSRC_OF
+ select PINCTRL
+ select PINCTRL_BCM2835
+ select ARM_AMBA
+ select ARM_TIMER_SP804
+ select HAVE_ARM_ARCH_TIMER
+ help
+ This enables support for the Broadcom BCM2837 SoC.
+ This SoC is used in the Raspberry Pi 3 device.
+
config ARCH_BCM_IPROC
bool "Broadcom iProc SoC Family"
+ depends on ARCH_BCM
Does not seem necessary nor adding anything here.
Added for consistency. When we add ARCH_BCM all ARCH_BCM_* should
depend on it ...
We could also do it the other way around: make ARCH_BCM a hidden bool
and have ARCH_BCM_* select it.
cheers,
Gerd
config ARCH_BCM2835
bool "Broadcom BCM2835 family"
- depends on ARCH_MULTI_V6 || ARCH_MULTI_V7
+ depends on ARCH_MULTI_V6 || ARCH_MULTI_V7 || ARM64
Humm, what does that achieve?
Nothing ;)
Slipped through unnoticed, I'll drop it.
quoted
quoted
+config ARCH_BCM
+ bool "Broadcom SoC Support"
+ help
+ This enables support for Broadcom ARM based SoC chips
menuconfig maybe?
There isn't any in arch/arm64/Kconfig.platforms right now, so I didn't
feel like introducing one. Also the dependency should have pretty much
the same effect ...
quoted
quoted
+config ARCH_BCM2835
+ bool "Broadcom BCM2835 family"
+ depends on ARCH_BCM
+ select ARCH_REQUIRE_GPIOLIB
+ select CLKSRC_OF
+ select PINCTRL
+ select PINCTRL_BCM2835
+ select ARM_AMBA
+ select ARM_TIMER_SP804
+ select HAVE_ARM_ARCH_TIMER
+ help
+ This enables support for the Broadcom BCM2837 SoC.
+ This SoC is used in the Raspberry Pi 3 device.
+
config ARCH_BCM_IPROC
bool "Broadcom iProc SoC Family"
+ depends on ARCH_BCM
Does not seem necessary nor adding anything here.
Added for consistency. When we add ARCH_BCM all ARCH_BCM_* should
depend on it ...
We could also do it the other way around: make ARCH_BCM a hidden bool
and have ARCH_BCM_* select it.
Yes, this is probably better.
ARCH_BCM_IPROC is currently enabled in arch/arm64/configs/defconfig. By
adding a dependency here without enabling ARCH_BCM in arm64 defconfig,
this effectively disables ARCH_BCM_IPROC from arm64 defconfig.
From: Scott Branden <scott.branden@broadcom.com> Date: 2016-06-02 16:48:31
Reply inline.
On 16-06-02 09:25 AM, Ray Jui wrote:
On 6/1/2016 11:45 PM, Gerd Hoffmann wrote:
quoted
quoted
quoted
config ARCH_BCM2835
bool "Broadcom BCM2835 family"
- depends on ARCH_MULTI_V6 || ARCH_MULTI_V7
+ depends on ARCH_MULTI_V6 || ARCH_MULTI_V7 || ARM64
Humm, what does that achieve?
Nothing ;)
Slipped through unnoticed, I'll drop it.
quoted
quoted
+config ARCH_BCM
+ bool "Broadcom SoC Support"
+ help
+ This enables support for Broadcom ARM based SoC chips
menuconfig maybe?
There isn't any in arch/arm64/Kconfig.platforms right now, so I didn't
feel like introducing one. Also the dependency should have pretty much
the same effect .
No need to add ARCH_BCM
.
quoted
quoted
quoted
+config ARCH_BCM2835
+ bool "Broadcom BCM2835 family"
+ depends on ARCH_BCM
+ select ARCH_REQUIRE_GPIOLIB
+ select CLKSRC_OF
+ select PINCTRL
+ select PINCTRL_BCM2835
+ select ARM_AMBA
+ select ARM_TIMER_SP804
+ select HAVE_ARM_ARCH_TIMER
+ help
+ This enables support for the Broadcom BCM2837 SoC.
+ This SoC is used in the Raspberry Pi 3 device.
+
config ARCH_BCM_IPROC
bool "Broadcom iProc SoC Family"
+ depends on ARCH_BCM
Does not seem necessary nor adding anything here.
Added for consistency. When we add ARCH_BCM all ARCH_BCM_* should
depend on it ...
We could also do it the other way around: make ARCH_BCM a hidden bool
and have ARCH_BCM_* select it.
Yes, this is probably better.
ARCH_BCM_IPROC is currently enabled in arch/arm64/configs/defconfig. By
adding a dependency here without enabling ARCH_BCM in arm64 defconfig,
this effectively disables ARCH_BCM_IPROC from arm64 defconfig.
There are Makefile(s) with
obj-$(CONFIG_ARCH_BCM) += bcm/
in drivers/pinctrl for example, maybe more, didn't check the whole tree.
So without ARCH_BCM some drivers are dropped from the build ...
cheers,
Gerd
From: Scott Branden <scott.branden@broadcom.com> Date: 2016-06-02 17:22:09
On 16-06-02 10:12 AM, Gerd Hoffmann wrote:
quoted
There is no need to add ARCH_BCM though?
There are Makefile(s) with
obj-$(CONFIG_ARCH_BCM) += bcm/
in drivers/pinctrl for example, maybe more, didn't check the whole tree.
So without ARCH_BCM some drivers are dropped from the build ...
I see that now. Quite bizarre how the NS2 pinctl driver (used on a
arm64 SoC) gets built right now....
Yes, adding the select with hidden option seems like what needs to be
done. The ARM Maintainers did not like multi-level ARCH_BCM being added
in the arm64 Kconfig previously so we dropped it.
There are Makefile(s) with
obj-$(CONFIG_ARCH_BCM) += bcm/
in drivers/pinctrl for example, maybe more, didn't check the whole tree.
So without ARCH_BCM some drivers are dropped from the build ...
I see that now. Quite bizarre how the NS2 pinctl driver (used on a
arm64 SoC) gets built right now....
Yes, adding the select with hidden option seems like what needs to be
done. The ARM Maintainers did not like multi-level ARCH_BCM being added
in the arm64 Kconfig previously so we dropped it.
We should always recusrse into that directory and build the respective
pinctrl drivers within drivers/pinctrl/bcm, only for the enabled
platforms, it makes no sense to have this kind of config symbol gating that.
I can submit a patch doing just that unless somebody wants to do it as
part of this patch series.
--
Florian