From: Hans de Goede <hdegoede@redhat.com>
To: Peter Rosin <peda@axentia.se>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: "Krogerus, Heikki" <heikki.krogerus@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sathyanarayanan Kuppuswamy Natarajan <sathyaosid@gmail.com>
Subject: Re: [PATCH v1 1/1] mux: mux-intel-usb: Add Intel USB Multiplexer driver
Date: Wed, 31 May 2017 16:18:10 +0200 [thread overview]
Message-ID: <1c57c881-3885-dca5-b202-07f71a7dc936@redhat.com> (raw)
In-Reply-To: <2ca23e5a-af13-f6f5-7c94-0af36acff6a3@axentia.se>
Hi,
On 31-05-17 15:05, Peter Rosin wrote:
> On 2017-05-31 14:21, Hans de Goede wrote:
>> actually this is the first time I hear about a mux framework
>> at all. Is there a git tree with the patches for this somewhere ?
>
> https://gitlab.com/peda-linux/mux.git in the "mux" branch.
>
> Series posted here:
> https://lkml.org/lkml/2017/5/14/160
Thank you.
I see that mux_control_get() currently relies on devicetree describing
the mux, that is not going to work on non devicetree platforms like
x86 where the relation typically is not described ad all (*) ?
Typically there would be a global list of mux_controls maintained
by mux_[de]register and then mux_control_get() would walk this list
until it finds a matching name. The names to register would then be
passed in by platform data/code when registering and likewise the
consumer would be passed a unique name to pass into mux_control_get()
through platform data / code, would that work for you ?
Note one option would be to set the names to use when registering
a mux chip through device_properties, this is what the power-supply
subsys is currently doing more or less.
Regards,
Hans
*) Work is under way to allow describing topologies in ACPI but it is
not in the standard yet, and we also need to deal with already existing
devices.
>
> Cheers,
> peda
>
next prev parent reply other threads:[~2017-05-31 14:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 0:47 sathyanarayanan.kuppuswamy
2017-05-30 13:40 ` Peter Rosin
2017-05-30 17:47 ` sathyanarayanan kuppuswamy
2017-05-31 6:29 ` Peter Rosin
2017-05-31 23:33 ` sathyanarayanan kuppuswamy
2017-05-30 16:20 ` Andy Shevchenko
2017-05-30 18:21 ` sathyanarayanan kuppuswamy
2017-05-30 18:50 ` Andy Shevchenko
2017-05-31 12:21 ` Hans de Goede
2017-05-31 13:05 ` Peter Rosin
2017-05-31 14:18 ` Hans de Goede [this message]
2017-05-31 15:30 ` Peter Rosin
2017-05-31 18:27 ` Hans de Goede
2017-05-31 23:29 ` sathyanarayanan kuppuswamy
2017-05-31 23:21 ` sathyanarayanan kuppuswamy
2017-05-31 23:12 ` sathyanarayanan kuppuswamy
2017-06-01 14:54 ` Hans de Goede
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=1c57c881-3885-dca5-b202-07f71a7dc936@redhat.com \
--to=hdegoede@redhat.com \
--cc=andy.shevchenko@gmail.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=sathyaosid@gmail.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
all inboxes | Powered by JetHome®