[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <200907050144.40444.rjw@sisk.pl>
Date: Sun, 5 Jul 2009 01:44:39 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Magnus Damm <magnus.damm@...il.com>
Cc: linux-kernel@...r.kernel.org, paul@...an.com,
khilman@...prootsystems.com, gregkh@...e.de,
stern@...land.harvard.edu, linux-pm@...ts.linux-foundation.org
Subject: Re: [PATCH] Driver Core: Add platform device arch data V3
On Wednesday 10 June 2009, Magnus Damm wrote:
> From: Magnus Damm <damm@...l.co.jp>
>
> Allow architecture specific data in struct platform_device V3.
>
> With this patch struct pdev_archdata is added to struct
> platform_device, similar to struct dev_archdata in found in
> struct device. Useful for architecture code that needs to
> keep extra data associated with each platform device.
>
> Struct pdev_archdata is different from dev.platform_data, the
> convention is that dev.platform_data points to driver-specific
> data. It may or may not be required by the driver. The format
> of this depends on driver but is the same across architectures.
>
> The structure pdev_archdata is a place for architecture specific
> data. This data is handled by architecture specific code (for
> example runtime PM), and since it is architecture specific it
> should _never_ be touched by device driver code. Exactly like
> struct dev_archdata but for platform devices.
>
> Signed-off-by: Magnus Damm <damm@...l.co.jp>
> ---
>
> Applies to next-20090610.
>
> Changes since V2:
> - updated commit message, thanks to Rafael for feedback
>
> Changes since V1:
> - post to lkml, keep linux-pm cc:ed
> - add struct pdev_archdata to asm-generic
> - add struct pdev_archdata to non-generic architectures
> - drop Kconfig bits
The patch is now in the linux-next branch of the suspend-2.6 tree. I'll move
it into the for-linus branch, which is not rebased, if it's not reported to
cause any problems in the next few days.
Best,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists