Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: santosh.shilimkar@oracle.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: keystone: defconfig: Fix USB configuration
Date: Wed, 17 Aug 2016 09:23:51 -0700	[thread overview]
Message-ID: <ef561ff0-bf6d-5515-7d10-7c03aa69dd4c@oracle.com> (raw)
In-Reply-To: <1471430690-17143-2-git-send-email-rogerq@ti.com>

Hi Arnd, Olof,

Can you please pick-up the fix for 4.8-rcx ?
Roger reported that USB ports are broken on Keystone2 boards
since v4.8-rc1 because USB_HPY config option got dropped.


On 8/17/2016 3:44 AM, Roger Quadros wrote:
> Simply enabling CONFIG_KEYSTONE_USB_PHY doesn't work anymore
> as it depends on CONFIG_NOP_USB_XCEIV. We need to enable
> that as well.
>
> This fixes USB on Keystone boards from v4.8-rc1 onwards.
>
> Signed-off-by: Roger Quadros <rogerq@ti.com>
> ---
Acked-by: Santosh Shilimkar <ssantosh@kernel.org>


>  arch/arm/configs/keystone_defconfig | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/configs/keystone_defconfig b/arch/arm/configs/keystone_defconfig
> index 71b42e6..78cd2f1 100644
> --- a/arch/arm/configs/keystone_defconfig
> +++ b/arch/arm/configs/keystone_defconfig
> @@ -161,6 +161,7 @@ CONFIG_USB_MON=y
>  CONFIG_USB_XHCI_HCD=y
>  CONFIG_USB_STORAGE=y
>  CONFIG_USB_DWC3=y
> +CONFIG_NOP_USB_XCEIV=y
>  CONFIG_KEYSTONE_USB_PHY=y
>  CONFIG_NEW_LEDS=y
>  CONFIG_LEDS_CLASS=y
>

  reply	other threads:[~2016-08-17 16:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17 10:44 [PATCH 0/1] ARM: Keystone: Fix USB on v4.8-rc Roger Quadros
2016-08-17 10:44 ` [PATCH 1/1] ARM: keystone: defconfig: Fix USB configuration Roger Quadros
2016-08-17 16:23   ` Santosh Shilimkar [this message]
2016-08-25 16:39     ` Santosh Shilimkar
2016-09-12 11:33       ` Roger Quadros
2016-09-15  9:47         ` Arnd Bergmann
2016-08-17 16:24 ` [PATCH 0/1] ARM: Keystone: Fix USB on v4.8-rc Santosh Shilimkar

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=ef561ff0-bf6d-5515-7d10-7c03aa69dd4c@oracle.com \
    --to=santosh.shilimkar@oracle.com \
    --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