Linux Power Management development
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google.com>
To: Thierry Reding <treding@nvidia.com>
Cc: Hugh Dickins <hughd@google.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Saravana Kannan <saravanak@google.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: 5.11-rc device reordering breaks ThinkPad rmi4 suspend
Date: Mon, 11 Jan 2021 09:42:42 -0800 (PST)	[thread overview]
Message-ID: <alpine.LSU.2.11.2101110922300.1620@eggly.anvils> (raw)
In-Reply-To: <X/xV7ZV5jzI7RvAe@ulmo>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2068 bytes --]

On Mon, 11 Jan 2021, Thierry Reding wrote:
> On Sun, Jan 10, 2021 at 08:44:13PM -0800, Hugh Dickins wrote:
> > 
> > Synaptics RMI4 SMBus touchpad on ThinkPad X1 Carbon (5th generation)
> > fails to suspend when running 5.11-rc kernels: bisected to 
> > 5b6164d3465f ("driver core: Reorder devices on successful probe"),
> > and reverting that fixes it.  dmesg.xz attached, but go ahead and ask
> > me to switch on a debug option to extract further info if that may help.
...
> 
> I think what might be happening here is that the offending patch causes
> some devices to be reordered in a way different to how they were ordered
> originally and the rmi4 driver currently depends on that implicit order.

Yes, all that you explained makes good sense, thanks.

> I'm not familiar with how exactly rmi4 works, so I'll have to do
> some digging to hopefully pinpoint exactly what's going wrong here.
> 
> In the meantime, it would be useful to know what exactly the I2C
> hierarchy looks like. For example, what's the I2C controller that the
> RMI4 device is hooked up to. According to the above, that's I2C bus 6,
> so you should be able to find out some details about it by inspecting
> the corresponding sysfs nodes:
> 
> 	$ ls -l /sys/class/i2c-adapter/i2c-6/
> 	$ cat /sys/class/i2c-adapter/i2c-6/name
> 	$ ls -l /sys/class/i2c-adapter/i2c-6/device/

That's curious: I don't even have a /sys/class/i2c-adapter directory.

(And I did wonder if you meant to say "smbus" rather than "i2c",
though I don't have any /sys/class/smbus* either: I have no notion
of the relationship between i2c and smbus, but I thought the failing
write_block calls were the ones in rmi_smbus.c rather than rmi_i2c.c.)

I've attached compressed output of "find /sys/bus /sys/class | sort":
/sys/bus looked more relevant than /sys/class, maybe it will help
point in the right direction?

And in case it's relevant, maybe I should mention that this is a
non-modular, all-built-in kernel.

But as I said to Rafael, my touchpad can wait: the wider ordering
discussion is much more important.

Hugh

[-- Attachment #2: Type: APPLICATION/x-xz, Size: 4240 bytes --]

      parent reply	other threads:[~2021-01-11 17:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11  4:44 5.11-rc device reordering breaks ThinkPad rmi4 suspend Hugh Dickins
2021-01-11 12:57 ` Rafael J. Wysocki
2021-01-11 17:20   ` Hugh Dickins
2021-01-11 13:43 ` Thierry Reding
2021-01-11 14:43   ` Rafael J. Wysocki
2021-01-11 14:57   ` Rafael J. Wysocki
2021-01-11 16:12     ` Thierry Reding
2021-01-11 16:57       ` Rafael J. Wysocki
2021-01-11 22:44         ` Saravana Kannan
2021-01-11 23:42           ` Hugh Dickins
2021-01-12  0:14             ` Saravana Kannan
2021-01-12  0:44               ` Hugh Dickins
2021-01-12  2:16                 ` Saravana Kannan
2021-01-12 12:43           ` Rafael J. Wysocki
2021-01-12 17:37           ` Thierry Reding
2021-01-12 17:57         ` Thierry Reding
2021-01-12 20:38           ` Saravana Kannan
2021-01-11 17:42   ` Hugh Dickins [this message]

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=alpine.LSU.2.11.2101110922300.1620@eggly.anvils \
    --to=hughd@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=saravanak@google.com \
    --cc=treding@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox