All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
	Hiroshi Doyu <hiroshi.doyu@nokia.com>,
	Paul Walmsley <paul@pwsan.com>, Ohad Ben-Cohen <ohad@wizery.com>
Subject: Re: [RFC/PATCH 1/2] omap: mailbox: initial hwmod support
Date: Tue, 25 May 2010 09:08:54 -0700	[thread overview]
Message-ID: <87hblwneuh.fsf@deeprootsystems.com> (raw)
In-Reply-To: <AANLkTikXZRPJIeZcnUBdegFTnHIOaXUL9Ukns45GO1bh@mail.gmail.com> (Felipe Contreras's message of "Tue\, 25 May 2010 18\:23\:48 +0300")

Felipe Contreras <felipe.contreras@gmail.com> writes:

> On Tue, May 25, 2010 at 5:49 PM, Kevin Hilman
> <khilman@deeprootsystems.com> wrote:
>> Felipe Contreras <felipe.contreras@gmail.com> writes:
>>
>>> On Tue, May 25, 2010 at 3:00 AM, Kevin Hilman
>>> <khilman@deeprootsystems.com> wrote:
>>>> Felipe Contreras <felipe.contreras@gmail.com> writes:
>>>>

[...]

>>>>> -static struct platform_device mbox_device = {
>>>>> -     .name           = "omap-mailbox",
>>>>> -     .id             = -1,
>>>>> -};
>>>>> +     pdata.base_addr = hwmod->_rt_va;
>>>>
>>>> Shouldn't need the base address in pdata.  The driver should just do a
>>>> platform_get_resource() to get the physical address and then ioremap.
>>>
>>> But the hwmod code already did ioremap in _find_mpu_rt_base().
>>
>> Yes, but that's a hwmod-internal implementation detail that may
>> change, or may not be needed for some hwmods, or may be iounmapped
>> after hwmod init etc.
>
> So I have to do another ioremap()?

Yes.

But keep in mind that these L4 devices have static mappings, so there
really not an additional mapping created.

Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-05-25 16:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-22 17:25 [RFC/PATCH 0/2] omap: mailbox: hwmod experiment Felipe Contreras
2010-05-22 17:25 ` [RFC/PATCH 1/2] omap: mailbox: initial hwmod support Felipe Contreras
2010-05-24  0:59   ` Kanigeri, Hari
2010-05-24 23:56     ` Kevin Hilman
2010-05-25  0:00   ` Kevin Hilman
2010-05-25  0:29     ` Felipe Contreras
2010-05-25 14:49       ` Kevin Hilman
2010-05-25 15:23         ` Felipe Contreras
2010-05-25 16:08           ` Kevin Hilman [this message]
2010-05-22 17:25 ` [RFC/PATCH 2/2] omap: mailbox: add omap_device latency information Felipe Contreras
2010-05-24 17:29 ` [RFC/PATCH 0/2] omap: mailbox: hwmod experiment Ohad Ben-Cohen
2010-05-24 19:33   ` Felipe Contreras
2010-05-24 19:55     ` Ohad Ben-Cohen
2010-05-25  0:02       ` Kevin Hilman

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=87hblwneuh.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=felipe.contreras@gmail.com \
    --cc=hiroshi.doyu@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=paul@pwsan.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.