linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ladislav Michl <ladis@linux-mips.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
	Tony Lindgren <tony@atomide.com>, Roger Quadros <rogerq@ti.com>,
	Lee Jones <lee.jones@linaro.org>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>
Subject: [1/3] mfd: omap-usb-host: Use regular platform device probe mechanism
Date: Tue, 11 Sep 2018 17:53:19 +0200	[thread overview]
Message-ID: <20180911155319.GA10574@lenoch> (raw)

On Tue, Sep 11, 2018 at 06:06:08PM +0300, Laurent Pinchart wrote:
> The omap-usb-host driver uses platform_driver_probe() in the fs initcall
> level to ensure that the devices get probed before the EHCI and OHCI
> drivers arer probed.
> 
> The EHCI and OHCI devices are created and registered by the omap-usb-host
> driver, and if no driver is present yet to handle them they will
> patiently wait for they turn without any adverse effect. This mechanism
> is thus not needed, remove it.
> 
> This fixes a bug that prevents EHCI and OHCI devices from being probed
> on the Pandaboard since commit 84badc5ec5fc ("ARM: dts: omap4: Move l4
> child devices to probe them with ti-sysc"), as then omap-usb-host
> devices are now registered after the omap-usb-host driver initializes,
> and thus fail to probe due to platform_driver_probe() not finding any
> device.
> 
> Fixes: 84badc5ec5fc ("ARM: dts: omap4: Move l4 child devices to probe them with ti-sysc")
> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
>  drivers/mfd/omap-usb-host.c | 24 ++++--------------------
>  1 file changed, 4 insertions(+), 20 deletions(-)
> 
> diff --git a/drivers/mfd/omap-usb-host.c b/drivers/mfd/omap-usb-host.c
> index e11ab12fbdf2..b731026541f5 100644
> --- a/drivers/mfd/omap-usb-host.c
> +++ b/drivers/mfd/omap-usb-host.c
> @@ -548,6 +548,7 @@ static int usbhs_omap_probe(struct platform_device *pdev)
>  	int				i;
>  	bool				need_logic_fck;
>  
> +	dev_info(&pdev->dev, "%s\n", __func__);

Is it indentional? Seems like debug leftover.

>  	if (dev->of_node) {
>  		/* For DT boot we populate platform data from OF node */
>  		pdata = devm_kzalloc(dev, sizeof(*pdata), GFP_KERNEL);
> @@ -855,31 +856,14 @@ static struct platform_driver usbhs_omap_driver = {
>  		.pm		= &usbhsomap_dev_pm_ops,
>  		.of_match_table = usbhs_omap_dt_ids,
>  	},
> +	.probe		= usbhs_omap_probe,
>  	.remove		= usbhs_omap_remove,
>  };
>  
> +module_platform_driver(usbhs_omap_driver);
> +
>  MODULE_AUTHOR("Keshava Munegowda <keshava_mgowda@ti.com>");
>  MODULE_AUTHOR("Roger Quadros <rogerq@ti.com>");
>  MODULE_ALIAS("platform:" USBHS_DRIVER_NAME);
>  MODULE_LICENSE("GPL v2");
>  MODULE_DESCRIPTION("usb host common core driver for omap EHCI and OHCI");
> -
> -static int __init omap_usbhs_drvinit(void)
> -{
> -	return platform_driver_probe(&usbhs_omap_driver, usbhs_omap_probe);
> -}
> -
> -/*
> - * init before ehci and ohci drivers;
> - * The usbhs core driver should be initialized much before
> - * the omap ehci and ohci probe functions are called.
> - * This usbhs core driver should be initialized after
> - * usb tll driver
> - */
> -fs_initcall_sync(omap_usbhs_drvinit);
> -
> -static void __exit omap_usbhs_drvexit(void)
> -{
> -	platform_driver_unregister(&usbhs_omap_driver);
> -}
> -module_exit(omap_usbhs_drvexit);
> -- 
> Regards,
> 
> Laurent Pinchart

             reply	other threads:[~2018-09-11 15:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11 15:53 Ladislav Michl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-09-11 16:12 [1/3] mfd: omap-usb-host: Use regular platform device probe mechanism Laurent Pinchart
2018-09-11 15:48 Tony Lindgren
2018-09-11 15:06 Laurent Pinchart

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=20180911155319.GA10574@lenoch \
    --to=ladis@linux-mips.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rogerq@ti.com \
    --cc=tomi.valkeinen@ti.com \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).