From: akpm@linux-foundation.org (Andrew Morton)
To: linux-arm-kernel@lists.infradead.org
Subject: (arm-)global platform device registration functions
Date: Wed, 29 Dec 2010 12:37:40 -0800 [thread overview]
Message-ID: <20101229123740.c39238f8.akpm@linux-foundation.org> (raw)
In-Reply-To: <20101229162512.GI14221@pengutronix.de>
On Wed, 29 Dec 2010 17:25:12 +0100
Uwe Kleine-K__nig <u.kleine-koenig@pengutronix.de> wrote:
> Hello,
>
> some time ago I started to dynamically allocate platform_devices for
> arm/plat-mxc. For that purpose I added many functions, see
> arch/arm/plat-mxc/include/mach/devices-common.h [1]. Now arm/arch-mxs
> want to do the same, so I wonder if it would be sensible to do something
> like this more globally (either for arm or better kernel global).
>
Sounds sensible to me, although I don't really understand what you've
done - didn't platform_device_alloc() already "dynamically allocate
platform_devices"?
If you were to implement this common infrastructure, there may be
already-existing code which could use it. How would we locate that?
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: (arm-)global platform device registration functions
Date: Wed, 29 Dec 2010 12:37:40 -0800 [thread overview]
Message-ID: <20101229123740.c39238f8.akpm@linux-foundation.org> (raw)
In-Reply-To: <20101229162512.GI14221@pengutronix.de>
On Wed, 29 Dec 2010 17:25:12 +0100
Uwe Kleine-K__nig <u.kleine-koenig@pengutronix.de> wrote:
> Hello,
>
> some time ago I started to dynamically allocate platform_devices for
> arm/plat-mxc. For that purpose I added many functions, see
> arch/arm/plat-mxc/include/mach/devices-common.h [1]. Now arm/arch-mxs
> want to do the same, so I wonder if it would be sensible to do something
> like this more globally (either for arm or better kernel global).
>
Sounds sensible to me, although I don't really understand what you've
done - didn't platform_device_alloc() already "dynamically allocate
platform_devices"?
If you were to implement this common infrastructure, there may be
already-existing code which could use it. How would we locate that?
next prev parent reply other threads:[~2010-12-29 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 16:25 (arm-)global platform device registration functions Uwe Kleine-König
2010-12-29 16:25 ` Uwe Kleine-König
2010-12-29 20:37 ` Andrew Morton [this message]
2010-12-29 20:37 ` Andrew Morton
2010-12-29 21:18 ` Uwe Kleine-König
2010-12-29 21:18 ` Uwe Kleine-König
2010-12-30 10:03 ` Arnd Bergmann
2010-12-30 10:03 ` Arnd Bergmann
2010-12-30 10:15 ` Uwe Kleine-König
2010-12-30 10:15 ` Uwe Kleine-König
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=20101229123740.c39238f8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--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.