linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
	Wolfram Sang <wsa@the-dreams.de>, Len Brown <lenb@kernel.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
	Takashi Iwai <tiwai@suse.de>,
	linux-i2c@vger.kernel.org, Lan Tianyu <tianyu.lan@intel.com>
Subject: Re: [PATCH v2 2/2] i2c: designware: Disable pm for PMIC i2c-bus even if there is no _SEM method
Date: Thu, 9 Mar 2017 17:02:24 +0200	[thread overview]
Message-ID: <fcc97084-c2b0-150c-ad85-3ec42fd192a2@linux.intel.com> (raw)
In-Reply-To: <8c2c5e0e-8678-e572-3f7a-3d62853e9b21@linux.intel.com>

On 03/09/17 17:00, Jarkko Nikula wrote:
> + Tianyu
>
> On 03/08/17 10:47, Hans de Goede wrote:
>> Cherrytrail devices use the dw i2c-bus with uid 7 to access their PMIC.
>> Even if the i2c-bus to the PMIC is not shared with the SoC's P-Unit
>> and i2c-designware-baytrail.c thus does not set the pm_disabled flag,
>> we still need to disable pm so that ACPI PMIC opregions can access the
>> PMIC during late-suspend and early-resume.
>>
>> This fixes errors like these blocking suspend:
>>
>>   i2c_designware 808622C1:06: timeout waiting for bus ready
>>   ACPI Exception: AE_ERROR, Returned by Handler for [UserDefinedRegion]
>>   acpi 80860F14:02: Failed to change power state to D3hot
>>   PM: late suspend of devices failed
>>
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>> ---
>>  drivers/i2c/busses/i2c-designware-platdrv.c | 15 +++++++++++++++
>>  1 file changed, 15 insertions(+)
>>
>> diff --git a/drivers/i2c/busses/i2c-designware-platdrv.c
>> b/drivers/i2c/busses/i2c-designware-platdrv.c
>> index 8ed96dd..08d609e 100644
>> --- a/drivers/i2c/busses/i2c-designware-platdrv.c
>> +++ b/drivers/i2c/busses/i2c-designware-platdrv.c
>> @@ -94,7 +94,10 @@ static void dw_i2c_acpi_params(struct
>> platform_device *pdev, char method[],
>>  static int dw_i2c_acpi_configure(struct platform_device *pdev)
>>  {
>>      struct dw_i2c_dev *dev = platform_get_drvdata(pdev);
>> +    acpi_handle handle = ACPI_HANDLE(&pdev->dev);
>>      const struct acpi_device_id *id;
>> +    struct acpi_device *adev;
>> +    const char *uid;
>>
>>      dev->adapter.nr = -1;
>>      dev->tx_fifo_depth = 32;
>> @@ -114,6 +117,18 @@ static int dw_i2c_acpi_configure(struct
>> platform_device *pdev)
>>      if (id && id->driver_data)
>>          dev->flags |= (u32)id->driver_data;
>>
>> +    if (acpi_bus_get_device(handle, &adev))
>> +        return -ENODEV;
>> +
>> +    /*
>> +     * Cherrytrail I2C7 gets used for the PMIC which gets accessed
>> +     * through ACPI opregions during late suspend / early resume
>> +     * disable pm for it.
>> +     */
>> +    uid = adev->pnp.unique_id;
>> +    if ((dev->flags & MODEL_CHERRYTRAIL) && !strcmp(uid, "7"))
>> +        dev->pm_disabled = true;
>> +
>
> I'm fine with this but wondering can this be detected any other way than
> hardcoded bus number.
>
> Tianyu: You are the author of 5d98e61d337c ("I2C/ACPI: Add i2c ACPI
> operation region support"). Do you know is there way to see is there a
> PMIC connected to the bus?
>
> Jarkko Nikula <jarkko.nikula@linux.intel.com>

Here too:

Acked-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>

  reply	other threads:[~2017-03-09 15:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08  8:47 [PATCH v2 0/2] i2c: designware: Never suspend i2c-busses used for system PMICs Hans de Goede
2017-03-08  8:47 ` [PATCH v2 1/2] i2c: designware: Never suspend i2c-busses used for accessing the system PMIC Hans de Goede
2017-03-09 14:24   ` Jarkko Nikula
2017-03-09 14:39     ` Wolfram Sang
2017-03-09 15:02       ` Jarkko Nikula
2017-03-08  8:47 ` [PATCH v2 2/2] i2c: designware: Disable pm for PMIC i2c-bus even if there is no _SEM method Hans de Goede
2017-03-09 15:00   ` Jarkko Nikula
2017-03-09 15:02     ` Jarkko Nikula [this message]
2017-03-10  2:33     ` Lan Tianyu
2017-03-10  7:49       ` Hans de Goede
2017-03-10 11:34         ` Lan, Tianyu
2017-03-10 20:46           ` Hans de Goede

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=fcc97084-c2b0-150c-ad85-3ec42fd192a2@linux.intel.com \
    --to=jarkko.nikula@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=lenb@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=tianyu.lan@intel.com \
    --cc=tiwai@suse.de \
    --cc=wsa@the-dreams.de \
    /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).