From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 01/04] Driver Core: Add platform device arch data
Date: Thu, 28 May 2009 21:26:56 +0000 [thread overview]
Message-ID: <200905282326.57431.rjw@sisk.pl> (raw)
In-Reply-To: <20090527100633.29671.83531.sendpatchset@rx1.opensource.se>
On Wednesday 27 May 2009, Magnus Damm wrote:
> From: Magnus Damm <damm@igel.co.jp>
>
> Allow architecture specific data in struct platform_device.
> Platform device data is needed by the runtime pm code. A similar
> struct already exists for struct device.
>
> The architecture specific asm/device.h file needs to provide
> struct pdev_archdata if CONFIG_HAVE_PLATFORM_DEVICE_DATA is set.
>
> Signed-off-by: Magnus Damm <damm@igel.co.jp>
> ---
>
> Optionally we can make use of struct device archdata instead,
> but since the runtime device pm is limited to platform devices
> it makes sense to make this data platform device specific imo.
>
> arch/Kconfig | 3 +++
> include/linux/platform_device.h | 5 +++++
> 2 files changed, 8 insertions(+)
>
> --- 0001/arch/Kconfig
> +++ work/arch/Kconfig 2009-05-15 14:51:35.000000000 +0900
> @@ -112,3 +112,6 @@ config HAVE_DMA_API_DEBUG
>
> config HAVE_DEFAULT_NO_SPIN_MUTEXES
> bool
> +
> +config HAVE_PLATFORM_DEVICE_ARCHDATA
Hmm. Do we really need yet another CONFIG_ option for that?
> + bool
> --- 0001/include/linux/platform_device.h
> +++ work/include/linux/platform_device.h 2009-05-15 16:59:01.000000000 +0900
> @@ -23,6 +23,11 @@ struct platform_device {
> void *platform_data;
>
> struct platform_device_id *id_entry;
> +
> +#ifdef CONFIG_HAVE_PLATFORM_DEVICE_ARCHDATA
> + /* arch specific additions */
> + struct pdev_archdata archdata;
> +#endif
> };
>
> #define platform_get_device_id(pdev) ((pdev)->id_entry)
next prev parent reply other threads:[~2009-05-28 21:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 10:06 [PATCH 01/04] Driver Core: Add platform device arch data Magnus Damm
2009-05-28 21:26 ` Rafael J. Wysocki [this message]
2009-05-29 5:07 ` Magnus Damm
2009-05-29 5:51 ` Paul Mundt
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=200905282326.57431.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-sh@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox