Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1032347AbbKEL1Z (ORCPT ); Thu, 5 Nov 2015 06:27:25 -0500 Received: from mail-pa0-f42.google.com ([209.85.220.42]:34629 "EHLO mail-pa0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031044AbbKEL1X (ORCPT ); Thu, 5 Nov 2015 06:27:23 -0500 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> <5639C1A5.1040708@samsung.com> <004f01d117bb$1e4fbb40$5aef31c0$@samsung.com> Cc: k.kozlowski.k@gmail.com, "'Rob Herring'" , "'Pawel Moll'" , "'Mark Rutland'" , "'Ian Campbell'" , "'Kumar Gala'" , "'Kukjin Kim'" From: Krzysztof Kozlowski X-Enigmail-Draft-Status: N1110 Message-ID: <563B3D15.2070700@samsung.com> Date: Thu, 5 Nov 2015 20:27:17 +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: <004f01d117bb$1e4fbb40$5aef31c0$@samsung.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2062 Lines: 50 W dniu 05.11.2015 o 20:14, Pavel Fedin pisze: > Hello! > >>> + 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?) > > Yes, according to: https://github.com/AndreiLux/Perseus-S3/blob/master/arch/arm/mach-exynos/mach-smdk5250.c#L133 Although this is different board, but okay. > >> 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). > > Sorry, i cannot. The board has lots of jumpers, which choose between fixed voltage and regulators for different components, > according to board's manual, but the manual is very poor IMHO, and i don't understand how to use them. And i use default, > fixed-voltage configuration. > One of my colleagues tried to get it working, but failed. It actually requires more time, and IIRC you need to bring up i2c before > you can drive regulators. > So can we leave it as it is for now? At least it works, and this is much better than no ethernet support at all. Ok, that is sufficient explanation. >> I don't have the board schematics so I couldn't verify the GPIOs. > > Me neither, i wrote GPIO settings according to chip datasheet i have. They are actually chip-specific, but i wrote them in board > file because on different boards you may use different banks, and therefore different pins. Or, if you don't use SROMc at all, you > can configure all pins to do something else. > Makes sense. 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/