linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Olof Johansson <olof@lixom.net>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-ide@vger.kernel.org, paulus@samba.org,
	linuxppc-dev@ozlabs.org,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [PATCH] pasemi: electra IDE/pata_platform glue
Date: Sun, 13 May 2007 13:17:57 +0200	[thread overview]
Message-ID: <82c4101a83362d2ce78713a70df535d4@kernel.crashing.org> (raw)
In-Reply-To: <20070513061954.GA16623@lixom.net>

> Also, in this particular case, the bindings are not standardized, and
> there's a good chance that whatever new platform uses a similar device
> will need to do something slightly different.

Yeah, everyone else will do the sane thing, and describe
the two register ranges the IDE uses, not a much bigger
range full of register shadows like you have.  It is one
thing for the hardware to do partial address decoding;
the device tree shouldn't normally expose this though.

But that's what you've got now, so you have your own
special OF device matching code, which is exactly as it
should be.  No need to have "generic" ide OF matching
code until device trees containing such devices show
up :-)


Segher


  parent reply	other threads:[~2007-05-13 11:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-12 14:50 [PATCH] pasemi: electra IDE/pata_platform glue Olof Johansson
2007-05-12 23:11 ` Arnd Bergmann
2007-05-12 23:58   ` Alan Cox
2007-05-13  0:48     ` Arnd Bergmann
2007-05-13  2:20       ` Benjamin Herrenschmidt
2007-05-13  6:19         ` Olof Johansson
2007-05-13  8:01           ` Benjamin Herrenschmidt
2007-05-13 11:17           ` Segher Boessenkool [this message]
2007-05-13 13:39       ` Alan Cox
2007-05-13 21:18       ` Olof Johansson

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=82c4101a83362d2ce78713a70df535d4@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arnd@arndb.de \
    --cc=benh@kernel.crashing.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olof@lixom.net \
    --cc=paulus@samba.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: 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).