linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/1] arm64: defconfig: Enable USB onboard hub
Date: Thu, 26 Jan 2023 08:22:45 +0800	[thread overview]
Message-ID: <20230126002244.GL20713@T480> (raw)
In-Reply-To: <20230109074008.111756-1-alexander.stein@ew.tq-group.com>

On Mon, Jan 09, 2023 at 08:40:08AM +0100, Alexander Stein wrote:
> USB host support on TQMa8MPxL (commit ca69b6c78d5d6 ("arm64: dts:
> tqma8mpql: add support for 2nd USB (host) interface") needs onboard USB
> hub driver for handling reset GPIO.
> 
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> ---
>  arch/arm64/configs/defconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index f9cab47c585c0..91ce61e4ea578 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -922,6 +922,7 @@ CONFIG_USB_ISP1760=y
>  CONFIG_USB_SERIAL=m
>  CONFIG_USB_SERIAL_CP210X=m
>  CONFIG_USB_SERIAL_FTDI_SIO=m
> +CONFIG_USB_ONBOARD_HUB=y

Does it have to be built-in?

Shawn

>  CONFIG_USB_SERIAL_OPTION=m
>  CONFIG_USB_QCOM_EUD=m
>  CONFIG_USB_HSIC_USB3503=y
> -- 
> 2.34.1
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-01-26  0:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09  7:40 [PATCH 1/1] arm64: defconfig: Enable USB onboard hub Alexander Stein
2023-01-26  0:22 ` Shawn Guo [this message]
2023-01-30  7:54   ` Alexander Stein

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=20230126002244.GL20713@T480 \
    --to=shawnguo@kernel.org \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=will@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).