From: khilman@deeprootsystems•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH/RFC] Runtime PM: ARM: subarch-specific extensions of pdev_archdata
Date: Mon, 26 Oct 2009 16:13:35 -0700 [thread overview]
Message-ID: <87k4yhagv4.fsf@deeprootsystems.com> (raw)
In-Reply-To: <f17812d70909231630i20f64328k8d604c3436094b85@mail.gmail.com> (Eric Miao's message of "Thu\, 24 Sep 2009 07\:30\:40 +0800")
Eric Miao <eric.y.miao@gmail•com> writes:
> On Thu, Sep 24, 2009 at 7:28 AM, Kevin Hilman
> <khilman@deeprootsystems•com> wrote:
>> Mikael Pettersson wrote:
>>>
>>> Eric Miao writes:
>>> ?> On Wed, Sep 23, 2009 at 9:50 AM, Kevin Hilman
>>> ?> <khilman@deeprootsystems•com> wrote:
>>> ?> > On ARM platforms, power management can be very platform specific.
>>> ?> > This patch allows ARM subarches to extend the platform_device
>>> ?> > pdev_archdata for each subarch by creating a new struct pdev_machdata
>>> ?> > and allowing each subarch to customize it as needed.
>>> ?> >
>>> ?> > As a starting point, each subarch's <mach/device.h> creates an empty
>>> ?> > struct pdev_machdata.
>>> ?> >
>>> ?> ?> Shouldn't that pdev_archdata and pdev_machdata be pointer or
>>> something
>>> ?> so that multiple platform_device can share something in common?
>>>
>>> Forcing it to be a pointer has allocation and lifetime implications.
>>> Making it a struct allows the subarch to duplicate or share
>>> (via a private pointer) data as it sees fit.
>>
>> Yes, the allocation/lifetime issues were why a struct was chosen.
>>
>
> Mmm... this makes sense to me. I'm ok with this patch - just wondering
> for the moment what to put for the pxa architecture - I'll see what davinci
> will do first, of course :)
OK, after no further comments, sending this patch to the patch system.
Kevin
next prev parent reply other threads:[~2009-10-26 23:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 1:50 [PATCH/RFC] Runtime PM: ARM: subarch-specific extensions of pdev_archdata Kevin Hilman
2009-09-23 3:54 ` Ben Dooks
2009-09-23 23:26 ` Kevin Hilman
2009-09-23 4:53 ` Eric Miao
2009-09-23 10:23 ` Mikael Pettersson
2009-09-23 23:28 ` Kevin Hilman
2009-09-23 23:30 ` Eric Miao
2009-09-23 23:36 ` Kevin Hilman
2009-10-26 23:13 ` Kevin Hilman [this message]
2010-07-22 8:06 ` [linux-pm] " Magnus Damm
2010-07-24 20:24 ` Grant Likely
2010-07-26 1:51 ` Magnus Damm
2010-08-03 16:16 ` Kevin Hilman
2010-08-04 3:56 ` Magnus Damm
2010-08-04 23:10 ` Grant Likely
2010-08-05 3:07 ` Magnus Damm
2010-08-05 15:12 ` Kevin Hilman
2010-08-04 22:54 ` Grant Likely
2010-08-05 15:19 ` Kevin Hilman
2010-08-04 22:41 ` Grant Likely
2010-08-05 2:53 ` Magnus Damm
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=87k4yhagv4.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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