From: omar.ramirez@ti.com (Ramirez Luna, Omar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] OMAP: omap_device: use pdev as parameter to get rt_va
Date: Mon, 13 Dec 2010 12:08:15 -0600 [thread overview]
Message-ID: <AANLkTik667cW19eCVNNLf3_dc9efFYms0H2z-fGU24Ob@mail.gmail.com> (raw)
In-Reply-To: <4D05D586.6090408@ti.com>
Hi Benoit,
On Mon, Dec 13, 2010 at 2:12 AM, Cousson, Benoit <b-cousson@ti.com> wrote:
> Hi Omar,
>
> On 12/11/2010 12:45 AM, Ramirez Luna, Omar wrote:
>>
>> Make the parameter received by omap_device_get_mpu_rt_va
>> consistent with the functions meant to be called by drivers.
>>
>> Also move its header declaration to appear in the set of
>> functions to be used by drivers, as per the comment there.
>
> Please note that even if Paul submitted this API upon request from Santosh,
> we do not want driver to us it most of the time.
Oh, ok. Yes, I was under the impression that this ioremap was internal
to hwmod, and drivers should do their own one; but then I noticed that
API and since it was under the "public functions through struct
platform data", I thought it was easier to pass pdev than od.
> All drivers should us the generic Linux way to get physical mem resource and
> then ioremap it.
Then I guess this function belongs to the "public for core code" and
not for drivers along with the omap_device_get_pwrdm.
> I assume that if you want to update this API, you are probably already using
> it.
> Why cannot you use the generic way?
I can leave the generic way along with ioremap, the purpose was to use
omap_device APIs as much as possible.
Thanks,
Omar
next prev parent reply other threads:[~2010-12-13 18:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 23:45 [PATCH] OMAP: omap_device: use pdev as parameter to get rt_va Omar Ramirez Luna
2010-12-13 8:12 ` Cousson, Benoit
2010-12-13 18:08 ` Ramirez Luna, Omar [this message]
2010-12-15 0:17 ` Paul Walmsley
2010-12-15 1:12 ` Paul Walmsley
2010-12-15 8:56 ` Russell King - ARM Linux
2010-12-15 14:53 ` Paul Walmsley
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=AANLkTik667cW19eCVNNLf3_dc9efFYms0H2z-fGU24Ob@mail.gmail.com \
--to=omar.ramirez@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).