From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: dts: kirkwood: add kirkwood-km_fixedeth DTS file
Date: Thu, 15 May 2014 12:43:16 +0200 [thread overview]
Message-ID: <53749A44.800@gmail.com> (raw)
In-Reply-To: <1400147335-20947-4-git-send-email-valentin.longchamp@keymile.com>
On 05/15/2014 11:48 AM, Valentin Longchamp wrote:
> Besides our Kirkwood Reference design, there is another group of board
> on which the eth interface is not connected to a phy but to a swtich for
s/swtich/switch/
> some board internal communication.
>
> The configuration of the switch is handled by an EEPROM or by the
> bootloader, but on the kirkwood side, the port is always configured as
> 1000 Mbits, full duplex.
Hmm, if it is another variant of the Keymile board we already have,
it should probably go like this:
+ kirkwood.dtsi
+ kirkwood-98dx4122.dtsi
+--> kirkwood_km_common.dtsi
+--> kirkwood_km_kirkwood.dts
+--> kirkwood_km_fixedeth.dts
Andrew did some great series for the various NAS vendor boards, where
you can look at.
> Signed-off-by: Valentin Longchamp <valentin.longchamp@keymile.com>
>
> ---
>
> arch/arm/boot/dts/kirkwood-km_fixedeth.dts | 70 ++++++++++++++++++++++++++++++
> 1 file changed, 70 insertions(+)
> create mode 100644 arch/arm/boot/dts/kirkwood-km_fixedeth.dts
>
> diff --git a/arch/arm/boot/dts/kirkwood-km_fixedeth.dts b/arch/arm/boot/dts/kirkwood-km_fixedeth.dts
> new file mode 100644
> index 0000000..3d54d9b
> --- /dev/null
> +++ b/arch/arm/boot/dts/kirkwood-km_fixedeth.dts
> @@ -0,0 +1,70 @@
> +/dts-v1/;
> +
> +#include "kirkwood.dtsi"
> +#include "kirkwood-98dx4122.dtsi"
> +
> +/ {
> + model = "Keymile Kirkwood Fixed Eth";
> + compatible = "keymile,km_fixedeth", "marvell,kirkwood-98DX4122", "marvell,kirkwood";
> +
> + memory {
> + device_type = "memory";
> + reg = <0x00000000 0x08000000>;
> + };
> +
> + chosen {
> + bootargs = "console=ttyS0,115200n8 earlyprintk";
> + stdout-path = &uart0;
> + };
> +
> + mbus {
> + pcie-controller {
> + status = "okay";
> +
> + pcie at 1,0 {
> + status = "okay";
> + };
> + };
> + };
> +
> + ocp at f1000000 {
> + pinctrl: pin-controller at 10000 {
> + pinctrl-0 = < &pmx_i2c_gpio_sda &pmx_i2c_gpio_scl >;
> + pinctrl-names = "default";
> +
> + pmx_i2c_gpio_sda: pmx-gpio-sda {
> + marvell,pins = "mpp8";
> + marvell,function = "gpio";
> + };
> + pmx_i2c_gpio_scl: pmx-gpio-scl {
> + marvell,pins = "mpp9";
> + marvell,function = "gpio";
> + };
> + };
> +
> + serial at 12000 {
> + status = "ok";
> + };
> + };
> +
> + i2c at 0 {
> + compatible = "i2c-gpio";
> + gpios = < &gpio0 8 GPIO_ACTIVE_HIGH /* sda */
> + &gpio0 9 GPIO_ACTIVE_HIGH>; /* scl */
> + i2c-gpio,delay-us = <2>; /* ~100 kHz */
> + };
> +};
> +
> +&nand {
> + status = "okay";
> + chip-delay = <25>;
> +};
> +
> +ð0 {
> + status = "okay";
> + ethernet0-port at 0 {
> + phy-handle = <>;
Is that empty phy-handle required? If so, we should probably fix
it in mv643xx_eth instead.
> + speed = <1000>; /* <SPEED_1000> */
> + duplex = <0x01>; /* <DUPLEX_FULL> */
s/0x01/1/
Sebastian
> + };
> +};
>
next prev parent reply other threads:[~2014-05-15 10:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 9:48 [PATCH 0/3] Update the Keymile kirkwood DTS files Valentin Longchamp
2014-05-15 9:48 ` [PATCH 1/3] ARM: dts: kirkwood: resynch 98dx4122 dtsi Valentin Longchamp
2014-05-15 10:35 ` Sebastian Hesselbarth
2014-05-15 11:11 ` Valentin Longchamp
2014-05-15 13:24 ` Jason Cooper
2014-05-15 9:48 ` [PATCH 2/3] ARM: dts: kirkwood: enable the PCIe for km_kirkwood Valentin Longchamp
2014-05-15 9:48 ` [PATCH 3/3] ARM: dts: kirkwood: add kirkwood-km_fixedeth DTS file Valentin Longchamp
2014-05-15 10:43 ` Sebastian Hesselbarth [this message]
2014-05-15 11:04 ` Valentin Longchamp
2014-05-15 13:08 ` Andrew Lunn
2014-05-15 15:07 ` Valentin Longchamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53749A44.800@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).