From: Kevin Hilman <khilman@ti.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH v2 1/6] OMAP: omap_device: Add omap_hwmod_name_get_dev
Date: Mon, 26 Sep 2011 11:24:33 -0700 [thread overview]
Message-ID: <87zkhrcgbi.fsf@ti.com> (raw)
In-Reply-To: <1314973520-3585-2-git-send-email-b-cousson@ti.com> (Benoit Cousson's message of "Fri, 2 Sep 2011 16:25:15 +0200")
Benoit Cousson <b-cousson@ti.com> writes:
> From: Nishanth Menon <nm@ti.com>
>
> An API which translates a standard hwmod name to corresponding
> platform_device is useful for drivers when they need to look up the
> device associated with a hwmod name to map back into the device
> structure pointers. These ideally should be used by drivers in
> mach directory. Using a generic hwmod name like "gpu" instead of
> the actual device name which could change in the future, allows
> us to:
> a) Could in effect help replace apis such as omap2_get_mpuss_device,
> omap2_get_iva_device, omap2_get_l3_device, omap4_get_dsp_device,
> etc..
> b) Scale to more devices rather than be restricted to named functions
> c) Simplify driver's platform_data from passing additional fields
> all doing the same thing with different function pointer names
> just for accessing a different device name.
>
> Provide an omap_hwmod_name_get_dev helper function to convert
> hwmod to device pointer.
> This wrapper provides ability for drivers to convert directly
> from hwmod name back to device pointer without having to handle
> this on a driver by driver basis.
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> [b-cousson@ti.com: Adapt it to the new pdev pointer inside od,
> remove the unneeded helpers, and fold the next patch here]
> Signed-off-by: Benoit Cousson <b-cousson@ti.com>
I replied to wrong version of patch before, here's the comment again:
One other comment on the API here.
This is an omap_hwmod_* API being added to omap_device.h.
Seems like the function name should be something more like:
omap_device_get_by_name(), or probably omap_device_get_by_hwmod_name().
Kevin
next prev parent reply other threads:[~2011-09-26 18:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 14:25 [PATCH v2 0/6] OMAP: omap_device cleanup before device-tree integration Benoit Cousson
2011-09-02 14:25 ` [PATCH v2 1/6] OMAP: omap_device: Add omap_hwmod_name_get_dev Benoit Cousson
2011-09-26 18:24 ` Kevin Hilman [this message]
2011-09-02 14:25 ` [PATCH v2 2/6] OMAP3: beagle-board: Use the omap_hwmod_name_get_dev API Benoit Cousson
2011-09-02 14:25 ` [PATCH v2 3/6] OMAP2+: pm: Use hwmod name instead of dev pointer Benoit Cousson
2011-09-02 14:25 ` [PATCH v2 4/6] OMAP2+: pm: Remove static devices variable for mpu, dsp, iva and l3 PM Benoit Cousson
2011-09-02 14:25 ` [PATCH v2 5/6] OMAP: omap_device: Create a default omap_device_pm_latency Benoit Cousson
2011-09-16 11:52 ` Cousson, Benoit
2011-09-16 16:41 ` Kevin Hilman
2011-09-02 14:25 ` [PATCH v2 6/6] OMAP2+: devices: Remove all omap_device_pm_latency structures Benoit Cousson
2011-09-26 22:36 ` [PATCH v2 0/6] OMAP: omap_device cleanup before device-tree integration 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=87zkhrcgbi.fsf@ti.com \
--to=khilman@ti.com \
--cc=b-cousson@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.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