From: "Pali Rohár" <pali.rohar@gmail.com>
To: Tony Lindgren <tony@atomide.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: Thu, 19 Feb 2015 17:47:24 +0100 [thread overview]
Message-ID: <201502191747.24296@pali> (raw)
In-Reply-To: <20150218224206.GC32521@atomide.com>
[-- Attachment #1: Type: Text/Plain, Size: 1982 bytes --]
On Wednesday 18 February 2015 23:42:06 Tony Lindgren wrote:
> * 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
Anyway, here are original Nokia board data (2.6.28) for smc91x ethernet:
https://gitorious.org/linux-n900/linux-n900/source/629fc5ab00cafb31272c478efa2c2b35fabd4c70:arch/arm/mach-omap2/board-rx51-peripherals.c#L42
https://gitorious.org/linux-n900/linux-n900/source/629fc5ab00cafb31272c478efa2c2b35fabd4c70:arch/arm/mach-omap2/board-rx51-peripherals.c#L274
Can you check if it match with our data in DT file?
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2015-02-19 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150105230228.GO4081@atomide.com>
2015-02-18 15:19 ` [PATCH] ARM: dts: Revert disabling of smc91x for n900 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
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 [this message]
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=201502191747.24296@pali \
--to=pali.rohar@gmail.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=pavel@ucw.cz \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
/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