Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1283270
| From | Sergei Shtylyov <sergei.shtylyov@cogentembedded.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCHv2 1/2] extcon: add driver for Intel USB mux |
| Date | 2015-12-03 20:20 +0100 |
| Message-ID | <qBHA5-Ns-3@gated-at.bofh.it> (permalink) |
| References | <qBywN-38I-9@gated-at.bofh.it> <qBywN-38I-7@gated-at.bofh.it> |
| Organization | Cogent Embedded |
On 12/03/2015 12:29 PM, Heikki Krogerus wrote:
> Several Intel PCHs and SOCs have an internal mux that is
> used to share one USB port between USB Device Controller and
> xHCI. The mux is normally handled by System FW/BIOS, but not
> always. For those platforms where the FW does not take care
> of the mux, this driver is needed.
>
> Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
[...]
> diff --git a/drivers/extcon/extcon-intel-usb.c b/drivers/extcon/extcon-intel-usb.c
> new file mode 100644
> index 0000000..3da6039
> --- /dev/null
> +++ b/drivers/extcon/extcon-intel-usb.c
> @@ -0,0 +1,118 @@
[...]
> +struct intel_usb_mux *intel_usb_mux_register(struct device *dev,
> + struct resource *r)
> +{
> + struct intel_usb_mux *mux;
> + int ret;
> +
> + mux = kzalloc(sizeof(*mux), GFP_KERNEL);
> + if (!mux)
> + return ERR_PTR(-ENOMEM);
> +
> + mux->regs = ioremap_nocache(r->start, resource_size(r));
> + if (!mux->regs) {
> + kfree(mux);
> + return ERR_PTR(-ENOMEM);
> + }
> +
> + mux->cfg0_ctx = readl(mux->regs + INTEL_MUX_CFG0);
> +
> + mux->edev.dev.parent = dev;
> + mux->edev.supported_cable = intel_mux_cable;
> +
> + ret = extcon_dev_register(&mux->edev);
I don't see where are you calling extcon_set_cable_state() fot the
"USB-HOST" cable...
This doesn't seem a legitimate extcon driver to me... :-/
> + if (ret)
> + goto err;
> +
> + mux->edev.name = "intel_usb_mux";
> + mux->edev.state = !!(readl(mux->regs + INTEL_MUX_CFG1) & CFG1_MODE);
> +
> + /* An external source needs to tell us what to do */
> + mux->nb.notifier_call = intel_usb_mux_notifier;
> + ret = extcon_register_notifier(&mux->edev, EXTCON_USB_HOST, &mux->nb);
So in reality this is an extcon client, not a provider? BTW, this API
isn't recommended...
MBR, Sergei
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCHv2 0/2] extcon: driver for Intel USB MUX Heikki Krogerus <heikki.krogerus@linux.intel.com> - 2015-12-03 10:40 +0100
[PATCHv2 1/2] extcon: add driver for Intel USB mux Heikki Krogerus <heikki.krogerus@linux.intel.com> - 2015-12-03 10:40 +0100
Re: [PATCHv2 1/2] extcon: add driver for Intel USB mux Chanwoo Choi <cw00.choi@samsung.com> - 2015-12-03 10:50 +0100
Re: [PATCHv2 1/2] extcon: add driver for Intel USB mux Heikki Krogerus <heikki.krogerus@linux.intel.com> - 2015-12-04 10:00 +0100
Re: [PATCHv2 1/2] extcon: add driver for Intel USB mux Chanwoo Choi <cw00.choi@samsung.com> - 2015-12-07 02:30 +0100
Re: [PATCHv2 1/2] extcon: add driver for Intel USB mux Heikki Krogerus <heikki.krogerus@linux.intel.com> - 2015-12-07 14:00 +0100
Re: [PATCHv2 1/2] extcon: add driver for Intel USB mux Chanwoo Choi <cw00.choi@samsung.com> - 2015-12-08 02:20 +0100
Re: [PATCHv2 1/2] extcon: add driver for Intel USB mux Heikki Krogerus <heikki.krogerus@linux.intel.com> - 2015-12-08 13:30 +0100
Re: [PATCHv2 1/2] extcon: add driver for Intel USB mux Sergei Shtylyov <sergei.shtylyov@cogentembedded.com> - 2015-12-03 20:20 +0100
[PATCHv2 2/2] usb: pci-quirks: register USB mux found on Cherrytrail SOC Heikki Krogerus <heikki.krogerus@linux.intel.com> - 2015-12-03 10:40 +0100
Re: [PATCHv2 2/2] usb: pci-quirks: register USB mux found on Cherrytrail SOC Sergei Shtylyov <sergei.shtylyov@cogentembedded.com> - 2015-12-03 20:10 +0100
csiph-web