linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Paulius Zaleckas <paulius.zaleckas@teltonika.lt>,
	Mike Frysinger <vapier.adi@gmail.com>,
	netdev@vger.kernel.org, linux-arm-kernel@lists.arm.linux.org.uk,
	linux-embedded@vger.kernel.org,
	Laurent Pinchart <laurentp@cse-semaphore.com>
Subject: Re: [PATCH] phylib: make mdio-gpio work without OF (v2)
Date: Wed, 5 Nov 2008 14:59:08 -0800	[thread overview]
Message-ID: <200811051459.08777.david-b@pacbell.net> (raw)
In-Reply-To: <fa686aa40811050704s2775fba8nc957a23cb81bb21d@mail.gmail.com>

On Wednesday 05 November 2008, Grant Likely wrote:
> > 	 Maybe the best solution is
> > to write separate driver for OF which will be just wrapper for platform
> > driver... Just like you suggested.

I'd certainly prefer that:  packaging all the OF glue in
a small bit of OF glue code, which doesn't need to affect
the majority of platforms (which don't and won't use OF).


> More complex than necessary.  Just give the driver 2 blocks of binding
> code; one for OF, one for non-OF.  No need to split up the driver.

The preceding discussion pointed out ways the "2 blocks"
approach doesn't currently work well ... minimally, there
is currently no way to do that without much ugly #ifdeffing.

And clearly, you and I view this a bit differently.  I'm
happier to think of these kinds of configuration as one
driver plus *separate* platform glue, while you want to be
modifying every driver to accomodate OF.  Or, by extension,
ACPI and any other hardware abstraction layer that comes
along.

- Dave

      reply	other threads:[~2008-11-05 22:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04 14:45 [PATCH] phylib: make mdio-gpio work without OF (v2) Paulius Zaleckas
2008-11-04 15:45 ` Marc Pignat
2008-11-04 15:57   ` Grant Likely
2008-11-04 16:24 ` Grant Likely
2008-11-05  0:04   ` David Brownell
2008-11-05  0:09     ` Mike Frysinger
2008-11-05  4:45       ` David Brownell
2008-11-05  5:34         ` Mike Frysinger
2008-11-05  8:11           ` David Brownell
2008-11-05  8:32             ` Mike Frysinger
2008-11-05  8:57               ` Marc Pignat
2008-11-05 23:03                 ` David Brownell
2008-11-05  8:57               ` Paulius Zaleckas
2008-11-05  9:04                 ` Paulius Zaleckas
2008-11-05 15:04                 ` Grant Likely
2008-11-05 22:59                   ` David Brownell [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=200811051459.08777.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=grant.likely@secretlab.ca \
    --cc=laurentp@cse-semaphore.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-embedded@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paulius.zaleckas@teltonika.lt \
    --cc=vapier.adi@gmail.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).