From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] usb: renesas: fix extcon dependency
Date: Wed, 18 Feb 2015 22:03:06 +0100 [thread overview]
Message-ID: <5999511.VS28SAB4Q0@wuerfel> (raw)
In-Reply-To: <20150129114158.GY26493@n2100.arm.linux.org.uk>
On Thursday 29 January 2015 11:41:58 Russell King - ARM Linux wrote:
> On Wed, Jan 28, 2015 at 10:47:18PM +0100, Arnd Bergmann wrote:
> > The renesas usbhs driver calls extcon_get_edev_by_phandle(), which
> > is defined in drivers/extcon/extcon-class.c, and that can be a
> > loadable module. If the extcon-class support is disabled, usbhs
> > will work correctly for all devices that do not need extcon.
> >
> > However, if extcon-class is a loadable module, and usbhs is
> > built-in, the kernel fails to link. In order to solve that,
> > we need a Kconfig dependency that allows extcon to be disabled
> > but does not allow usbhs built-in if extcon is a module.
> >
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> >
> > diff --git a/drivers/usb/renesas_usbhs/Kconfig b/drivers/usb/renesas_usbhs/Kconfig
> > index de83b9d0cd5c..0ea9040b9f10 100644
> > --- a/drivers/usb/renesas_usbhs/Kconfig
> > +++ b/drivers/usb/renesas_usbhs/Kconfig
> > @@ -6,6 +6,7 @@ config USB_RENESAS_USBHS
> > tristate 'Renesas USBHS controller'
> > depends on USB_GADGET
> > depends on ARCH_SHMOBILE || SUPERH || COMPILE_TEST
> > + depends on EXTCON || !EXTCON # for module build if extcon is
>
> The comment doesn't make much sense on its own (and when I read it before
> reading the above description, it was down right confusing.) Maybe a
> longer comment would be a good idea?
>
Sorry for the late reply.
We have a lot of these dependencies, and I never know what a particular
maintainer expects. Let me try to come up with something better.
Arnd
prev parent reply other threads:[~2015-02-18 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 21:47 [PATCH] usb: renesas: fix extcon dependency Arnd Bergmann
2015-01-29 11:41 ` Russell King - ARM Linux
2015-02-18 21:03 ` Arnd Bergmann [this message]
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=5999511.VS28SAB4Q0@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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