From: gregkh@suse.de (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clkdev: add support to lookup for early platform device
Date: Wed, 27 Apr 2011 15:12:04 -0700 [thread overview]
Message-ID: <20110427221204.GC12787@suse.de> (raw)
In-Reply-To: <20110427150057.GH29103@game.jcrosoft.org>
On Wed, Apr 27, 2011 at 05:00:57PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 12:47 Wed 27 Apr , Jean-Christophe PLAGNIOL-VILLARD wrote:
> > On 12:31 Wed 27 Apr , Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > On 09:42 Wed 27 Apr , Russell King - ARM Linux wrote:
> > > > On Wed, Apr 20, 2011 at 04:05:14PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > > > early platform device may do not have a device name as the slab is not yet
> > > > > available. So to search a clock base on the dev_id we need to search first the
> > > > > device base name and then the id
> > > >
> > > > I really don't like this. IDs are platform device specific, and this is
> > > > a platform devince independent layer.
> > > >
> > > > If you want to do this, then add a platform_device_clk_get() call, which
> > > > takes the platform device and connection id. Uses the platform device
> > > > infrastructure to format the device name, and use clk_get_sys() to look
> > > > up the device/connection id from that.
> > > I do not want to alloc a string in the clkdev
> > > but if you prefer
> > I check we can not do so
> > if slab is not available we can not use kmalloc
> >
> > so we can not generate the dev.init_name
> I check also we can not use the bootmem as it's too early in the init
> so allocate the dev_id is not possible
>
> use a satic buffer I'm not so happy about it
> the only other solution is this one
>
> which Greg or you prefer
I have no idea what you are asking, please be more specific, hopefully
including a patch showing what you are referring to.
thanks,
greg k-h
next prev parent reply other threads:[~2011-04-27 22:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 14:05 [PATCH] clkdev: add support to lookup for early platform device Jean-Christophe PLAGNIOL-VILLARD
2011-04-27 8:42 ` Russell King - ARM Linux
2011-04-27 10:31 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-27 10:47 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-27 15:00 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-27 22:12 ` Greg KH [this message]
2011-04-28 2:09 ` Paul Mundt
2011-04-28 2:45 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-28 3:08 ` Paul Mundt
2011-04-28 3:17 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-28 3:20 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-28 3:35 ` Magnus Damm
2011-04-28 3:29 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-28 3:44 ` Magnus Damm
2011-04-28 8:33 ` Russell King - ARM Linux
2011-04-28 9:28 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-28 3:38 ` Paul Mundt
2011-04-28 4:31 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-28 4:46 ` Saravana Kannan
2011-04-28 4:50 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-28 5:12 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-28 5:47 ` Magnus Damm
2011-04-28 8:35 ` Russell King - ARM Linux
2011-04-28 9:26 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-28 10:07 ` Russell King - ARM Linux
2011-04-28 11:19 ` Jean-Christophe PLAGNIOL-VILLARD
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=20110427221204.GC12787@suse.de \
--to=gregkh@suse.de \
--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 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.