From: Imre Deak <imre.deak@solidboot.com>
To: Eduardo Valentin <edubezval@gmail.com>
Cc: Kyungmin Park <kmpark@infradead.org>,
Linux OMAP ML <linux-omap-open-source@linux.omap.com>
Subject: Re: TSC2101/2102
Date: Tue, 3 Apr 2007 17:36:16 +0300 [thread overview]
Message-ID: <20070403143616.GA12681@bitbox> (raw)
In-Reply-To: <a0580c510704030422u1ce3df44n45c4617fa2abb1a8@mail.gmail.com>
Hi,
On Tue, Apr 03, 2007 at 07:22:57AM -0400, Eduardo Valentin wrote:
> Hello again Imre,
>
>
> I didn't understand properly your question. My bad. Sorry.
> I used set_drvdata because it is used into lcd_h2.c (accordingly to
> my previous patch):
> @@ -117,6 +97,19 @@ struct lcd_panel h2_panel = {
>
> static int h2_panel_probe(struct platform_device *pdev)
> {
> + struct spi_device *tsc2101;
> +
> + tsc2101 = dev_get_drvdata(&pdev->dev);
> + if (tsc2101 == NULL) {
> + dev_err(&pdev->dev, "no platform data\n");
> + return -ENODEV;
> + }
>
> Of course, it is clear enough that this dev_err message is wrong.
> It must be "no driver data". My bad again. However, why do you suggest
> use platform_data instead of driver_data?
That's the standard way platforms pass init data to the driver. The
driver can then use the driver_data field for it's own purpose.
But more important would be to know why platform_data gets zero'd, since
the device core is not touching it. A workaround you're proposing might
just delay some other problem..
--Imre
next prev parent reply other threads:[~2007-04-03 14:36 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 14:06 TSC2101/2102 Imre Deak
2007-03-09 14:23 ` TSC2101/2102 andrzej zaborowski
2007-03-14 13:21 ` TSC2101/2102 Nishanth Menon
2007-03-14 17:09 ` TSC2101/2102 Imre Deak
2007-03-14 20:35 ` TSC2101/2102 Dirk Behme
2007-03-15 1:18 ` TSC2101/2102 Kyungmin Park
2007-03-15 10:23 ` TSC2101/2102 Imre Deak
2007-03-15 14:23 ` Regarding use of DirectFB Raja Mallik
2007-03-15 17:09 ` Cliff Brake
2007-03-16 0:28 ` TSC2101/2102 Kyungmin Park
2007-03-16 7:41 ` TSC2101/2102 Imre Deak
2007-03-16 8:05 ` TSC2101/2102 Kyungmin Park
2007-03-16 9:49 ` TSC2101/2102 Imre Deak
2007-03-19 2:02 ` TSC2101/2102 Kyungmin Park
2007-03-19 7:37 ` TSC2101/2102 Jarkko Nikula
2007-03-19 8:04 ` TSC2101/2102 Kyungmin Park
2007-03-19 8:37 ` TSC2101/2102 Jarkko Nikula
2007-03-19 19:22 ` TSC2101/2102 tony
2007-03-20 1:46 ` TSC2101/2102 Kyungmin Park
2007-03-20 13:27 ` TSC2101/2102 tony
2007-03-20 13:54 ` TSC2101/2102 Jarkko Nikula
2007-03-20 15:38 ` TSC2101/2102 Tony Lindgren
2007-03-21 19:24 ` TSC2101/2102 Eduardo Valentin
2007-03-22 6:48 ` TSC2101/2102 Jarkko Nikula
2007-03-30 18:49 ` TSC2101/2102 Tony Lindgren
2007-03-31 12:52 ` TSC2101/2102 Eduardo Valentin
2007-03-31 17:01 ` TSC2101/2102 Imre Deak
2007-04-02 13:43 ` TSC2101/2102 Eduardo Valentin
2007-04-02 20:23 ` TSC2101/2102 Imre Deak
2007-04-02 20:41 ` TSC2101/2102 Eduardo Valentin
2007-04-03 11:22 ` TSC2101/2102 Eduardo Valentin
2007-04-03 14:36 ` Imre Deak [this message]
2007-04-03 15:10 ` TSC2101/2102 Eduardo Valentin
2007-04-03 19:23 ` TSC2101/2102 Tony Lindgren
2007-03-29 20:26 ` TSC2101/2102 Tony Lindgren
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=20070403143616.GA12681@bitbox \
--to=imre.deak@solidboot.com \
--cc=edubezval@gmail.com \
--cc=kmpark@infradead.org \
--cc=linux-omap-open-source@linux.omap.com \
/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