From: Tony Lindgren <tony@atomide.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, sre@kernel.org, nekit1000@gmail.com,
mpartap@gmx.net, merlijn@wizzup.org
Subject: Re: Droid 4: very confusing config around OHCI_OMAP3_HCD
Date: Thu, 3 May 2018 12:28:38 -0700 [thread overview]
Message-ID: <20180503192838.GY98604@atomide.com> (raw)
In-Reply-To: <20180503192510.GB32572@amd>
* Pavel Machek <pavel@ucw.cz> [180503 19:27]:
> Hi!
>
> For power management experiments, I tried
>
> CONFIG_USB_OHCI_HCD=y
> CONFIG_USB_OHCI_HCD_OMAP3=m
> CONFIG_USB_OHCI_HCD_PLATFORM=y
>
> and could not find resulting .ko.
>
> Help text says:
>
> CONFIG_USB_OHCI_HCD_OMAP3:
>
> This option is deprecated now and the driver was removed, use
> USB_OHCI_HCD_PLATFORM instead.
>
> Enables support for the on-chip OHCI controller on
> OMAP3 and later chips.
>
> Which may partly explain it. But if the option no longer does
> anything, why keep it? Certainly second part is confusing if option is
> NOP...
Yeah it's ohci-platform now, I think we decided to keep the old one
around to avoid breaking people's .config files for booting rather
than silently fail.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Droid 4: very confusing config around OHCI_OMAP3_HCD
Date: Thu, 3 May 2018 12:28:38 -0700 [thread overview]
Message-ID: <20180503192838.GY98604@atomide.com> (raw)
In-Reply-To: <20180503192510.GB32572@amd>
* Pavel Machek <pavel@ucw.cz> [180503 19:27]:
> Hi!
>
> For power management experiments, I tried
>
> CONFIG_USB_OHCI_HCD=y
> CONFIG_USB_OHCI_HCD_OMAP3=m
> CONFIG_USB_OHCI_HCD_PLATFORM=y
>
> and could not find resulting .ko.
>
> Help text says:
>
> CONFIG_USB_OHCI_HCD_OMAP3:
>
> This option is deprecated now and the driver was removed, use
> USB_OHCI_HCD_PLATFORM instead.
>
> Enables support for the on-chip OHCI controller on
> OMAP3 and later chips.
>
> Which may partly explain it. But if the option no longer does
> anything, why keep it? Certainly second part is confusing if option is
> NOP...
Yeah it's ohci-platform now, I think we decided to keep the old one
around to avoid breaking people's .config files for booting rather
than silently fail.
Regards,
Tony
next prev parent reply other threads:[~2018-05-03 19:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 19:25 Droid 4: very confusing config around OHCI_OMAP3_HCD Pavel Machek
2018-05-03 19:25 ` Pavel Machek
2018-05-03 19:28 ` Tony Lindgren [this message]
2018-05-03 19:28 ` Tony Lindgren
2018-05-03 19:38 ` Pavel Machek
2018-05-03 19:38 ` Pavel Machek
2018-05-03 22:07 ` Tony Lindgren
2018-05-03 22:07 ` Tony Lindgren
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=20180503192838.GY98604@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--cc=pavel@ucw.cz \
--cc=sre@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.