From: Arek Burdach <arek.burdach@gmail.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>, lorenzo.pieralisi@arm.com
Cc: Benjamin Tissoires <benjamin.tissoires@gmail.com>,
srinivas.pandruvada@intel.com, linux-i2c@vger.kernel.org,
ard.biesheuvel@linaro.org, wsa@the-dreams.de
Subject: Re: Accelometer data not changes
Date: Mon, 22 May 2017 09:34:07 +0200 [thread overview]
Message-ID: <57c772a7-8e59-c2a7-2c9e-91674f51bf35@gmail.com> (raw)
In-Reply-To: <18bd3103-c560-9a87-4df7-b1786ce91f8c@linux.intel.com>
Hi
On 22.05.2017 08:47, Jarkko Nikula wrote:
> Hi
>
> On 05/21/2017 07:06 PM, Arek Burdach wrote:
>> Hi Lorenzo,
>>
>> I wanted to check if your newest fix
>> 9d6408433019bfae15e2d0d5f4498c4ff70b86c0 resolved my problem but it
>> looks like it breaks i2c devices on yoga 910 at all.
>>
>> One thing that I see in dmesg is:
>> [ 5.443582] i2c_designware i2c_designware.1: controller timed out
>> [ 5.443601] i2c_hid i2c-SYNA2B31:00: hid_descr_cmd failed
>> [ 6.595650] i2c_designware i2c_designware.2: controller timed out
>> [ 6.595673] i2c_hid i2c-ITE8186:00: hid_descr_cmd failed
>>
>> More details you can see in mentioned isssue.
>> BTW maybe you have an idea what is the root of my problem. I've attached
>> i2c_hid logs for previous version.
>>
> Commit 9d6408433019 ("i2c: designware: don't infer timings described
> by ACPI from clock rate") had issue with uninitialized variables that
> show up when ACPI platform doesn't provide timing parameters for the
> I2C but fortunately that was caught quickly.
>
> Could you try does a patch from Jan Kiszka fix the issue you are seeing?
>
> https://lkml.org/lkml/2017/5/22/24
I've tried and it looks like it removed this regression but still all of
this changes didn't helped for my problem with missing changes from
accelometer.
Maybe you can take a look at isc_hid log after all of those changes:
https://bugzilla.kernel.org/attachment.cgi?id=256651 and tell me if you
see something worrying?
BTW sorry for invalid mailing list - changed
Cheers,
Arek
parent reply other threads:[~2017-05-22 7:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <18bd3103-c560-9a87-4df7-b1786ce91f8c@linux.intel.com>]
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=57c772a7-8e59-c2a7-2c9e-91674f51bf35@gmail.com \
--to=arek.burdach@gmail.com \
--cc=ard.biesheuvel@linaro.org \
--cc=benjamin.tissoires@gmail.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=srinivas.pandruvada@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).