Searched hist:ed7481c7d18fe2c632b6fbe5646b32cefd2dc791 (Results 1 – 8 of 8) sorted by relevance
| /rk3399_rockchip-uboot/arch/arm/mach-bcm283x/include/mach/ |
| H A D | sdhci.h | ed7481c7d18fe2c632b6fbe5646b32cefd2dc791 Thu Mar 17 03:40:56 UTC 2016 Stephen Warren <swarren@wwwdotorg.org> ARM: bcm283x: don't always define CONFIG_BCM2835
Currently, CONFIG_BCM2835 is defined for all BCM283x builds and _BCM2836
is defined when building for that SoC. That means there isn't a single
define that means "exactly BCM2835". This will complicate future patches
where BCM2835-vs-anything-else needs to be determined simply.
Modify the code to define one or the other of CONFIG_BCM2835/BCM2836 so
future patches are simpler.
Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
|
| H A D | timer.h | ed7481c7d18fe2c632b6fbe5646b32cefd2dc791 Thu Mar 17 03:40:56 UTC 2016 Stephen Warren <swarren@wwwdotorg.org> ARM: bcm283x: don't always define CONFIG_BCM2835
Currently, CONFIG_BCM2835 is defined for all BCM283x builds and _BCM2836
is defined when building for that SoC. That means there isn't a single
define that means "exactly BCM2835". This will complicate future patches
where BCM2835-vs-anything-else needs to be determined simply.
Modify the code to define one or the other of CONFIG_BCM2835/BCM2836 so
future patches are simpler.
Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
|
| H A D | gpio.h | ed7481c7d18fe2c632b6fbe5646b32cefd2dc791 Thu Mar 17 03:40:56 UTC 2016 Stephen Warren <swarren@wwwdotorg.org> ARM: bcm283x: don't always define CONFIG_BCM2835
Currently, CONFIG_BCM2835 is defined for all BCM283x builds and _BCM2836
is defined when building for that SoC. That means there isn't a single
define that means "exactly BCM2835". This will complicate future patches
where BCM2835-vs-anything-else needs to be determined simply.
Modify the code to define one or the other of CONFIG_BCM2835/BCM2836 so
future patches are simpler.
Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
|
| H A D | wdog.h | ed7481c7d18fe2c632b6fbe5646b32cefd2dc791 Thu Mar 17 03:40:56 UTC 2016 Stephen Warren <swarren@wwwdotorg.org> ARM: bcm283x: don't always define CONFIG_BCM2835
Currently, CONFIG_BCM2835 is defined for all BCM283x builds and _BCM2836
is defined when building for that SoC. That means there isn't a single
define that means "exactly BCM2835". This will complicate future patches
where BCM2835-vs-anything-else needs to be determined simply.
Modify the code to define one or the other of CONFIG_BCM2835/BCM2836 so
future patches are simpler.
Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
|
| H A D | mbox.h | ed7481c7d18fe2c632b6fbe5646b32cefd2dc791 Thu Mar 17 03:40:56 UTC 2016 Stephen Warren <swarren@wwwdotorg.org> ARM: bcm283x: don't always define CONFIG_BCM2835
Currently, CONFIG_BCM2835 is defined for all BCM283x builds and _BCM2836
is defined when building for that SoC. That means there isn't a single
define that means "exactly BCM2835". This will complicate future patches
where BCM2835-vs-anything-else needs to be determined simply.
Modify the code to define one or the other of CONFIG_BCM2835/BCM2836 so
future patches are simpler.
Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
|
| /rk3399_rockchip-uboot/arch/arm/mach-bcm283x/ |
| H A D | phys2bus.c | ed7481c7d18fe2c632b6fbe5646b32cefd2dc791 Thu Mar 17 03:40:56 UTC 2016 Stephen Warren <swarren@wwwdotorg.org> ARM: bcm283x: don't always define CONFIG_BCM2835
Currently, CONFIG_BCM2835 is defined for all BCM283x builds and _BCM2836
is defined when building for that SoC. That means there isn't a single
define that means "exactly BCM2835". This will complicate future patches
where BCM2835-vs-anything-else needs to be determined simply.
Modify the code to define one or the other of CONFIG_BCM2835/BCM2836 so
future patches are simpler.
Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
|
| /rk3399_rockchip-uboot/board/raspberrypi/rpi/ |
| H A D | rpi.c | ed7481c7d18fe2c632b6fbe5646b32cefd2dc791 Thu Mar 17 03:40:56 UTC 2016 Stephen Warren <swarren@wwwdotorg.org> ARM: bcm283x: don't always define CONFIG_BCM2835
Currently, CONFIG_BCM2835 is defined for all BCM283x builds and _BCM2836
is defined when building for that SoC. That means there isn't a single
define that means "exactly BCM2835". This will complicate future patches
where BCM2835-vs-anything-else needs to be determined simply.
Modify the code to define one or the other of CONFIG_BCM2835/BCM2836 so
future patches are simpler.
Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
|
| /rk3399_rockchip-uboot/include/configs/ |
| H A D | rpi.h | ed7481c7d18fe2c632b6fbe5646b32cefd2dc791 Thu Mar 17 03:40:56 UTC 2016 Stephen Warren <swarren@wwwdotorg.org> ARM: bcm283x: don't always define CONFIG_BCM2835
Currently, CONFIG_BCM2835 is defined for all BCM283x builds and _BCM2836
is defined when building for that SoC. That means there isn't a single
define that means "exactly BCM2835". This will complicate future patches
where BCM2835-vs-anything-else needs to be determined simply.
Modify the code to define one or the other of CONFIG_BCM2835/BCM2836 so
future patches are simpler.
Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
|