From: Felipe Contreras <felipe.contreras@gmail.com>
To: "Kanigeri, Hari" <h-kanigeri2@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>,
Hiroshi Doyu <hiroshi.doyu@nokia.com>,
Ohad Ben-Cohen <ohad@wizery.com>
Subject: Re: [RFC/PATCH 6/8] omap: mailbox: more more stuff to omap2_mbox_init
Date: Mon, 3 May 2010 22:22:30 +0300 [thread overview]
Message-ID: <n2z94a0d4531005031222t10ea8b8dm3de50b83936fafac@mail.gmail.com> (raw)
In-Reply-To: <8F7AF80515AF0D4D93307E594F3CB40E4B791DED@dlee03.ent.ti.com>
On Mon, May 3, 2010 at 9:50 PM, Kanigeri, Hari <h-kanigeri2@ti.com> wrote:
>> > Small suggestion...if we are re-organizing can we make it look similar
>> to how iommu is structured? This way we can maintain consistency.
>>
>> I thought I did. What exactly do you have in mind?
>
> 1. What Tony mentioned in another email about using #ifdefs for the platforms. That will be bring close to what is in omap-iommu.c
>
> 2. Compare iommu_get with mailbox_get. iommu_get uses driver_find_device to get the iommu structure. I guess we can apply the same logic to get mailbox structure. This way we can get rid of omap_mbox_register, omap_mbox_unregister, and find_mboxes functions.
As I mentioned in another thread[1], we can't really do that because
the mailboxes are not really separate devices, but different irqs of
the same device. They all share the same resources (mem, and even
irqs), so effectively they are all one device.
[1] http://article.gmane.org/gmane.linux.ports.arm.omap/34921
--
Felipe Contreras
--
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
next prev parent reply other threads:[~2010-05-03 19:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-02 23:59 [RFC/PATCH 0/8] omap: mailbox: split platform_driver Felipe Contreras
2010-05-02 23:59 ` [RFC/PATCH 1/8] omap: mailbox: trivial cleanups Felipe Contreras
2010-05-02 23:59 ` [RFC/PATCH 2/8] omap: mailbox: reorganize structures Felipe Contreras
2010-05-02 23:59 ` [RFC/PATCH 3/8] omap: mailbox: 2420 should be detected at run-time Felipe Contreras
2010-05-02 23:59 ` [RFC/PATCH 4/8] omap: mailbox: reorganize omap2 registering Felipe Contreras
2010-05-03 0:02 ` [RFC/PATCH 5/8] omap: mailbox: reorganize omap2 platform_device Felipe Contreras
2010-05-03 18:10 ` Tony Lindgren
2010-05-03 18:14 ` Felipe Contreras
2010-05-03 0:02 ` [RFC/PATCH 6/8] omap: mailbox: more more stuff to omap2_mbox_init Felipe Contreras
2010-05-03 13:42 ` Kanigeri, Hari
2010-05-03 15:08 ` Felipe Contreras
2010-05-03 18:50 ` Kanigeri, Hari
2010-05-03 19:22 ` Felipe Contreras [this message]
2010-05-04 6:04 ` Hiroshi DOYU
2010-05-04 8:42 ` Felipe Contreras
2010-05-03 0:02 ` [RFC/PATCH 7/8] omap: mailbox: split platform_driver Felipe Contreras
2010-05-03 0:02 ` [RFC/PATCH 8/8] omap: mailbox: always built-in omap2 platform data Felipe Contreras
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=n2z94a0d4531005031222t10ea8b8dm3de50b83936fafac@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=h-kanigeri2@ti.com \
--cc=hiroshi.doyu@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=tony@atomide.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 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).