devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: nm@ti.com
Cc: tony@atomide.com, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, nico@fluxnic.net,
	mark.rutland@arm.com
Subject: Re: [PATCH v2] net: smc91x: Fix device tree based configuration so it's usable
Date: Wed, 11 Dec 2013 15:44:26 -0500 (EST)	[thread overview]
Message-ID: <20131211.154426.2252395344655389568.davem@davemloft.net> (raw)
In-Reply-To: <52A8ADE6.8010209@ti.com>

From: Nishanth Menon <nm@ti.com>
Date: Wed, 11 Dec 2013 12:24:38 -0600

> Hi Tony,
> On 11/27/2013 12:56 PM, Tony Lindgren wrote:
>> Commit 89ce376c6bdc (drivers/net: Use of_match_ptr() macro in smc91x.c)
>> added minimal device tree support to smc91x, but it's not working on
>> many platforms because of the lack of some key configuration bits.
>> 
>> Fix the issue by parsing the necessary configuration like the
>> smc911x driver is doing. As most smc91x users seem to use 16-bit
>> access, let's default to that if no reg-io-width is specified.
>> 
>> Cc: Nicolas Pitre <nico@fluxnic.net>
>> Cc: Mark Rutland <mark.rutland@arm.com>
>> Cc: netdev@vger.kernel.org
>> Cc: devicetree@vger.kernel.org
>> Signed-off-by: Tony Lindgren <tony@atomide.com>
>> 
>> ---
>> 
>> Device tree folks, any objection to using the reg-io-width property
>> as a mask here?
>> 
>> Looks like we can use reg-io-width as a mask too if needed, it seems
>> to play fine with combinations of 1 = 8-bit, 2 = 16-bit, 4 = 32-bit
>> and so on.
>> 
>> I would like to see this merged during the -rc cycle as this makes
>> my test devices behave the same way when booted in legacy platform
>> data mode compared to when booted with device tree.
>> 
> please feel free to add my:
> Acked-by: Nishanth Menon <nm@ti.com>
> 
> Also tested on SDP2430:
> http://pastebin.mozilla.org/3756403

That patch needs changes, it adds a warning when CONFIG_OF is disabled
because the variable 'np' only gets used in the CONFIG_OF protected
code block yet is declared unconditionally.

  reply	other threads:[~2013-12-11 20:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27 18:56 [PATCH v2] net: smc91x: Fix device tree based configuration so it's usable Tony Lindgren
     [not found] ` <20131127185657.GA26766-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2013-12-11 18:24   ` Nishanth Menon
2013-12-11 20:44     ` David Miller [this message]
     [not found]       ` <20131211.154426.2252395344655389568.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2013-12-11 21:22         ` Tony Lindgren

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=20131211.154426.2252395344655389568.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=nico@fluxnic.net \
    --cc=nm@ti.com \
    --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;
as well as URLs for NNTP newsgroup(s).