Hi,
> >>>> + real_role = cdsn3_real_role_switch_get(cdns->dev);
> >>>> +
> >>>> + current_role = role;
> >>>> + dev_dbg(cdns->dev, "Switching role");
> >>>> +
> >>>> + ret = cdns3_role_start(cdns, real_role);
> >>>> + if (ret) {
> >>>> + /* Back to current role */
> >>>> + dev_err(cdns->dev, "set %d has failed, back to %d\n",
> >>>> + role, current_role);
> >>>> + ret = cdns3_role_start(cdns, current_role);
> >>>> + if (ret)
> >>>> + dev_err(cdns->dev, "back to %d failed too\n",
> >>>> + current_role);
> >>>> + }
> >>>> +exit:
> >>>> + pm_runtime_put_sync(cdns->dev);
> >>>> + return ret;
> >>>> +}
> >>>> +
> >>>> +static const struct usb_role_switch_desc cdns3_switch_desc = {
> >>>> + .set = cdns3_role_switch_set,
> >>>> + .get = cdsn3_real_role_switch_get,
> >>>> + .allow_userspace_control = true,
> >>>
> >>> how does user initiated cdns3_role_switch_set() via sysfs co-exist with role
> >>> changes done by hardware events. e.g. ID/VBUS?
> >>>
> >>
> >> Do you expect any issues whit this, have you seen any problem with this
> >> on your platform ?
> >>
> >> I assume that it should work in this way:
> >> 1. user change role by sysfs
> >> 2. Driver change the role according with user request.
> >> 3. If we receive correct ID/VBUS then role should not be changed
> >> because new role is the same as current set in point 2.
> >>
> >
> >I have not tested this series yet.
> >My understanding is that if user sets role to "host" or "device" then it should
> >remain in that role irrespective of ID/VBUS. Once user sets it to "none" then
> >port should set role based on ID/VBUS.
>
> According with your understanding it works the same way as by debugfs.
> Now I have no doubts to remove debugfs.c file :)
Hold on! The role "none" means that the connector should not be
connected to either the host nor device.
The sysfs file we expose from the class for the role switches is
primarily meant for supporting proprietary protocols that require us
to basically override the connector USB data role. The default role
should always be selected in the drivers.
With USB Type-C connectors and alternate modes, the "none" role is
used for example when the connector is put into "USB Safe State". In
case you guys are not familiar with USB Safe State, then it is a state
(defined in USB PD specifications) for the connector where the data
lines on the connector should not be physically connected to anything.
The connector needs to be put into safe state always when entering
or exiting an alternate mode, before the final mode (USB or alternate)
is actually being set for the connector.
thanks,
--
heikki
