From: Arnd Bergmann <arnd@arndb.de>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Olof Johansson <olof@lixom.net>,
Kevin Hilman <khilman@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Boris BREZILLON <boris.brezillon@free-electrons.com>
Subject: Re: [PATCH] ARM: multi_v7_defconfig: Add Atmel SAMA5 family
Date: Tue, 19 May 2015 13:04:22 +0200 [thread overview]
Message-ID: <9986808.t62JLgg5NJ@wuerfel> (raw)
In-Reply-To: <555AFF3F.10400@atmel.com>
On Tuesday 19 May 2015 11:15:43 Nicolas Ferre wrote:
> Le 03/04/2015 11:01, Alexandre Belloni a écrit :
> > Add the Atmel sama5d3 and sama5d4 and their peripherals to multi_v7_defconfig.
> >
> > Note that the console will be ttyAT0 instead of the usual ttyS0.
> >
> > Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>
> It seems good to me: thanks Alexandre.
>
> Arnd, Olof, Kevin: do you have a comment about this addition?
We're trying to move to a more modular build of multi_v7_defconfig.
Please make all drivers that are not required for booting '=m',
and ensure that they have a MODULE_DEVICE_TABLE entry that allows
autoloading.
Most of the symbols are already marked =m here, but there are a
few that I'm wondering about:
> If it's okay on your side, I may have to rebase it on top of whichever
> branch you want, just to avoid conflicts:
> - your most recent arm-soc/next/defconfig branch
> - or the v4.1-rc3 tag on which the branch is made from?
-rc3 is fine, we can easily handle the conflicts when merging in your
patch.
> > @@ -250,15 +261,18 @@ CONFIG_SERIAL_FSL_LPUART=y
> > CONFIG_SERIAL_FSL_LPUART_CONSOLE=y
> > CONFIG_SERIAL_ST_ASC=y
> > CONFIG_SERIAL_ST_ASC_CONSOLE=y
> > +CONFIG_HW_RANDOM=y
> > CONFIG_I2C_CHARDEV=y
> > CONFIG_I2C_DAVINCI=y
> > CONFIG_I2C_MUX=y
seems non-essential.
> > @@ -502,6 +522,8 @@ CONFIG_RTC_DRV_MV=y
> > CONFIG_RTC_DRV_TEGRA=y
> > CONFIG_DMADEVICES=y
> > CONFIG_DW_DMAC=y
> > +CONFIG_AT_HDMAC=y
> > +CONFIG_AT_XDMAC=y
> > CONFIG_MV_XOR=y
> > CONFIG_TEGRA20_APB_DMA=y
> > CONFIG_SH_DMAE=y
What are these required for? I assume you need them for MMC? If so, that's
fine.
Arnd
next prev parent reply other threads:[~2015-05-19 11:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 9:01 [PATCH] ARM: multi_v7_defconfig: Add Atmel SAMA5 family Alexandre Belloni
2015-05-19 9:15 ` Nicolas Ferre
2015-05-19 11:04 ` Arnd Bergmann [this message]
2015-05-19 12:33 ` Alexandre Belloni
2015-05-19 13:02 ` Nicolas Ferre
2015-05-19 13:28 ` Nicolas Ferre
2015-05-19 13:53 ` Nicolas Ferre
2015-05-20 13:53 ` Kevin Hilman
2015-05-20 14:08 ` Alexandre Belloni
2015-05-20 14:59 ` Kevin Hilman
2015-05-20 21:29 ` Alexandre Belloni
2015-05-20 15:18 ` Robert Nelson
2015-05-20 21:22 ` Alexandre Belloni
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=9986808.t62JLgg5NJ@wuerfel \
--to=arnd@arndb.de \
--cc=alexandre.belloni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=olof@lixom.net \
/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