linux-kernel - Re: [PATCH v2 00/11] ARM: shmobile: MSIOF integration on r8a7790/lager and r8a7791/koelsch

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]

Date:	Thu, 6 Mar 2014 11:25:03 +0900
From:	Magnus Damm <magnus.damm@...il.com>
To:	Simon Horman <horms@...ge.net.au>
Cc:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	SH-Linux <linux-sh@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 00/11] ARM: shmobile: MSIOF integration on
 r8a7790/lager and r8a7791/koelsch

On Thu, Mar 6, 2014 at 10:38 AM, Simon Horman <horms@...ge.net.au> wrote:
> On Wed, Mar 05, 2014 at 05:31:42PM +0900, Magnus Damm wrote:
>> On Tue, Feb 25, 2014 at 7:30 PM, Geert Uytterhoeven
>> <geert@...ux-m68k.org> wrote:
>> >         Hi Simon, Magnus,
>> >
>> > This patch series integrates support for the MSIOF module in the Renesas
>> > R-Car H2 (r8a7790) and M2 (r8a7791) SoCs on the Lager and Koelsch
>> > development boards.
>> >
>> > It was tested on Lager and Koelsch, both legacy and DT, using a dummy
>> > driver for the Renesas r2a11302ft PMIC that reads out the PMIC's version
>> > ID.
>> >
>> >     [01/11] ARM: shmobile: r8a7790: Add MSIOF clocks
>> >     [02/11] ARM: shmobile: r8a7791: Add MSIOF clocks
>> >     [03/11] ARM: shmobile: lager legacy: Add MSIOF support
>> >     [04/11] ARM: shmobile: koelsch legacy: Add MSIOF support
>> >     [05/11] ARM: shmobile: r8a7790/lager dts: Rename label spi to qspi, add
>> >             spi0 alias
>> >     [06/11] ARM: shmobile: r8a7791/koelsch dts: Rename label spi to qspi,
>> >             add spi0 alias
>> >     [07/11] ARM: shmobile: r8a7790 dtsi: Add MSIOF nodes and aliases
>> >     [08/11] ARM: shmobile: r8a7791 dtsi: Add MSIOF nodes and aliases
>> >     [09/11] ARM: shmobile: lager dts: Add MSIOF nodes
>> >     [10/11] ARM: shmobile: koelsch dts: Add MSIOF nodes
>> >     [11/11] ARM: shmobile: koelsch/lager/multi defconfig: Enable MSIOF
>> >
>> > These are (reworked versions of) the remaining patches not taken from v1.
>> > Changelogs are available in the individual patches.
>>
>> Hi Geert,
>>
>> Thanks for your efforts. All these look fine to me.
>>
>> Acked-by: Magnus Damm <damm@...nsource.se>
>>
>> Exactly what to merge upstream depends on what the ARM SoC maintainers prefer.
>
> I wonder if for now we could move things forwards by merging the
> non-legacy code. I think that would mean the following:
>
>     [05/11] ARM: shmobile: r8a7790/lager dts: Rename label spi to qspi, add
>             spi0 alias
>     [06/11] ARM: shmobile: r8a7791/koelsch dts: Rename label spi to qspi,
>             add spi0 alias
>     [07/11] ARM: shmobile: r8a7790 dtsi: Add MSIOF nodes and aliases
>     [08/11] ARM: shmobile: r8a7791 dtsi: Add MSIOF nodes and aliases
>     [09/11] ARM: shmobile: lager dts: Add MSIOF nodes
>     [10/11] ARM: shmobile: koelsch dts: Add MSIOF nodes
>
> And just the 'multi' portion of:
>
>     [11/11] ARM: shmobile: koelsch/lager/multi defconfig: Enable MSIOF
>
>
> Would that result in working MSIOF support for koelsch and lager
> when using multiplatform?

I believe so, but I rely on Geert to point out if this assumption is wrong.

> Then later, if appropriate, in accordance with discussions with the
> ARM SoC maintainers, we could merge the remaining changes in
> this series: the legacy code.

Sure, sounds good.

Thanks,

/ magnus
--
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/