linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@oracle.com>
To: Vignesh R <vigneshr@ti.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: multi_v7_defconfig: Add configs for peripherals on Keystone2 SoCs
Date: Tue, 5 Dec 2017 08:49:51 -0800	[thread overview]
Message-ID: <fffba75f-6674-f293-d2c5-53eb477c0e76@oracle.com> (raw)
In-Reply-To: <20171205091940.22957-1-vigneshr@ti.com>

On 12/5/2017 1:19 AM, Vignesh R wrote:
> Enable Cadence QSPI present on 66AK2G SoC and Keystone USB PHY driver
> for K2E.
> 
> Signed-off-by: Vignesh R <vigneshr@ti.com>
> ---
>   arch/arm/configs/multi_v7_defconfig | 2 ++
>   1 file changed, 2 insertions(+)
> 
> diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
> index 992a8a5da065..c4f4f6682ea5 100644
> --- a/arch/arm/configs/multi_v7_defconfig
> +++ b/arch/arm/configs/multi_v7_defconfig
> @@ -185,6 +185,7 @@ CONFIG_MTD_NAND_BRCMNAND=y
>   CONFIG_MTD_NAND_VF610_NFC=y
>   CONFIG_MTD_NAND_DAVINCI=y
>   CONFIG_MTD_SPI_NOR=y
> +CONFIG_SPI_CADENCE_QUADSPI=m
>   CONFIG_SPI_FSL_QUADSPI=m
>   CONFIG_MTD_UBI=y
>   CONFIG_BLK_DEV_LOOP=y
> @@ -675,6 +676,7 @@ CONFIG_USB_CHIPIDEA_HOST=y
>   CONFIG_USB_ISP1760=y
>   CONFIG_USB_HSIC_USB3503=y
>   CONFIG_AB8500_USB=y
> +CONFIG_KEYSTONE_USB_PHY=m
>   CONFIG_NOP_USB_XCEIV=m
>   CONFIG_USB_GPIO_VBUS=y
>   CONFIG_USB_ISP1301=y
> 
There are more peripherals/drivers which are enabled
in keystone config.

PWM_TIECAP, CAN_C_CAN, RESET_TI_SYSCON, TI_SCI_PROTOCOL,
TI_MESSAGE_MANAGER, NOP_USB_XCEIV, GPIO_PCA953X etc etc

Could please check the complete config and update the
patch please ?

  reply	other threads:[~2017-12-05 16:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05  9:19 [PATCH] ARM: multi_v7_defconfig: Add configs for peripherals on Keystone2 SoCs Vignesh R
2017-12-05 16:49 ` Santosh Shilimkar [this message]
2017-12-05 17:10   ` Vignesh R
2017-12-05 17:15     ` 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=fffba75f-6674-f293-d2c5-53eb477c0e76@oracle.com \
    --to=santosh.shilimkar@oracle.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vigneshr@ti.com \
    /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).