From: Russell King <rmk@arm.linux.org.uk>
To: Paul Mundt <lethal@linux-sh.org>,
Ralf Baechle <ralf@linux-mips.org>,
Al Viro <viro@ftp.linux.org.uk>,
Magnus Damm <magnus.damm@gmail.com>,
netdev@vger.kernel.org, ben-linux@fluff.or
Subject: Re: [RFC] dependencies for platform drivers (was Re: ax88796: add superh to kconfig dependencies)
Date: Fri, 9 Nov 2007 12:02:55 +0000 [thread overview]
Message-ID: <20071109120255.GB8101@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20071109094023.GA7022@linux-sh.org>
On Fri, Nov 09, 2007 at 06:40:23PM +0900, Paul Mundt wrote:
> On Fri, Nov 09, 2007 at 09:26:52AM +0000, Ralf Baechle wrote:
> > If writesb() is not an official API then maybe the answer should have been
> > to either add that API to other architectures or fix the driver.
> >
> > I guess this incident means I need to go through all Kconfig* files to
> > see what bogus architecture dependencies on MIPS or !MIPS exist ...
> >
> While writesb() isn't an official API, the iowriteX_rep() interfaces
> theoretically are. Tidying up the driver for iomap is probably a better
> option.
writesb() predates iowriteX_rep() interfaces by quite a number of years,
though if you're using writesb(), converting over to iowriteX_rep() is
really a no-brainer.
writesb() is effectively what mmio_outsb() is, and exists to do what
outsb() does but for peripherals mapped using ioremap on ARM rather
than trying to emulate them via the legacy x86 IO interfaces.
Note that it would've been far better that whoever invented mmio_outsb()
looked around and noticed that some of us already have an implementation
called writesb()... but time has proven that folk seem to be blinkered
to anything not x86.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2007-11-09 12:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 7:31 ax88796: add superh to kconfig dependencies Magnus Damm
2007-11-08 8:12 ` Paul Mundt
2007-11-08 8:18 ` [RFC] dependencies for platform drivers (was Re: ax88796: add superh to kconfig dependencies) Al Viro
2007-11-08 9:02 ` Andrew Morton
2007-11-09 9:26 ` Ralf Baechle
2007-11-09 9:40 ` Paul Mundt
2007-11-09 12:02 ` Russell King [this message]
2007-11-09 12:08 ` Ben Dooks
2007-11-09 12:06 ` Ben Dooks
2007-11-10 3:12 ` Jeff Garzik
2007-11-08 17:47 ` ax88796: add superh to kconfig dependencies Jeff Garzik
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=20071109120255.GB8101@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=ben-linux@fluff.or \
--cc=lethal@linux-sh.org \
--cc=magnus.damm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=viro@ftp.linux.org.uk \
/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).