From: "Jaya Kumar" <jayakumar.lkml@gmail.com>
To: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
Cc: "Linux Kernel Development" <linux-kernel@vger.kernel.org>
Subject: Re: Clarifying platform_device_unregister
Date: Tue, 1 Apr 2008 00:47:54 -0700 [thread overview]
Message-ID: <45a44e480804010047m36a9b8e3p97910308ed5677fb@mail.gmail.com> (raw)
In-Reply-To: <20080401051947.GD18041@anvil.corenet.prv>
On Mon, Mar 31, 2008 at 10:19 PM, Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:
> On Mon, Mar 31, 2008 at 09:14:35PM -0400, Jaya Kumar wrote:
> > mytest_device->dev.platform_data = &mydata;
>
> Platform device code does kfree(pdev->dev.platform_data) unpon
> unregistration, so it is not a good idea to assign address of
> statically-allocated variable here. You should be using:
>
> platform_device_add_data(mytest_device, &mydata, sizeof(mydata));
>
That's interesting. I noticed though that a lot of platform device
code assigns a statically allocated structure to platform_data. For
example:
arch/arm/mach-pxa/corgi_pm.c
static struct sharpsl_charger_machinfo corgi_pm_machinfo = {
...
}
corgipm_device->dev.platform_data = &corgi_pm_machinfo;
same with spitz_pm.c.
egrep "platform_data.*=.*\&" *.c shows quite a lot of users doing
that. I guess most of these below are probably okay since these
drivers can't be rmmoded.
corgi.c: .platform_data = &corgi_scoop_setup,
corgi.c: .platform_data = &corgi_bl_machinfo,
corgi.c: .platform_data = &corgi_ts_machinfo,
corgi_lcd.c: .platform_data = &corgi_fb_info,
corgi_pm.c: corgipm_device->dev.platform_data = &corgi_pm_machinfo;
generic.c: .platform_data = &pxa_udc_info,
lpd270.c: .platform_data = &lpd270_flash_data[0],
lpd270.c: .platform_data = &lpd270_flash_data[1],
lubbock.c: .platform_data = &pxa_ssp_master_info,
lubbock.c: .platform_data = &ads_info,
lubbock.c: .platform_data = &lubbock_flash_data[0],
lubbock.c: .platform_data = &lubbock_flash_data[1],
mainstone.c: .dev = { .platform_data = &mst_audio_ops },
mainstone.c: .platform_data = &mst_flash_data[0],
mainstone.c: .platform_data = &mst_flash_data[1],
poodle.c: .platform_data = &poodle_scoop_setup,
poodle.c: .platform_data = &poodle_ts_machinfo,
spitz.c: .platform_data = &spitz_scoop_setup,
spitz.c: .platform_data = &spitz_scoop2_setup,
spitz.c: .platform_data = &spitz_bl_machinfo,
spitz.c: .platform_data = &spitz_ts_machinfo,
spitz_pm.c: spitzpm_device->dev.platform_data = &spitz_pm_machinfo;
tosa.c: .platform_data = &tosa_scoop_setup,
tosa.c: .platform_data = &tosa_scoop_jc_setup,
trizeps4.c: .platform_data = &trizeps4_flash_data,
next prev parent reply other threads:[~2008-04-01 7:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 1:14 Jaya Kumar
2008-04-01 5:19 ` Dmitry Torokhov
2008-04-01 7:47 ` Jaya Kumar [this message]
2008-04-01 14:54 ` Dmitry Torokhov
2008-04-02 1:57 ` Jaya Kumar
2008-04-05 12:07 ` Richard Purdie
2008-04-05 11:44 ` Richard Purdie
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=45a44e480804010047m36a9b8e3p97910308ed5677fb@mail.gmail.com \
--to=jayakumar.lkml@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®