linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Huan Wang <alison.wang@freescale.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: "shawnguo@kernel.org" <shawnguo@kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jin Jason <Jason.Jin@freescale.com>
Subject: RE: [PATCH v4] ARM: configs: Add Freescale LS1021A defconfig
Date: Fri, 18 Sep 2015 07:38:13 +0000	[thread overview]
Message-ID: <BN3PR0301MB08674C65714A9423E39E1F10FE590@BN3PR0301MB0867.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20150917103414.GN21084@n2100.arm.linux.org.uk>

> On Thu, Sep 17, 2015 at 05:03:34PM +0800, Alison Wang wrote:
> > Add Freescale LS1021A initial defconfig file.
> > The LS1021A SoC is a dual-core Cortex-A7 based processor.
> >
> > LS1021A has some special configurations against imx_v6_v7_defconfig
> > and multi_v7_defconfig, such as CONFIG_ARM_LPAE, CONFIG_ARM_PSCI...
> > LPAE needs to be supported to access memory beyond the 4GB limit for
> > LS1021A. PSCI needs to be supported for LS1021A too. But
> > CONFIG_ARM_LPAE and CONFIG_ARM_PSCI are disabled in
> > imx_v6_v7_defconfig and multi_v7_defconfig, so a separate LS1021A
> defconfig is needed.
> 
> Sounds like a need for multi_v7_lpae_defconfig rather than creating a
> new load of platform specific defconfigs.
> 
[Alison Wang] Thanks for your reply. I agreed with you about creating
a new multi_v7_lpae_defconfig. In multi_v7_lpae_defconfig, I need to add
the following CONFIG_XX to support LS1021A based on multi_v7_defconfig.

CONFIG_ARM_LPAE=y
CONFIG_VMSPLIT_2G=y
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=256000
CONFIG_GIANFAR=y
CONFIG_REALTEK_PHY=y
CONFIG_I2C_IMX=y
CONFIG_SPI_FSL_DSPI=y
CONFIG_IMX2_WDT=y
CONFIG_REGULATOR_DEBUG=y
CONFIG_REGULATOR_VIRTUAL_CONSUMER=y
CONFIG_SOUND=y
CONFIG_SND=y
CONFIG_SND_SOC=y
CONFIG_SND_SOC_FSL_SAI=y
CONFIG_SND_SOC_SGTL5000=y
CONFIG_SND_SIMPLE_CARD=y
CONFIG_FSL_EDMA=y
CONFIG_CLK_QORIQ=y

What's your suggestion? If it's ok, I will send a patch about multi_v7_lpae_defconfig.


Best Regards,
Alison Wang

  reply	other threads:[~2015-09-18  7:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17  9:03 [PATCH v4] ARM: configs: Add Freescale LS1021A defconfig Alison Wang
2015-09-17 10:34 ` Russell King - ARM Linux
2015-09-18  7:38   ` Huan Wang [this message]
2015-09-18 15:45     ` Fabio Estevam
2015-09-24  7:27       ` Huan Wang
2015-09-24  7:34         ` Arnd Bergmann
2015-10-14 10:18           ` Huan Wang
2015-10-14 12:54             ` Arnd Bergmann
2015-10-15  2:11               ` Huan Wang
2015-10-15 12:12                 ` Arnd Bergmann
2015-10-27 14:40                   ` Huan Wang
2015-10-30 13:46                     ` Arnd Bergmann
2015-11-02  3:19                       ` Huan Wang

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=BN3PR0301MB08674C65714A9423E39E1F10FE590@BN3PR0301MB0867.namprd03.prod.outlook.com \
    --to=alison.wang@freescale.com \
    --cc=Jason.Jin@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=shawnguo@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).