From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Nicolai Stange <nicstange@gmail.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
Octavian Purdila <octavian.purdila@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION? v4.8] i2c-core: acpi_i2c_get_info() touches non-existent devices
Date: Tue, 20 Sep 2016 10:55:43 +0300 [thread overview]
Message-ID: <20160920075543.GL1811@lahna.fi.intel.com> (raw)
In-Reply-To: <87fuowf0tf.fsf@gmail.com>
On Mon, Sep 19, 2016 at 03:58:52PM +0200, Nicolai Stange wrote:
> > Can you try if the following patch cures the problem?
>
> Unfortunately not. That patch installs the check after the
> acpi_i2c_get_info() invocation which is part of the backtrace above.
Ah, indeed it needs to happen before we parse resources.
> I moved your check into i2c_get_info(), right in front of the IRQ
> handling and this works.
>
> So,
>
> Tested-by: Nicolai Stange <nicstange@gmail.com>
Thanks.
> for this:
>
> diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
> index 74e5aea..3f2b3cf 100644
> --- a/drivers/i2c/i2c-core.c
> +++ b/drivers/i2c/i2c-core.c
> @@ -141,6 +141,7 @@ static int acpi_i2c_get_info(struct acpi_device *adev,
> struct list_head resource_list;
> struct resource_entry *entry;
> struct acpi_i2c_lookup lookup;
> + struct acpi_device *adapter_adev;
> int ret;
>
> if (acpi_bus_get_status(adev) || !adev->status.present ||
> @@ -163,6 +164,12 @@ static int acpi_i2c_get_info(struct acpi_device *adev,
> if (ret < 0 || !info->addr)
> return -EINVAL;
>
> + /* The adapter must be present */
> + if (acpi_bus_get_device(lookup.adapter_handle, &adapter_adev))
> + return -EINVAL;
> + if (acpi_bus_get_status(adapter_adev) || !adapter_adev->status.present)
> + return -EINVAL;;
> +
> *adapter_handle = lookup.adapter_handle;
>
> /* Then fill IRQ number if any */
>
>
>
> But it is still true that acpi_i2c_register_devices() configures the
> interrupts for all ACPI I2C slaves attached to an available adapter,
> independent of whether their adapter is the one given as an argument or
> not. I can't tell whether this is desired, just a note...
You are right it should not do that. I'll send you an updated patch
shortly, can you try if it works?
next prev parent reply other threads:[~2016-09-20 7:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87a8f4kfhe.fsf@gmail.com>
2016-09-19 8:48 ` [REGRESSION? v4.8] i2c-core: acpi_i2c_get_info() touches non-existent devices Mika Westerberg
2016-09-19 13:03 ` Mika Westerberg
2016-09-19 13:58 ` Nicolai Stange
2016-09-20 7:55 ` Mika Westerberg [this message]
2016-09-20 8:00 ` [PATCH] i2c / ACPI: Do not touch an I2C device if it belongs to another adapter Mika Westerberg
2016-09-20 10:32 ` Nicolai Stange
2016-09-20 10:45 ` Mika Westerberg
2016-09-20 13:59 ` [PATCH v2] " Mika Westerberg
2016-09-20 18:49 ` Nicolai Stange
2016-09-21 5:48 ` Wolfram Sang
2016-09-21 8:45 ` Mika Westerberg
2016-09-21 16:14 ` Wolfram Sang
2016-09-22 8:49 ` Mika Westerberg
2016-09-22 8:59 ` Wolfram Sang
2016-09-22 9:25 ` Mika Westerberg
2016-09-22 17:46 ` Wolfram Sang
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=20160920075543.GL1811@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicstange@gmail.com \
--cc=octavian.purdila@intel.com \
--cc=rafael.j.wysocki@intel.com \
--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).