From: Hans de Goede <hdegoede@redhat.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Wolfram Sang <wsa@the-dreams.de>, Len Brown <lenb@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: acpi: Do not create i2c-clients for LNXVIDEO ACPI devices
Date: Tue, 4 Jul 2017 14:47:48 +0200 [thread overview]
Message-ID: <8ca5511a-b56c-d5b9-bf37-61fb7c293c0e@redhat.com> (raw)
In-Reply-To: <20170704124613.14591-1-hdegoede@redhat.com>
Hi all,
I forgot to add "v2" to the subject, but this is a rebased v2,
which should apply cleanly on next.
Regards.
Hans
On 04-07-17 14:46, Hans de Goede wrote:
> ACPI video devices get tagged by the kernel with the custom LNXVIDEO
> HID so that normal pnp-id matching can be used and are handled by the
> acpi-video driver.
>
> Sometimes the ACPI nodes describing these contain a SERIAL_TYPE_I2C ACPI
> resource. Before this commit the presence of this resource would cause the
> i2c-core to create a /sys/bus/i2c/devices/i2c-LNXVIDEO:00 device for this
> with a modalias of: "i2c:LNXVIDEO:00".
>
> There is no i2c driver for this custom HID, the acpi-video driver binds
> directly to the ACPI device /sys/bus/acpi/devices/LNXVIDEO\:00 which has
> a modalias of "acpi:LNXVIDEO:" .
>
> Not only is the creation of an i2c-client for this undesirable, it is
> actually causing problems. This weird pseudo-resource claims an i2c
> speed of 100KHz and typically points to the i2c bus which is used by the
> touchscreen controller. Some touchscreen controllers only work properly at
> 400KHz, at 100KHz they cause errors like these:
>
> i2c_designware 80860F41:03: i2c_dw_handle_tx_abort: lost arbitration
> i2c_designware 80860F41:03: i2c_dw_handle_tx_abort: lost arbitration
> i2c_designware 80860F41:03: i2c_dw_handle_tx_abort: lost arbitration
> i2c_designware 80860F41:03: i2c_dw_handle_tx_abort: lost arbitration
> silead_ts i2c-MSSL1680:00: Registers clear error -11
>
> This commit makes the i2c-core ignore LNXVIDEO compatible ACPI devices
> which has 2 positive results:
>
> 1) The bogus i2c-client for these is no longer created.
> 2) i2c_acpi_lookup_speed now ignores the 100KHz speed from the pseudo
> i2c-resouce and properly returns 400KHz as speed for the touchscreen
> i2c bus, fixing the touchscreen not working on various devies.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
> Changes in v2:
> -Rebase on top of linux-i2c/for-next
> ---
> drivers/i2c/i2c-core-acpi.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/drivers/i2c/i2c-core-acpi.c b/drivers/i2c/i2c-core-acpi.c
> index 052005579ed6..bda281293d28 100644
> --- a/drivers/i2c/i2c-core-acpi.c
> +++ b/drivers/i2c/i2c-core-acpi.c
> @@ -82,11 +82,22 @@ static int i2c_acpi_do_lookup(struct acpi_device *adev,
> struct i2c_board_info *info = lookup->info;
> struct list_head resource_list;
> int ret;
> + static const struct acpi_device_id video_device_ids[] = {
> + { ACPI_VIDEO_HID, 0 },
> + {}
> + };
>
> if (acpi_bus_get_status(adev) || !adev->status.present ||
> acpi_device_enumerated(adev))
> return -EINVAL;
>
> + /*
> + * ACPI video acpi_devices, which are handled by the acpi-video driver
> + * sometimes contain a SERIAL_TYPE_I2C ACPI resource, ignore these.
> + */
> + if (acpi_match_device_ids(adev, video_device_ids) == 0)
> + return -ENODEV;
> +
> memset(info, 0, sizeof(*info));
> lookup->device_handle = acpi_device_handle(adev);
>
>
next prev parent reply other threads:[~2017-07-04 12:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 12:46 [PATCH] i2c: acpi: Do not create i2c-clients for LNXVIDEO ACPI devices Hans de Goede
2017-07-04 12:47 ` Hans de Goede [this message]
2017-07-04 12:49 ` Wolfram Sang
2017-07-04 12:50 ` Hans de Goede
2017-07-04 12:49 ` Andy Shevchenko
2017-07-04 12:51 ` Hans de Goede
-- strict thread matches above, loose matches on Subject: below --
2017-07-01 10:03 Hans de Goede
2017-07-03 11:10 ` Andy Shevchenko
2017-07-03 15:04 ` Hans de Goede
2017-07-03 15:48 ` Andy Shevchenko
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=8ca5511a-b56c-d5b9-bf37-61fb7c293c0e@redhat.com \
--to=hdegoede@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.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).