Linux IIO development
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>,
	ktsai@capellamicro.com, jic23@kernel.org, lars@metafoo.de
Cc: Wahaj <wahajaved@protonmail.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: light: cm32181: Fix PM support on system with 2 I2C resources
Date: Tue, 17 Jan 2023 22:02:29 +0100	[thread overview]
Message-ID: <a204fdeb-b2bb-5c61-8a75-de6dd244892a@redhat.com> (raw)
In-Reply-To: <5c95d25b-ff26-053b-efc8-5f6fd979c7e2@redhat.com>

Hi,

On 1/17/23 18:19, Hans de Goede wrote:
> Hi,
> 
> On 1/17/23 17:09, Kai-Heng Feng wrote:
>> Commit c1e62062ff54 ("iio: light: cm32181: Handle CM3218 ACPI devices
>> with 2 I2C resources") creates a second client for the actual I2C
>> address, but the "struct device" passed to PM ops is the first client
>> that can't talk to the sensor.
>>
>> That means the I2C transfers in both suspend and resume routines can
>> fail and blocking the whole suspend process.
>>
>> Instead of using the first client for I2C transfer, store the cm32181
>> private struct on both cases so the PM ops can get the correct I2C
>> client to perfrom suspend and resume.
>>
>> Fixes: 68c1b3dd5c48 ("iio: light: cm32181: Add PM support")
>> Tested-by: Wahaj <wahajaved@protonmail.com>
>> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
> 
> Thank you for this fix. I had looking into this on my todo list,
> since I have been seeing some bug reports about this too.
> 
> One remark inline:
> 
>> ---
>>  drivers/iio/light/cm32181.c | 11 +++++++----
>>  1 file changed, 7 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/iio/light/cm32181.c b/drivers/iio/light/cm32181.c
>> index 001055d097509..0f319c891353c 100644
>> --- a/drivers/iio/light/cm32181.c
>> +++ b/drivers/iio/light/cm32181.c
>> @@ -440,6 +440,8 @@ static int cm32181_probe(struct i2c_client *client)
>>  	if (!indio_dev)
>>  		return -ENOMEM;
>>  
>> +	i2c_set_clientdata(client, indio_dev);
>> +
> 
> Why move this up, the suspend/resume callbacks cannot run until
> probe() completes, so no need for this change.
> 
>>  	/*
>>  	 * Some ACPI systems list 2 I2C resources for the CM3218 sensor, the
>>  	 * SMBus Alert Response Address (ARA, 0x0c) and the actual I2C address.
>> @@ -458,9 +460,9 @@ static int cm32181_probe(struct i2c_client *client)
>>  		client = i2c_acpi_new_device(dev, 1, &board_info);
>>  		if (IS_ERR(client))
>>  			return PTR_ERR(client);
>> -	}
>>  
>> -	i2c_set_clientdata(client, indio_dev);
>> +		i2c_set_clientdata(client, indio_dev);
>> +	}
> 
> And moving it inside the if block here (instead of just dropping it)
> is also weird. I guess you meant to just delete it since you moved it up.
> 
>>  
>>  	cm32181 = iio_priv(indio_dev);
>>  	cm32181->client = client;
> 
> Also note that the ->client used in suspend/resume now is not set until
> here, so moving the i2c_set_clientdata() up really does not do anything.
> 
> I beleive it would be best to just these 2 hunks from the patch and
> only keep the changes to the suspend/resume callbacks.

p.s.

I believe that this will likely also fix:
https://bugzilla.redhat.com/show_bug.cgi?id=2152281

Can you please add a:

Link: https://bugzilla.redhat.com/show_bug.cgi?id=2152281

to the next version.

Regards,

Hans



> 
> 
>> @@ -490,7 +492,8 @@ static int cm32181_probe(struct i2c_client *client)
>>  
>>  static int cm32181_suspend(struct device *dev)
>>  {
>> -	struct i2c_client *client = to_i2c_client(dev);
>> +	struct cm32181_chip *cm32181 = iio_priv(dev_get_drvdata(dev));
>> +	struct i2c_client *client = cm32181->client;
>>  
>>  	return i2c_smbus_write_word_data(client, CM32181_REG_ADDR_CMD,
>>  					 CM32181_CMD_ALS_DISABLE);
>> @@ -498,8 +501,8 @@ static int cm32181_suspend(struct device *dev)
>>  
>>  static int cm32181_resume(struct device *dev)
>>  {
>> -	struct i2c_client *client = to_i2c_client(dev);
>>  	struct cm32181_chip *cm32181 = iio_priv(dev_get_drvdata(dev));
>> +	struct i2c_client *client = cm32181->client;
>>  
>>  	return i2c_smbus_write_word_data(client, CM32181_REG_ADDR_CMD,
>>  					 cm32181->conf_regs[CM32181_REG_ADDR_CMD]);
> 


  reply	other threads:[~2023-01-17 23:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 16:09 [PATCH] iio: light: cm32181: Fix PM support on system with 2 I2C resources Kai-Heng Feng
2023-01-17 17:19 ` Hans de Goede
2023-01-17 21:02   ` Hans de Goede [this message]
2023-01-18  3:29   ` Kai-Heng Feng
2023-01-18  5:15     ` Kai-Heng Feng
2023-01-18 10:52       ` Hans de Goede
2023-01-18 17:03         ` Kai-Heng Feng

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=a204fdeb-b2bb-5c61-8a75-de6dd244892a@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=jic23@kernel.org \
    --cc=kai.heng.feng@canonical.com \
    --cc=ktsai@capellamicro.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wahajaved@protonmail.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