All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akihiko Odaki <akihiko.odaki@gmail.com>
To: Basavaraj Natikar <bnatikar@amd.com>
Cc: Basavaraj Natikar <basavaraj.natikar@amd.com>,
	Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mario Limonciello <mario.limonciello@amd.com>
Subject: Re: [PATCH v2] AMD_SFH: Add a DMI quirk entry for Chromebooks
Date: Fri, 15 Jul 2022 13:45:45 +0900	[thread overview]
Message-ID: <2b73e71c-a927-076d-bf44-6dc4431eb3be@gmail.com> (raw)
In-Reply-To: <87d96692-7dbf-f846-f644-5a81f92efcb9@amd.com>

On 2022/07/15 13:41, Basavaraj Natikar wrote:
> 
> 
> On 7/14/2022 11:07 AM, Akihiko Odaki wrote:
>> Google Chromebooks use Chrome OS Embedded Controller Sensor Hub instead
>> of Sensor Hub Fusion and leaves MP2 uninitialized, which disables all
>> functionalities, even including the registers necessary for feature
>> detections.
>>
>> The behavior was observed with Lenovo ThinkPad C13 Yoga.
>>
>>
> This driver should not get loaded in chrome OS by default.
> Could you please provide details of Chrome OS Version and Kernel version to confirm the behavior.
> 
> Are you enabling manually CONFIG_AMD_SFH_HID config?
> 
> Thanks,
> Basavaraj
> 

I use Fedora 36, not Chrome OS. The config is enabled on Fedora's 
generic kernel. The kernel is built from commit 
78ca55889a549a9a194c6ec666836329b774ab6d from the upstream.

Regards,
Akihiko Odaki

  reply	other threads:[~2022-07-15  4:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14  5:37 [PATCH v2] AMD_SFH: Add a DMI quirk entry for Chromebooks Akihiko Odaki
2022-07-14 11:38 ` Mario Limonciello
2022-07-14 18:44 ` Basavaraj Natikar
2022-07-15  4:41 ` Basavaraj Natikar
2022-07-15  4:45   ` Akihiko Odaki [this message]
2022-08-15 18:36     ` Limonciello, Mario

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=2b73e71c-a927-076d-bf44-6dc4431eb3be@gmail.com \
    --to=akihiko.odaki@gmail.com \
    --cc=basavaraj.natikar@amd.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=bnatikar@amd.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.