linux-kernel - Re: [PATCH] ARM: multi_v7_defconfig: Add Atmel SAMA5 family

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <9986808.t62JLgg5NJ@wuerfel>
Date:	Tue, 19 May 2015 13:04:22 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Nicolas Ferre <nicolas.ferre@...el.com>
Cc:	Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
	Olof Johansson <olof@...om.net>,
	Kevin Hilman <khilman@...nel.org>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Boris BREZILLON <boris.brezillon@...e-electrons.com>
Subject: Re: [PATCH] ARM: multi_v7_defconfig: Add Atmel SAMA5 family

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@...e-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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/