Age | Commit message (Collapse) | Author | Files | Lines |
|
The arm dts directory has grown to 1559 boards which makes it a bit
unwieldy to maintain and use. Past attempts stalled out due to plans to
move .dts files out of the kernel tree. Doing that is no longer planned
(any time soon at least), so let's go ahead and group .dts files by
vendors. This move aligns arm with arm64 .dts file structure.
There's no change to dtbs_install as the flat structure is maintained on
install.
The naming of vendor directories is roughly in this order of preference:
- Matching original and current SoC vendor prefix/name (e.g. ti, qcom)
- Current vendor prefix/name if still actively sold (SoCs which have
been aquired) (e.g. nxp/imx)
- Existing platform name for older platforms not sold/maintained by any
company (e.g. gemini, nspire)
The whole move was scripted with the exception of MAINTAINERS and a few
makefile fixups.
Acked-by: Viresh Kumar <[email protected]>
Acked-by: Michal Simek <[email protected]> #Xilinx
Acked-by: Krzysztof Kozlowski <[email protected]>
Acked-by: Neil Armstrong <[email protected]>
Acked-by: Paul Barker <[email protected]>
Acked-by: Tony Lindgren <[email protected]>
Acked-by: Gregory CLEMENT <[email protected]>
Acked-by: Heiko Stuebner <[email protected]>
Acked-by: Wei Xu <[email protected]> #hisilicon
Acked-by: Geert Uytterhoeven <[email protected]>
Acked-by: Nick Hawkins <[email protected]>
Acked-by: Baruch Siach <[email protected]>
Reviewed-by: Linus Walleij <[email protected]>
Reviewed-by: Andre Przywara <[email protected]>
Acked-by: Andre Przywara <[email protected]>
Reviewed-by: Claudiu Beznea <[email protected]>
Acked-by: Peter Rosin <[email protected]>
Acked-by: Jesper Nilsson <[email protected]>
Acked-by: Sudeep Holla <[email protected]>
Acked-by: Florian Fainelli <[email protected]> #broadcom
Acked-by: Manivannan Sadhasivam <[email protected]>
Reviewed-by: Jisheng Zhang <[email protected]>
Acked-by: Patrice Chotard <[email protected]>
Acked-by: Romain Perier <[email protected]>
Acked-by: Alexandre TORGUE <[email protected]>
Acked-by: Shawn Guo <[email protected]>
Acked-by: Kunihiko Hayashi <[email protected]>
Acked-by: Enric Balletbo i Serra <[email protected]>
Signed-off-by: Rob Herring <[email protected]>
|
|
The node names should be generic and DT schema expects certain pattern
(e.g. with key/button/switch).
Signed-off-by: Krzysztof Kozlowski <[email protected]>
Signed-off-by: Florian Fainelli <[email protected]>
|
|
Fix compatible strings for devicetrees using the BCM53012 and BCM53016 SoC.
Signed-off-by: Arınç ÜNAL <[email protected]>
Acked-by: Krzysztof Kozlowski <[email protected]>
Signed-off-by: Florian Fainelli <[email protected]>
|
|
Provide an empty 'ports' container node with the correct #address-cells
and #size-cells properties. This silences the following warning:
arch/arm/boot/dts/bcm4708-asus-rt-ac56u.dt.yaml:
ethernet-switch@18007000: 'oneOf' conditional failed, one must be fixed:
'ports' is a required property
'ethernet-ports' is a required property
From schema:
Documentation/devicetree/bindings/net/dsa/b53.yaml
Acked-by: Rafał Miłecki <[email protected]>
Signed-off-by: Florian Fainelli <[email protected]>
|
|
Fix the bulk of the unit_address_vs_reg warnings and unnecessary
\#address-cells/#size-cells without "ranges" or child "reg" property
Signed-off-by: Florian Fainelli <[email protected]>
|
|
Remove the usage of skeleton.dtsi in the remaining dts files. It was
deprecated since commit 9c0da3cc61f1 ("ARM: dts: explicitly mark
skeleton.dtsi as deprecated"). This will make adding a unit-address to
memory nodes easier.
The main tricky part to removing skeleton.dtsi is we could end up with
no /memory node at all when a bootloader depends on one being present. I
hacked up dtc to check for this condition.
Acked-by: Linus Walleij <[email protected]>
Reviewed-by: Florian Fainelli <[email protected]>
Reviewed-by: Matthias Brugger <[email protected]>
Acked-by: Viresh Kumar <[email protected]>
Acked-by: Alexandre Belloni <[email protected]>
Acked-by: Neil Armstrong <[email protected]>
Acked-by: Antoine Tenart <[email protected]>
Acked-by: Alexandre TORGUE <[email protected]>
Acked-by: Robert Jarzmik <[email protected]>
Acked-by: Vladimir Zapolskiy <[email protected]>
Tested-by: Kevin Hilman <[email protected]>
Reviewed-by: Kevin Hilman <[email protected]>
Tested-by: Martin Blumenstingl <[email protected]>
Reviewed-by: Martin Blumenstingl <[email protected]>
Signed-off-by: Rob Herring <[email protected]>
Reviewed-by: Gregory CLEMENT <[email protected]>
Tested-by: Gregory CLEMENT <[email protected]>
Signed-off-by: Arnd Bergmann <[email protected]>
|
|
Currently, the USB 3.0 PHY in bcm5301x.dtsi uses platform driver which
requires register range "ccb-mii" <0x18003000 0x1000>. This range
overlaps with MDIO cmd and param registers (<0x18003000 0x8>).
Essentially, the platform driver partly acts like a MDIO bus driver,
hence to use of this register range.
In some Northstar devices like Linksys EA9500, secondary switch is
connected via external MDIO. The only way to access and configure the
external switch is via MDIO bus. When we enable the MDIO bus in it's
current state, the MDIO bus and any child buses fail to register because
of the register range overlap.
On Northstar, the USB 3.0 PHY is connected at address 0x10 on the
internal MDIO bus. This change moves the usb3_phy node and makes it a
child node of internal MDIO bus.
Thanks to Rafał Miłecki's commit af850e14a7ae ("phy: bcm-ns-usb3: add
MDIO driver using proper bus layer") the same USB 3.0 platform driver
can now act as USB 3.0 PHY MDIO driver.
Tested on Linksys Panamera (EA9500)
Signed-off-by: Vivek Unune <[email protected]>
Signed-off-by: Florian Fainelli <[email protected]>
|
|
So far every Northstar device we have seen was using the same serial
console params (115200n8). It probably make the most sense to put it in
some proper dtsi files instead of repeating over and over for every
single device. As different boards may use different bootloaders it
seems the safest idea is to use board specific dtsi files.
Just in case some vendor decides to use different UART (parameters) this
can be always easily overwritten.
Signed-off-by: Rafał Miłecki <[email protected]>
Signed-off-by: Florian Fainelli <[email protected]>
|
|
Every device tested so far got UART0 (at 0x18000300) working as serial
console. It's most likely part of reference design and all vendors use
it that way.
It seems to be easier to enable it by default and just disable it if we
ever see a device with different hardware design.
Signed-off-by: Rafał Miłecki <[email protected]>
Acked-by: Jon Mason <[email protected]>
Acked-by: Hauke Mehrtens <[email protected]>
Signed-off-by: Florian Fainelli <[email protected]>
|
|
Add support for the Broadcom BCM953012 Enterprise Router reference
board, enable the following peripherals:
- UART0 (UART1 is not populated)
- WPS and restart GPIO buttons
- Ethernet switch w/ only two facing ports
- NAND flash
- SPI-NOR flash
Acked-by: Jon Mason <[email protected]>
Signed-off-by: Florian Fainelli <[email protected]>
|