linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Felipe Balbi <balbi@ti.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	David Cohen <david.a.cohen@linux.intel.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Baolu Lu <baolu.lu@linux.intel.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 01/12] usb: add bus type for USB ULPI
Date: Thu, 19 Mar 2015 00:26:35 +0100	[thread overview]
Message-ID: <1426721195.2375.10.camel@x220> (raw)
In-Reply-To: <1426682433-133813-2-git-send-email-heikki.krogerus@linux.intel.com>

On Wed, 2015-03-18 at 14:40 +0200, Heikki Krogerus wrote:
> --- a/drivers/usb/common/Makefile
> +++ b/drivers/usb/common/Makefile
> @@ -7,3 +7,4 @@ usb-common-y			  += common.o
>  usb-common-$(CONFIG_USB_LED_TRIG) += led.o
>  
>  obj-$(CONFIG_USB_OTG_FSM) += usb-otg-fsm.o
> +obj-$(CONFIG_USB_ULPI_BUS)	+= ulpi.o

USB_ULPI_BUS is added as a bool symbol (see below). So ulpi.o will never
be part of a module.

> --- /dev/null
> +++ b/drivers/usb/common/ulpi.c

> +#include <linux/module.h>

So is this include needed?

> +static int __init ulpi_init(void)
> +{
> +	return bus_register(&ulpi_bus);
> +}
> +module_init(ulpi_init);

This will be equivalent to
    __initcall(ulpi_init)

according to include/linux/init.h.

> +static void __exit ulpi_exit(void)
> +{
> +	bus_unregister(&ulpi_bus);
> +}
> +module_exit(ulpi_exit);

This will never be called.

> +MODULE_AUTHOR("Intel Corporation");
> +MODULE_LICENSE("GPL v2");
> +MODULE_DESCRIPTION("USB ULPI PHY bus");

And these three macros will be, effectively, preprocessed away.

> --- a/drivers/usb/core/Kconfig
> +++ b/drivers/usb/core/Kconfig
 
> +config USB_ULPI_BUS
> +	bool "USB ULPI PHY interface support"
> +	depends on USB || USB_GADGET
> +	help
> +	  Say yes if you have ULPI PHY attached to your USB controller.
> +
> +	  If unsure, say N.
> +


Paul Bolle


  reply	other threads:[~2015-03-18 23:26 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18 12:40 [PATCHv2 00/12] usb: ulpi bus Heikki Krogerus
2015-03-18 12:40 ` [PATCHv2 01/12] usb: add bus type for USB ULPI Heikki Krogerus
2015-03-18 23:26   ` Paul Bolle [this message]
2015-03-19 11:44     ` Heikki Krogerus
2015-03-20 12:20       ` [PATCHv3 " Heikki Krogerus
2015-03-26 14:02         ` [PATCHv4 " Heikki Krogerus
2015-03-23  7:16   ` [PATCHv2 " Lu, Baolu
2015-03-23 10:57     ` Heikki Krogerus
2015-03-18 12:40 ` [PATCHv2 02/12] usb: dwc3: USB2 PHY register access bits Heikki Krogerus
2015-03-18 12:40 ` [PATCHv2 03/12] usb: dwc3: ULPI or UTMI+ select Heikki Krogerus
2015-03-18 12:40 ` [PATCHv2 04/12] usb: dwc3: store driver data earlier Heikki Krogerus
2015-03-18 12:40 ` [PATCHv2 05/12] usb: dwc3: cache hwparams earlier Heikki Krogerus
2015-03-18 12:40 ` [PATCHv2 06/12] usb: dwc3: soft reset to it's own function Heikki Krogerus
2015-03-18 12:40 ` [PATCHv2 07/12] usb: dwc3: setup phys earlier Heikki Krogerus
2015-03-18 12:40 ` [PATCHv2 08/12] usb: dwc3: add hsphy_interface property Heikki Krogerus
2015-03-18 12:40 ` [PATCHv2 09/12] usb: dwc3: pci: add quirk for Baytrails Heikki Krogerus
2015-03-18 17:08   ` David Cohen
2015-03-19 11:51     ` Heikki Krogerus
2015-03-20 12:20       ` [PATCHv3 " Heikki Krogerus
2015-03-18 12:40 ` [PATCHv2 10/12] usb: dwc3: add ULPI interface support Heikki Krogerus
2015-03-18 22:53   ` Paul Bolle
2015-03-19 11:48     ` Heikki Krogerus
2015-03-20 12:20       ` [PATCHv3 " Heikki Krogerus
2015-03-18 12:40 ` [PATCHv2 11/12] phy: helpers for USB ULPI PHY registering Heikki Krogerus
2015-03-18 14:46   ` Sergei Shtylyov
2015-03-18 16:54     ` David Cohen
2015-03-18 18:02       ` Sergei Shtylyov
2015-03-18 12:40 ` [PATCHv2 12/12] phy: add driver for TI TUSB1210 ULPI PHY Heikki Krogerus
2015-03-18 17:12 ` [PATCHv2 00/12] usb: ulpi bus David Cohen
2015-03-18 17:19   ` David Cohen

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=1426721195.2375.10.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=balbi@ti.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=david.a.cohen@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sboyd@codeaurora.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 NNTP newsgroup(s).