From: Shine Liu <liuxian@redflag-linux.com>
To: Ben Dooks <ben@simtec.co.uk>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Arnaud Patard <arnaud.patard@rtp-net.org>,
Simtec Linux Team <linux@simtec.co.uk>
Subject: Re: [patch 1/1] TOUCHSCREEN: S3C24XX touchscreen driver from Arnaud Patard.
Date: Thu, 19 Nov 2009 14:15:31 +0800 [thread overview]
Message-ID: <1258611331.2676.53.camel@shinel> (raw)
In-Reply-To: <20091119025930.GA20172@core.coreip.homeip.net>
Hi Ben,
On Wed, 2009-11-18 at 18:59 -0800, Dmitry Torokhov wrote:
> > +#ifdef CONFIG_PM
> > +static int s3c2410ts_suspend(struct platform_device *pdev, pm_message_t state)
> > +{
> > + writel(TSC_SLEEP, ts.io + S3C2410_ADCTSC);
> > + disable_irq(ts.irq_tc);
> > + clk_disable(ts.clock);
> > +
> > + return 0;
> > +}
> > +
> > +static int s3c2410ts_resume(struct platform_device *pdev)
> > +{
> > + struct s3c2410_ts_mach_info *info = pdev->dev.platform_data;
> > +
> > + clk_enable(ts.clock);
> > +
> > + /* Initialise registers */
> > + if ((info->delay & 0xffff) > 0)
> > + writel(info->delay & 0xffff, ts.io + S3C2410_ADCDLY);
> > +
> > + writel(WAIT4INT | INT_DOWN, ts.io + S3C2410_ADCTSC);
> > +
> > + return 0;
> > +}
> > +
> > +#else
> > +#define s3c2410ts_suspend NULL
> > +#define s3c2410ts_resume NULL
> > +#endif
> > +
> > +static struct platform_device_id s3cts_driver_ids[] = {
> > + { "s3c2410-ts", 0 },
> > + { "s3c2440-ts", 1 },
> > + { }
> > +};
> > +MODULE_DEVICE_TABLE(platform, s3cts_driver_ids);
> > +
> > +static struct platform_driver s3c_ts_driver = {
> > + .driver = {
> > + .name = "s3c24xx-ts",
> > + .owner = THIS_MODULE,
> > + },
> > + .id_table = s3cts_driver_ids,
> > + .probe = s3c2410ts_probe,
> > + .remove = s3c2410ts_remove,
>
> __devexit_p()
>
> > + .suspend = s3c2410ts_suspend,
> > + .resume = s3c2410ts_resume,
>
> Switch to pm_ops.
For these comments from Dmitry I have implemented in my patch last month
send to linux-input. You can refer
http://patchwork.kernel.org/patch/54933/ which maybe save some time for
you.
Regards,
Shine Liu
next prev parent reply other threads:[~2009-11-19 6:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091118232939.201290297@fluff.org.uk>
2009-11-18 23:29 ` [patch 1/1] TOUCHSCREEN: S3C24XX touchscreen driver from Arnaud Patard Ben Dooks
2009-11-19 1:45 ` Ramax Lo
2009-11-19 2:59 ` Dmitry Torokhov
2009-11-19 5:47 ` Harald Welte
2009-11-19 6:15 ` Shine Liu [this message]
2009-11-19 11:34 ` Ben Dooks
2009-11-19 13:52 ` Daniel Silverstone
2009-11-19 17:03 ` Dmitry Torokhov
2009-11-19 17:12 ` Russell King - ARM Linux
2009-11-19 17:48 ` Ben Dooks
2009-11-19 17:14 ` Dmitry Torokhov
2009-11-27 7:31 ` Pavel Machek
2009-11-19 5:46 ` Shine Liu
2009-11-19 10:37 ` Mark Brown
2009-11-19 12:06 ` Ben Dooks
2009-11-19 8:04 ` Vasily Khoruzhick
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=1258611331.2676.53.camel@shinel \
--to=liuxian@redflag-linux.com \
--cc=arnaud.patard@rtp-net.org \
--cc=ben@simtec.co.uk \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@simtec.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).