From: "Bjørn Mork" <bjorn-yOkvZcmFvRU@public.gmane.org>
To: balbi-l0cyMroinI0@public.gmane.org
Cc: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org,
linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
kuninori.morimoto.gx-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [balbi-usb:xceiv 3/3] drivers/usb/phy/rcar-phy.c:75:3: error: implicit declaration of function 'iowrite32'
Date: Fri, 02 Nov 2012 11:05:35 +0100 [thread overview]
Message-ID: <87liekz5e8.fsf@nemi.mork.no> (raw)
In-Reply-To: <20121102091620.GE17938-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org> (Felipe Balbi's message of "Fri, 2 Nov 2012 11:16:20 +0200")
Felipe Balbi <balbi-l0cyMroinI0@public.gmane.org> writes:
> On Thu, Nov 01, 2012 at 11:06:58AM -0400, David Miller wrote:
>> From: Bjørn Mork <bjorn-yOkvZcmFvRU@public.gmane.org>
>> Date: Thu, 01 Nov 2012 14:38:29 +0100
>>
>> > Felipe Balbi <balbi-l0cyMroinI0@public.gmane.org> writes:
>> >
>> >> btw, only alpha and x86 seem to be providing all of those, but if you
>> >> look into our documentation, it's said that drivers are supposed to use
>> >> write/read{b,w,l,q} for all memory-mapped io. I'd expect all platforms
>> >> to provide those even if just to allow compilation of drivers.
>> >
>> > Only if HAS_IOMEM is true, I believe.
>>
>> This is correct.
>
> fair enough, then we can depend on HAS_IOMEM.
>
> Another question, if HAS_IOMEM is true, is the arch expected to provide
> *all* accessor methods ?
I'll leave this for those with more clue...
But there is a comment in arch/alpha/include/asm/io.h indicating that
writeq/readq support is tested separately, so I guess it must be
optional:
/*
* Some mucking forons use if[n]def writeq to check if platform has it.
* It's a bloody bad idea and we probably want ARCH_HAS_WRITEQ for them
* to play with; for now just use cpp anti-recursion logics and make sure
* that damn thing is defined and expands to itself.
*/
#define writeq writeq
#define readq readq
> And the last one: if the arch provides
> read/write{b,w,l,q}, should it be selecting HAS_IOMEM ??
But that one is easy: HAS_IOMEM is true by default. The arch sets
NO_IOMEM to disable it. Similar to HAS_DMA. So you can be pretty sure
that HAS_IOMEM is selected unless the arch has reasons not to. From
lib/Kconfig:
config HAS_IOMEM
boolean
depends on !NO_IOMEM
select GENERIC_IO
default y
Bjørn
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: "Bjørn Mork" <bjorn@mork.no>
To: balbi@ti.com
Cc: David Miller <davem@davemloft.net>,
gregkh@linuxfoundation.org, linux-arch@vger.kernel.org,
fengguang.wu@intel.com, kuninori.morimoto.gx@renesas.com,
linux-usb@vger.kernel.org
Subject: Re: [balbi-usb:xceiv 3/3] drivers/usb/phy/rcar-phy.c:75:3: error: implicit declaration of function 'iowrite32'
Date: Fri, 02 Nov 2012 11:05:35 +0100 [thread overview]
Message-ID: <87liekz5e8.fsf@nemi.mork.no> (raw)
Message-ID: <20121102100535.AwS3ajh6jYx_KBuYuMA2Tc7sAQ4-n1JUJJvpUxROwco@z> (raw)
In-Reply-To: <20121102091620.GE17938@arwen.pp.htv.fi> (Felipe Balbi's message of "Fri, 2 Nov 2012 11:16:20 +0200")
Felipe Balbi <balbi@ti.com> writes:
> On Thu, Nov 01, 2012 at 11:06:58AM -0400, David Miller wrote:
>> From: Bjørn Mork <bjorn@mork.no>
>> Date: Thu, 01 Nov 2012 14:38:29 +0100
>>
>> > Felipe Balbi <balbi@ti.com> writes:
>> >
>> >> btw, only alpha and x86 seem to be providing all of those, but if you
>> >> look into our documentation, it's said that drivers are supposed to use
>> >> write/read{b,w,l,q} for all memory-mapped io. I'd expect all platforms
>> >> to provide those even if just to allow compilation of drivers.
>> >
>> > Only if HAS_IOMEM is true, I believe.
>>
>> This is correct.
>
> fair enough, then we can depend on HAS_IOMEM.
>
> Another question, if HAS_IOMEM is true, is the arch expected to provide
> *all* accessor methods ?
I'll leave this for those with more clue...
But there is a comment in arch/alpha/include/asm/io.h indicating that
writeq/readq support is tested separately, so I guess it must be
optional:
/*
* Some mucking forons use if[n]def writeq to check if platform has it.
* It's a bloody bad idea and we probably want ARCH_HAS_WRITEQ for them
* to play with; for now just use cpp anti-recursion logics and make sure
* that damn thing is defined and expands to itself.
*/
#define writeq writeq
#define readq readq
> And the last one: if the arch provides
> read/write{b,w,l,q}, should it be selecting HAS_IOMEM ??
But that one is easy: HAS_IOMEM is true by default. The arch sets
NO_IOMEM to disable it. Similar to HAS_DMA. So you can be pretty sure
that HAS_IOMEM is selected unless the arch has reasons not to. From
lib/Kconfig:
config HAS_IOMEM
boolean
depends on !NO_IOMEM
select GENERIC_IO
default y
Bjørn
next prev parent reply other threads:[~2012-11-02 10:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50924f0a.QuF7xjrp4IUSKMwd%fengguang.wu@intel.com>
[not found] ` <20121101103339.GD410@arwen.pp.htv.fi>
[not found] ` <20121101105034.GE410@arwen.pp.htv.fi>
[not found] ` <20121101105034.GE410-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2012-11-01 13:04 ` [balbi-usb:xceiv 3/3] drivers/usb/phy/rcar-phy.c:75:3: error: implicit declaration of function 'iowrite32' Greg KH
2012-11-01 13:04 ` Greg KH
2012-11-01 13:23 ` Felipe Balbi
[not found] ` <20121101132342.GE12489-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2012-11-01 13:38 ` Bjørn Mork
2012-11-01 13:38 ` Bjørn Mork
2012-11-01 15:06 ` David Miller
2012-11-02 9:16 ` Felipe Balbi
[not found] ` <20121102091620.GE17938-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2012-11-02 10:05 ` Bjørn Mork [this message]
2012-11-02 10:05 ` Bjørn Mork
2012-11-01 13:47 ` Max Filippov
2012-11-01 14:29 ` Fengguang Wu
2012-11-01 15:07 ` David Miller
2012-11-02 9:17 ` Felipe Balbi
[not found] ` <20121101130420.GB20982-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2012-11-01 15:53 ` James Bottomley
2012-11-01 15:53 ` James Bottomley
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=87liekz5e8.fsf@nemi.mork.no \
--to=bjorn-yokvzcmfvru@public.gmane.org \
--cc=balbi-l0cyMroinI0@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=kuninori.morimoto.gx-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org \
--cc=linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.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