From: Jun Li <jun.li@nxp.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux@roeck-us.net" <linux@roeck-us.net>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH 3/4] usb: typec: add typec orientation switch support via mux controller
Date: Fri, 21 May 2021 13:02:23 +0000 [thread overview]
Message-ID: <VI1PR04MB5935E0011B57A2AD018A065489299@VI1PR04MB5935.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <YKZXHG7BSSZssiBg@kuha.fi.intel.com>
> -----Original Message-----
> From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> Sent: Thursday, May 20, 2021 8:34 PM
> To: Jun Li <jun.li@nxp.com>
> Cc: robh+dt@kernel.org; shawnguo@kernel.org; gregkh@linuxfoundation.org;
> linux@roeck-us.net; linux-usb@vger.kernel.org; dl-linux-imx
> <linux-imx@nxp.com>; devicetree@vger.kernel.org;
> linux-arm-kernel@lists.infradead.org
> Subject: Re: [PATCH 3/4] usb: typec: add typec orientation switch support
> via mux controller
>
> On Wed, May 19, 2021 at 03:14:49PM +0800, Li Jun wrote:
> > Some dedicated mux block can use existing mux controller as a mux
> > provider, typec port as a consumer to select channel for orientation
> > switch, this can be an alternate way to current typec_switch
> > interface.
> >
> > Signed-off-by: Li Jun <jun.li@nxp.com>
> > ---
> > drivers/usb/typec/class.c | 26 +++++++++++++++++++++++++-
> > drivers/usb/typec/class.h | 2 ++
> > drivers/usb/typec/mux.c | 34 ++++++++++++++++++++++++++++++++++
> > include/linux/usb/typec_mux.h | 4 ++++
> > 4 files changed, 65 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/usb/typec/class.c b/drivers/usb/typec/class.c
> > index a29bf2c32233..1bb0275e6204 100644
> > --- a/drivers/usb/typec/class.c
> > +++ b/drivers/usb/typec/class.c
> > @@ -1601,6 +1601,7 @@ static void typec_release(struct device *dev)
> > ida_simple_remove(&typec_index_ida, port->id);
> > ida_destroy(&port->mode_ids);
> > typec_switch_put(port->sw);
> > + typec_mux_control_switch_put(port->mux_control_switch);
> > typec_mux_put(port->mux);
> > kfree(port->cap);
> > kfree(port);
> > @@ -1816,6 +1817,13 @@ int typec_set_orientation(struct typec_port *port,
> > if (ret)
> > return ret;
> >
> > + if (!port->sw) {
> > + ret = typec_mux_control_switch_set(port->mux_control_switch,
> > + port->mux_control_switch_states[orientation]);
> > + if (ret)
> > + return ret;
> > + }
> > +
> > port->orientation = orientation;
> > sysfs_notify(&port->dev.kobj, NULL, "orientation");
> > kobject_uevent(&port->dev.kobj, KOBJ_CHANGE); @@ -1991,7 +1999,7 @@
> > struct typec_port *typec_register_port(struct device *parent,
> > const struct typec_capability *cap) {
> > struct typec_port *port;
> > - int ret;
> > + int ret = 0;
> > int id;
> >
> > port = kzalloc(sizeof(*port), GFP_KERNEL); @@ -2068,6 +2076,22 @@
> > struct typec_port *typec_register_port(struct device *parent,
> > return ERR_PTR(ret);
> > }
> >
> > + if (!port->sw) {
> > + /* Try to get typec switch via general mux controller */
> > + port->mux_control_switch =
> typec_mux_control_switch_get(&port->dev);
> > + if (IS_ERR(port->mux_control_switch))
> > + ret = PTR_ERR(port->mux_control_switch);
> > + else if (port->mux_control_switch)
> > + ret = device_property_read_u32_array(&port->dev,
> > + "mux-control-switch-states",
> > + port->mux_control_switch_states,
> > + 3);
> > + if (ret) {
> > + put_device(&port->dev);
> > + return ERR_PTR(ret);
> > + }
> > + }
>
> Why not just do that inside fwnode_typec_switch_get() and handle the whole
> thing in drivers/usb/typec/mux.c (or in its own file if you prefer)?
>
> You'll just need to register a "wrapper" Type-C switch object for the OF
> mux controller, but that should not be a problem. That way you don't need
> to export any new functions, touch this file or anything else.
>
Okay, so stick to current typec_switch is preferred, actually I hesitated
on this, I know that approach will have a unified interface, but with
the cost of creating it only for wrap.
My v2 will go with the direction you suggested.
Thanks
Li Jun
>
> thanks,
>
> --
> heikki
next prev parent reply other threads:[~2021-05-21 13:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 7:14 [PATCH 0/4] typec switch via mux controller Li Jun
2021-05-19 7:14 ` [PATCH 1/4] dt-bindings: connector: Add typec orientation switch properties Li Jun
2021-05-21 1:30 ` Rob Herring
2021-05-25 11:48 ` Jun Li
2021-05-19 7:14 ` [PATCH 2/4] usb: typec: use typec cap fwnode's of_node for typec port Li Jun
2021-05-20 12:38 ` Heikki Krogerus
2021-05-19 7:14 ` [PATCH 3/4] usb: typec: add typec orientation switch support via mux controller Li Jun
2021-05-20 12:33 ` Heikki Krogerus
2021-05-21 8:37 ` Heikki Krogerus
2021-05-25 11:46 ` Jun Li
2021-05-26 9:16 ` Heikki Krogerus
2021-05-31 11:58 ` Jun Li
2021-05-21 13:02 ` Jun Li [this message]
2021-05-19 7:14 ` [PATCH 4/4] arm64: dts: imx8mp-evk: enable usb0 with typec connector Li Jun
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=VI1PR04MB5935E0011B57A2AD018A065489299@VI1PR04MB5935.eurprd04.prod.outlook.com \
--to=jun.li@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).