All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google.com>
To: Saravana Kannan <saravanak@google.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Thierry Reding <treding@nvidia.com>,
	Hugh Dickins <hughd@google.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Vincent Huang <vincent.huang@tw.synaptics.com>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	Andrew Duggan <aduggan@synaptics.com>,
	Lucas Stach <l.stach@pengutronix.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux PM <linux-pm@vger.kernel.org>
Subject: Re: 5.11-rc device reordering breaks ThinkPad rmi4 suspend
Date: Mon, 11 Jan 2021 15:42:27 -0800 (PST)	[thread overview]
Message-ID: <alpine.LSU.2.11.2101111539070.2728@eggly.anvils> (raw)
In-Reply-To: <CAGETcx_odme9ufTps6tctOW+zfOox6iXgTx_9GAjoYn=+jy1BQ@mail.gmail.com>

On Mon, 11 Jan 2021, Saravana Kannan wrote:
> 
> I happen to have an X1 Carbon (different gen though) lying around and
> I poked at its /sys folders. None of the devices in the rmi4_smbus are
> considered the grandchildren of the i2c device. I think the real
> problem is rmi_register_transport_device() [1] not setting up the
> parent for any of the new devices it's adding.
> 
> Hugh, can you try this patch?

Just tried, but no, this patch does not help; but I bet
you're along the right lines, and something as simple will do it.

> 
> diff --git a/drivers/input/rmi4/rmi_bus.c b/drivers/input/rmi4/rmi_bus.c
> index 24f31a5c0e04..50a0134b6901 100644
> --- a/drivers/input/rmi4/rmi_bus.c
> +++ b/drivers/input/rmi4/rmi_bus.c
> @@ -90,6 +90,7 @@ int rmi_register_transport_device(struct
> rmi_transport_dev *xport)
> 
>         rmi_dev->dev.bus = &rmi_bus_type;
>         rmi_dev->dev.type = &rmi_device_type;
> +       rmi_dev->dev.parent = xport->dev;
> 
>         xport->rmi_dev = rmi_dev;
> 
> -Saravana
> 
> [1] - https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/input/rmi4/rmi_bus.c#n74

  reply	other threads:[~2021-01-12  0:44 UTC|newest]

Thread overview: 19+ 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 [this message]
2021-01-12  0:14             ` Saravana Kannan
2021-01-12  0:44               ` Hugh Dickins
2021-01-12  2:16                 ` Saravana Kannan
2021-01-12  4:42                   ` Hugh Dickins
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

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.2101111539070.2728@eggly.anvils \
    --to=hughd@google.com \
    --cc=Jason@zx2c4.com \
    --cc=aduggan@synaptics.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=l.stach@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=saravanak@google.com \
    --cc=treding@nvidia.com \
    --cc=vincent.huang@tw.synaptics.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.