From: Tony Lindgren <tony@atomide.com> To: "Pali Rohár" <pali.rohar@gmail.com> Cc: linux-omap@vger.kernel.org, Kevin Hilman <khilman@kernel.org>, Aaro Koskinen <aaro.koskinen@iki.fi>, Sebastian Reichel <sre@kernel.org>, Pavel Machek <pavel@ucw.cz>, linux-kernel@vger.kernel.org, Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>, Nishanth Menon <nm@ti.com> Subject: Re: [PATCH] ARM: dts: Revert disabling of smc91x for n900 Date: Wed, 18 Feb 2015 14:42:06 -0800 [thread overview] Message-ID: <20150218224206.GC32521@atomide.com> (raw) In-Reply-To: <201502182004.03195@pali> * Pali Rohár <pali.rohar@gmail.com> [150218 11:07]: > On Wednesday 18 February 2015 17:33:53 Tony Lindgren wrote: > > > */ +// reg = <1 0x300 0xf>; /* 16 byte IO range at > offset > > > 0x300 */ + reg = <1 0x0 0xf>; /* 16 byte IO range > at > > > offset 0x300 */ > > > > > > bank-width = <2>; > > > pinctrl-names = "default"; > > > pinctrl-0 = <ðernet_pins>; > > > > Oh cool, the 0x300 offset is there mostly to suppress warnings > > about non-standard location. ... > > OK that's good news. Care to do a patch to set the offset 0x0 > > with added comment that qemu needs it? I'll test to make sure > > it works on the real hardware as well. > > Yes, I can send proper git format-patch, but first let me know if > that change does not break your HW... Yes using reg = <1 0 0xf> works, it just adds this extra warning: smc91x 2000000.ethernet (unnamed net_device) (uninitialized): smc91x: IOADDR d09d6000 doesn't match configuration (300). And I'm pretty sure that can be fixed by setting the EEPROM offset to 0 instead of the default 0x300. People with smc91x most likely want to write at least the MAC address to the EEPROM, so might as well set the offset to zero then too. Of course it's always possible to do do a omap3-n900-qemu.dts if larger changes are needed :) Regards, Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com> To: "Pali Rohár" <pali.rohar@gmail.com> Cc: linux-omap@vger.kernel.org, Kevin Hilman <khilman@kernel.org>, Aaro Koskinen <aaro.koskinen@iki.fi>, Sebastian Reichel <sre@kernel.org>, Pavel Machek <pavel@ucw.cz>, linux-kernel@vger.kernel.org, Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>, Nishanth Menon <nm@ti.com> Subject: Re: [PATCH] ARM: dts: Revert disabling of smc91x for n900 Date: Wed, 18 Feb 2015 14:42:06 -0800 [thread overview] Message-ID: <20150218224206.GC32521@atomide.com> (raw) In-Reply-To: <201502182004.03195@pali> * Pali Rohár <pali.rohar@gmail.com> [150218 11:07]: > On Wednesday 18 February 2015 17:33:53 Tony Lindgren wrote: > > > */ +// reg = <1 0x300 0xf>; /* 16 byte IO range at > offset > > > 0x300 */ + reg = <1 0x0 0xf>; /* 16 byte IO range > at > > > offset 0x300 */ > > > > > > bank-width = <2>; > > > pinctrl-names = "default"; > > > pinctrl-0 = <ðernet_pins>; > > > > Oh cool, the 0x300 offset is there mostly to suppress warnings > > about non-standard location. ... > > OK that's good news. Care to do a patch to set the offset 0x0 > > with added comment that qemu needs it? I'll test to make sure > > it works on the real hardware as well. > > Yes, I can send proper git format-patch, but first let me know if > that change does not break your HW... Yes using reg = <1 0 0xf> works, it just adds this extra warning: smc91x 2000000.ethernet (unnamed net_device) (uninitialized): smc91x: IOADDR d09d6000 doesn't match configuration (300). And I'm pretty sure that can be fixed by setting the EEPROM offset to 0 instead of the default 0x300. People with smc91x most likely want to write at least the MAC address to the EEPROM, so might as well set the offset to zero then too. Of course it's always possible to do do a omap3-n900-qemu.dts if larger changes are needed :) Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-02-18 23:26 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-05 23:02 [PATCH] ARM: dts: Revert disabling of smc91x for n900 Tony Lindgren 2015-01-05 23:09 ` Pali Rohár 2015-01-05 23:10 ` Tony Lindgren 2015-01-06 15:03 ` Sebastian Reichel 2015-01-06 15:23 ` Pali Rohár 2015-01-06 8:00 ` Pavel Machek 2015-01-06 16:59 ` Tony Lindgren 2015-01-06 19:44 ` Aaro Koskinen 2015-01-06 19:54 ` Tony Lindgren 2015-01-06 20:17 ` Tony Lindgren 2015-01-06 20:34 ` Pali Rohár 2015-01-06 21:24 ` Tony Lindgren 2015-01-06 20:42 ` Pavel Machek 2015-01-06 21:56 ` Aaro Koskinen 2015-01-06 22:04 ` Tony Lindgren 2015-01-06 19:59 ` Pali Rohár 2015-01-07 9:57 ` Pavel Machek 2015-01-07 15:44 ` Nishanth Menon 2015-01-07 16:40 ` Tony Lindgren 2015-01-07 20:09 ` Pavel Machek 2015-01-07 21:25 ` Pavel Machek 2015-01-08 9:01 ` Pali Rohár 2015-01-08 18:54 ` Tony Lindgren 2015-01-07 20:00 ` Pavel Machek 2015-01-06 17:38 ` Kevin Hilman 2015-02-18 15:19 ` Pali Rohár 2015-02-18 16:33 ` Tony Lindgren 2015-02-18 19:04 ` Pali Rohár 2015-02-18 22:42 ` Tony Lindgren [this message] 2015-02-18 22:42 ` Tony Lindgren 2015-02-18 22:52 ` Pali Rohár 2015-02-19 4:50 ` Tony Lindgren 2015-02-19 10:59 ` Pali Rohár 2015-02-19 16:47 ` Pali Rohár
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=20150218224206.GC32521@atomide.com \ --to=tony@atomide.com \ --cc=aaro.koskinen@iki.fi \ --cc=ivo.g.dimitrov.75@gmail.com \ --cc=khilman@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=nm@ti.com \ --cc=pali.rohar@gmail.com \ --cc=pavel@ucw.cz \ --cc=sre@kernel.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.