Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755378AbbKDI23 (ORCPT ); Wed, 4 Nov 2015 03:28:29 -0500 Received: from mailout4.w1.samsung.com ([210.118.77.14]:56695 "EHLO mailout4.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751403AbbKDI20 (ORCPT ); Wed, 4 Nov 2015 03:28:26 -0500 X-AuditID: cbfec7f5-f794b6d000001495-5b-5639c1a8b80a Subject: Re: [PATCH v5 4/4] ARM: dts: Add Ethernet chip to SMDK5410 To: Pavel Fedin , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org References: <4568ad982f0af1846994119961cbb798edff311c.1446542020.git.p.fedin@samsung.com> Cc: Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Kukjin Kim From: Krzysztof Kozlowski X-Enigmail-Draft-Status: N1110 Message-id: <5639C1A5.1040708@samsung.com> Date: Wed, 04 Nov 2015 17:28:21 +0900 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-version: 1.0 In-reply-to: <4568ad982f0af1846994119961cbb798edff311c.1446542020.git.p.fedin@samsung.com> Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupkkeLIzCtJLcpLzFFi42I5/e/4Nd0VBy3DDE7N57KYf+Qcq0X/m4Ws FuderWS0eP3C0KL/8Wtmi02Pr7FaXN41h81ixvl9TBZLr19ksnh1aRWbxYTpa1ksWvceYXfg 8Vgzbw2jx+W+XiaPlcu/sHlsWtXJ5rF5Sb1H35ZVjB6fN8kFsEdx2aSk5mSWpRbp2yVwZUz/ F1LwUqhi36e9zA2MV/m6GDk5JARMJI5tWscIYYtJXLi3nq2LkYtDSGApo8SryT0sEM4XRonG Z6uYQKqEBZwlptzpBUuICKxhlFh+7iAjRFUbo8SWHbdYQRxmgQeMEvcvN4ENZhMwlti8fAkb xBI5id7uSSwgNq+AlsTq7y3sIDaLgKrElbNHWEFsUYEIiYkTGlghagQlfky+B1bPKRAj0XDn N1CcA2iBnsT9i1ogYWYBeYnNa94yT2AUnIWkYxZC1SwkVQsYmVcxiqaWJhcUJ6XnGukVJ+YW l+al6yXn525ihETQ1x2MS49ZHWIU4GBU4uG9yWgZJsSaWFZcmXuIUYKDWUmEt2kJUIg3JbGy KrUoP76oNCe1+BCjNAeLkjjvzF3vQ4QE0hNLUrNTUwtSi2CyTBycUg2M2vf39shOOyoxrexh nciTnRqa2Q5G2pJpSldu20ypaaqdIM1z7YmwlYemxoT5RpsWd19jja08Xcr/ZqLmsx9/NtpL dvfL2huk7vr9YFuB59v5u94vDXyguu2K62oBTds0jRYX44va5ZUHnzjm9tbejnRjkQvZtfLZ 0YU1Tb/6+DQfFd7vXrleiaU4I9FQi7moOBEAb8CYTZwCAAA= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2569 Lines: 90 On 03.11.2015 18:16, Pavel Fedin wrote: > The chip is smsc9115, connected via SROMc bank 3. Additionally, some GPIO > initialization is required. > > Signed-off-by: Pavel Fedin > --- > arch/arm/boot/dts/exynos5410-smdk5410.dts | 40 +++++++++++++++++++++++++++++++ > 1 file changed, 40 insertions(+) > > diff --git a/arch/arm/boot/dts/exynos5410-smdk5410.dts b/arch/arm/boot/dts/exynos5410-smdk5410.dts > index cebeaab..f41952f 100644 > --- a/arch/arm/boot/dts/exynos5410-smdk5410.dts > +++ b/arch/arm/boot/dts/exynos5410-smdk5410.dts > @@ -61,6 +61,27 @@ > disable-wp; > }; > > +&pinctrl_0 { > + srom_ctl: srom-ctl { > + samsung,pins = "gpy0-3", "gpy0-4", "gpy0-5", > + "gpy1-0", "gpy1-1", "gpy1-2", "gpy1-3"; > + samsung,pin-function = <2>; > + samsung,pin-drv = <0>; > + }; > + > + srom_ebi: srom-ebi { > + samsung,pins = "gpy3-0", "gpy3-1", "gpy3-2", "gpy3-3", > + "gpy3-4", "gpy3-5", "gpy3-6", "gpy3-7", > + "gpy5-0", "gpy5-1", "gpy5-2", "gpy5-3", > + "gpy5-4", "gpy5-5", "gpy5-6", "gpy5-7", > + "gpy6-0", "gpy6-1", "gpy6-2", "gpy6-3", > + "gpy6-4", "gpy6-5", "gpy6-6", "gpy6-7"; > + samsung,pin-function = <2>; > + samsung,pin-pud = <3>; > + samsung,pin-drv = <0>; > + }; > +}; > + > &uart0 { > status = "okay"; > }; > @@ -72,3 +93,22 @@ > &uart2 { > status = "okay"; > }; > + > +&sromc { Put sromc in alphabetical order. > + pinctrl-names = "default"; > + pinctrl-0 = <&srom_ctl>, <&srom_ebi>; > + > + ethernet@3 { > + compatible = "smsc,lan9115"; > + reg = <3 0 0x10000>; > + phy-mode = "mii"; > + interrupt-parent = <&gpx0>; > + interrupts = <5 8>; s/8/IRQ_TYPE_LEVEL_LOW/ (is this really level low interrupt?) > + reg-io-width = <2>; > + smsc,irq-push-pull; > + smsc,force-internal-phy; > + > + samsung,srom-page-mode = <1>; > + samsung,srom-timing = <9 12 1 9 1 1>; Some other DTS include regulators: vddvario-supply and vdd33a-supply. It seems that they are not described in SMSC911x bindings but in GPMC-eth... but the smsc911x driver is requesting them. Could you investigate that? I think these regulators should be provided (and SMSC911x bindings should be updated). > + }; > +}; I don't have the board schematics so I couldn't verify the GPIOs. Overall looks good. Best regards, Krzysztof -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/