linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Arnd Bergmann <arnd@kernel.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: rework USB Kconfig dependencies
Date: Thu, 22 Apr 2021 09:32:27 -0700	[thread overview]
Message-ID: <74e04402-58b3-b1e5-4f72-9fe227f21b35@infradead.org> (raw)
In-Reply-To: <20210422133647.1877425-1-arnd@kernel.org>

On 4/22/21 6:36 AM, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> 
> A lot of input drivers traditionally depend on CONFIG_USB_ARCH_HAS_HCD
> and select CONFIG_USB. This works but is different from almost every
> other subsystem in the kernel.
> 
> I found this when debugging a build failure in the RC subsystem that
> had the same logic.
> 
> The problem here is that CONFIG_USB_ARCH_HAS_HCD no longer has
> a meaning since the host controller support has been changed to
> use machine specific loadable modules for the USB host. Selecting
> a subsystem that a driver needs is confusing and can lead to
> recursive dependency chains in Kconfig.
> 
> In both cases, the normal logic is to specify 'depends on USB'.
> 
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

Reviewed-by: Randy Dunlap <rdunlap@infradead.org>

Thanks.

> ---
>  drivers/input/joystick/Kconfig    |  6 ++----
>  drivers/input/misc/Kconfig        | 15 +++++----------
>  drivers/input/mouse/Kconfig       |  9 +++------
>  drivers/input/tablet/Kconfig      | 15 +++++----------
>  drivers/input/touchscreen/Kconfig |  3 +--
>  5 files changed, 16 insertions(+), 32 deletions(-)
> 


-- 
~Randy


      reply	other threads:[~2021-04-22 16:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 13:36 [PATCH] Input: rework USB Kconfig dependencies Arnd Bergmann
2021-04-22 16:32 ` Randy Dunlap [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=74e04402-58b3-b1e5-4f72-9fe227f21b35@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.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 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).