From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-i2c@vger.kernel.org
Cc: Peter Rosin <peda@axentia.se>,
linux-renesas-soc@vger.kernel.org,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: [PATCH v2 0/2] i2c: mux: demux-pinctrl: improve device relationships
Date: Mon, 21 May 2018 09:29:37 +0200 [thread overview]
Message-ID: <20180521072939.2836-1-wsa+renesas@sang-engineering.com> (raw)
While researching some PM behaviour within I2C, I found out that the i2c-demux
driver does not play well with that due to broken relationship with other
devices. Patch 1 ensures the right parent-child relationship. Patch 2 makes the
connection between the demux device and the demuxed bus similar to that we have
in the mux core.
Tested on a Renesas Lager board (R-Car H2).
Changes since v1:
* added error check in patch 2
Wolfram Sang (2):
i2c: mux: demux-pinctrl: use proper parent device for demux adapter
i2c: mux: demux-pinctrl: add symlinks to the demux device in sysfs
drivers/i2c/muxes/i2c-demux-pinctrl.c | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
--
2.11.0
next reply other threads:[~2018-05-21 7:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 7:29 Wolfram Sang [this message]
2018-05-21 7:29 ` [PATCH v2 1/2] i2c: mux: demux-pinctrl: use proper parent device for demux adapter Wolfram Sang
2018-05-23 8:48 ` Simon Horman
2018-05-24 11:54 ` Peter Rosin
2018-05-21 7:29 ` [PATCH v2 2/2] i2c: mux: demux-pinctrl: add symlinks to the demux device in sysfs Wolfram Sang
2018-05-22 7:13 ` Peter Rosin
2018-05-22 19:13 ` Wolfram Sang
2018-05-24 11:55 ` Peter Rosin
2018-05-23 8:48 ` Simon Horman
2018-05-23 8:54 ` Wolfram Sang
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=20180521072939.2836-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=peda@axentia.se \
/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).