linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] tty: max310x: Use dev_pm_ops
Date: Mon, 11 Mar 2013 19:35:06 +0100	[thread overview]
Message-ID: <513E23DA.90100@metafoo.de> (raw)
In-Reply-To: <1363025431.558252587@f43.mail.ru>

On 03/11/2013 07:10 PM, Alexander Shiyan wrote:
> Hello.
> 
>> Use dev_pm_ops instead of the deprecated legacy suspend/resume for the
>> max310x driver.
>>
>> Cc: Alexander Shiyan <shc_work@mail.ru>
>> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
>> ---
>>  drivers/tty/serial/max310x.c | 24 ++++++++++++++++--------
>>  1 file changed, 16 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/tty/serial/max310x.c b/drivers/tty/serial/max310x.c
>> index 0c2422c..8941e64 100644
>> --- a/drivers/tty/serial/max310x.c
>> +++ b/drivers/tty/serial/max310x.c
>> @@ -881,12 +881,14 @@ static struct uart_ops max310x_ops = {
>>  	.verify_port	= max310x_verify_port,
>>  };
>>  
>> -static int max310x_suspend(struct spi_device *spi, pm_message_t state)
>> +#ifdef CONFIG_PM_SLEEP
>> +
>> +static int max310x_suspend(struct device *dev)
>>  {
>>  	int ret;
>> -	struct max310x_port *s = dev_get_drvdata(&spi->dev);
>> +	struct max310x_port *s = dev_get_drvdata(dev);
>>  
>> -	dev_dbg(&spi->dev, "Suspend\n");
>> +	dev_dbg(dev, "Suspend\n");
>>  
>>  	ret = uart_suspend_port(&s->uart, &s->port);
>>  
>> @@ -905,11 +907,11 @@ static int max310x_suspend(struct spi_device *spi, pm_message_t state)
>>  	return ret;
>>  }
>>  
>> -static int max310x_resume(struct spi_device *spi)
>> +static int max310x_resume(struct device *dev)
>>  {
>> -	struct max310x_port *s = dev_get_drvdata(&spi->dev);
>> +	struct max310x_port *s = dev_get_drvdata(dev);
>>  
>> -	dev_dbg(&spi->dev, "Resume\n");
>> +	dev_dbg(dev, "Resume\n");
>>  
>>  	if (s->pdata->suspend)
>>  		s->pdata->suspend(0);
>> @@ -928,6 +930,13 @@ static int max310x_resume(struct spi_device *spi)
>>  	return uart_resume_port(&s->uart, &s->port);
>>  }
>>  
>> +static SIMPLE_DEV_PM_OPS(max310x_pm_ops, max310x_suspend, max310x_resume);
>> +#define MAX310X_PM_OPS (&max310x_pm_ops)
>> +
>> +#else
>> +#define MAX310X_PM_OPS NULL
>> +#endif
>> +
>>  #ifdef CONFIG_GPIOLIB
>>  static int max310x_gpio_get(struct gpio_chip *chip, unsigned offset)
>>  {
>> @@ -1242,11 +1251,10 @@ static struct spi_driver max310x_driver = {
>>  	.driver = {
>>  		.name	= "max310x",
>>  		.owner	= THIS_MODULE,
>> +		.pm	= MAX310X_PM_OPS,
> 
> Check for CONFIG_PM_SLEEP not necessary at all.
> <linux/pm.h> will do all for us.

No it wont, you'll end up with a dev_pm_ops struct full of zeros and two
warnings from your compiler about unused functions.

> 
>>  	},
>>  	.probe		= max310x_probe,
>>  	.remove		= max310x_remove,
>> -	.suspend	= max310x_suspend,
>> -	.resume		= max310x_resume,
>>  	.id_table	= max310x_id_table,
>>  };
>>  module_spi_driver(max310x_driver);
>> -- 
>> 1.8.0
> 
> ---


  reply	other threads:[~2013-03-11 18:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-11 17:44 [PATCH 1/4] tty: max3100: Use dev_pm_ops Lars-Peter Clausen
2013-03-11 17:44 ` [PATCH 2/4] tty: max310x: " Lars-Peter Clausen
2013-03-11 18:10   ` Alexander Shiyan
2013-03-11 18:35     ` Lars-Peter Clausen [this message]
2013-03-11 18:41       ` Re[2]: " Alexander Shiyan
2013-03-11 18:49         ` Lars-Peter Clausen
2013-03-11 18:54           ` Re[2]: " Alexander Shiyan
2013-03-11 19:09             ` Lars-Peter Clausen
2013-03-11 17:44 ` [PATCH 3/4] tty: mrst_max3110: " Lars-Peter Clausen
2013-03-11 17:44 ` [PATCH 4/4] tty: ifx6x60: Remove unused suspend/resume callbacks Lars-Peter Clausen

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=513E23DA.90100@metafoo.de \
    --to=lars@metafoo.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=shc_work@mail.ru \
    /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).