mirror of
git://git.openwrt.org/openwrt/openwrt.git
synced 2025-01-20 05:40:50 +00:00
51ec9b3864
I have collected the known information from the dts files we have.
After that I made a new device tree that should work for this whole D-Link
switch family.
This device tree is based on modules where you first select which SoC group
the device belongs to. Then you include the GPIO dtsi file depending on what
hardware your device has, see examples below.
This tree is also expandable for more hardware,
see the part 'Future expansion possibilities' further down.
-------------------------------------------------------------------------------
The device tree now looks like this:
----------------
| rtl838x.dtsi | // Note 1.
----------------
|
|
---------------------------------------
| rtl838x_d-link_dgs-1210_common.dtsi | // Note 2.
---------------------------------------
|
| --------------
|-------| device.dts | // Note 3.
| --------------
|
-------------------------------------
| rtl83xx_d-link_dgs-1210_gpio.dtsi | // Note 4.
-------------------------------------
|
| --------------
|-------| device.dts | // Note 5.
--------------
Note 1; Included in rtl838x_d-link_dgs-1210_common.dtsi.
Note 2; SoC level information and memory mapping. Choose which one to include
in the device dts.
Note 3; At this point dgs-1210-16 will come out here.
Note 4; In this dtsi only common board hardware based on the rtl8231 is found.
No PoE based hardware in this dtsi.
In this dtsi there is no <#include> to above *_common.dtsi.
Note 5; Device dts with only rtl8231 based hardware without PoE will come out
here.
-------------------------------------------------------------------------------
How to set up in dts file:
The device dts will have one of these two <#include> alternatives.
This alternative includes only common features:
<#include "rtl838x_d-link_dgs-1210_common.dtsi">
This alternative includes common and the rtl8231 GPIO (no PoE) features:
<#include "rtl838x_d-link_dgs-1210_common.dtsi">
<#include "rtl83xx_d-link_dgs-1210_gpio.dtsi">
-------------------------------------------------------------------------------
Implementation:
Finally, I also implemented this new family device tree on the current
supported devices:
dgs-1210-10p
dgs-1210-16
dgs-1210-20
dgs-1210-28
The implementation for the dgs-1210-10p is different. I have removed the
information from the rtl8382_d-link_dgs-1210-10p.dts that is already present
in rtl838x_d-link_dgs-1210_common.dtsi.
Since the rest isn't officially probed in the device dts I do not want to
include the rtl83xx_d-link_dgs-1210_gpio.dtsi with dgs-1210-10p.dts.
Since I don't have these devices to test on I have built the original firmware
for each one of these devices before this change and saved the dtb file and
then compared the original dtb file with the dtb file built with this new
device tree.
-------------------------------------------------------------------------------
Future expansion possibilities:
In parallel with the rtl838x_d-link_dgs-1210_common.dtsi in the tree map
we can make a rtl839x_d-link_dgs-1210_common.dtsi to use the rtl839x.dtsi if
the need arises with more devices based on rtl839x soc.
When we have more PoE devices so the hardware map for these gets more clear
we can make a rtl83xx_d-link_dgs-1210_poe.dtsi below
the rtl83xx_d-link_dgs-1210_gpio.dtsi in the tree map.
I looked at the port and switch setup to see if it could be moved to the dtsi.
I decided not to touch this part now. The reason was that there isn't really
any meaningful way this could be shared between the devices.
The only thing in common over the family is the 8+2sfp ports on the
dgs-1210-10xx device.
And then there is the hot plug SFP and I2C ports that aren’t implemented
on any device. So maybe when we see the whole port map for the family
then maybe the ports can be moved to a *_common.dtsi but I don't think it is
the right moment for that now.
Signed-off-by: Daniel Groth <flygarn12@gmail.com>
[Capitalisation of abbreviations and 'D-Link']
Signed-off-by: Sander Vanheule <sander@svanheule.net>
|
||
|---|---|---|
| .. | ||
| rtl83xx_d-link_dgs-1210_gpio.dtsi | ||
| rtl83xx_panasonic_mxxeg-pn28xx0k.dtsi | ||
| rtl838x_d-link_dgs-1210_common.dtsi | ||
| rtl838x_hpe_1920.dtsi | ||
| rtl838x.dtsi | ||
| rtl839x.dtsi | ||
| rtl930x.dtsi | ||
| rtl931x.dtsi | ||
| rtl8380_engenius_ews2910p.dts | ||
| rtl8380_hpe_1920-8g.dts | ||
| rtl8380_netgear_gigabit_1xx.dtsi | ||
| rtl8380_netgear_gigabit_3xx.dtsi | ||
| rtl8380_netgear_gigabit.dtsi | ||
| rtl8380_netgear_gs108t-v3.dts | ||
| rtl8380_netgear_gs110tpp-v1.dts | ||
| rtl8380_netgear_gs308t-v1.dts | ||
| rtl8380_netgear_gs310tp-v1.dts | ||
| rtl8380_panasonic_m8eg-pn28080k.dts | ||
| rtl8380_tplink_sg2008p-v1.dts | ||
| rtl8380_zyxel_gs1900-8.dts | ||
| rtl8380_zyxel_gs1900-8hp-v1.dts | ||
| rtl8380_zyxel_gs1900-8hp-v2.dts | ||
| rtl8380_zyxel_gs1900-10hp.dts | ||
| rtl8380_zyxel_gs1900.dtsi | ||
| rtl8382_allnet_all-sg8208m.dts | ||
| rtl8382_d-link_dgs-1210-10p.dts | ||
| rtl8382_d-link_dgs-1210-16.dts | ||
| rtl8382_d-link_dgs-1210-20.dts | ||
| rtl8382_d-link_dgs-1210-28.dts | ||
| rtl8382_hpe_1920-16g.dts | ||
| rtl8382_hpe_1920-24g.dts | ||
| rtl8382_hpe_1920.dtsi | ||
| rtl8382_inaba_aml2-17gp.dts | ||
| rtl8382_iodata_bsh-g24mb.dts | ||
| rtl8382_panasonic_m16eg-pn28160k.dts | ||
| rtl8382_panasonic_m24eg-pn28240k.dts | ||
| rtl8382_zyxel_gs1900-16.dts | ||
| rtl8382_zyxel_gs1900-24-v1.dts | ||
| rtl8382_zyxel_gs1900-24e.dts | ||
| rtl8382_zyxel_gs1900-24hp-v1.dts | ||
| rtl8382_zyxel_gs1900-24hp-v2.dts | ||
| rtl8393_panasonic_m48eg-pn28480k.dts | ||
| rtl8393_zyxel_gs1900-48.dts | ||
| rtl9302_zyxel_xgs1250-12.dts | ||