linux-kernel - Re: [PATCH 14/18] ARM: mvebu: add support for the Armada 395 SoC 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] [day] [month] [year] [list]

Message-ID: <CAL_Jsq+Or4=Oa5+OMw5pZh6CBgHktiTL89UcZcw6pJ1VBWB8cg@mail.gmail.com>
Date:	Thu, 28 Jul 2016 10:59:38 -0500
From:	Rob Herring <robh@...nel.org>
To:	Gregory CLEMENT <gregory.clement@...e-electrons.com>
Cc:	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
	Grzegorz Jaszczyk <jaz@...ihalf.com>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Mark Rutland <mark.rutland@....com>,
	Jason Cooper <jason@...edaemon.net>,
	Andrew Lunn <andrew@...n.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
	Russell King - ARM Linux <linux@...linux.org.uk>,
	Marcin Wojtas <mw@...ihalf.com>,
	Lior Amsalem <alior@...vell.com>
Subject: Re: [PATCH 14/18] ARM: mvebu: add support for the Armada 395 SoC family

On Thu, Jul 28, 2016 at 6:19 AM, Gregory CLEMENT
<gregory.clement@...e-electrons.com> wrote:
> Hi Rob,
>
>  On lun., juil. 25 2016, Thomas Petazzoni <thomas.petazzoni@...e-electrons.com> wrote:
>
>> Hello,
>>
>> On Mon, 25 Jul 2016 10:12:43 -0500, Rob Herring wrote:
>>
>>> Yes, I get that, but that is only meaningful if you want to run an OS
>>> that is only aware of 395 on a 398 SoC/board (though I'd guess the 390
>>> compat is enough for that). Otherwise, that property is not really
>>> meaningful as the additional nodes are enough to handle what is the
>>> superset.
>>>
>>> I would agree both are fine if both chips are in fact the same die,
>>> just fused or packaged differently. I've seen a lot of chips that are
>>> supposed to be sub/supersets of each other, but have different errata
>>> lists because they are different die.
>>
>> Unfortunately HW vendors are rarely willing to publicly indicate whether
>> the different chips in their families are actually the same die fused
>> differently, or really different dies.

Then it is safest to assume they are different.

> So do you want that we keep both "marvell,armada398" and
> "marvell,armada395" or do you xant we use only "marvell,armada398" ?

For the 398 based boards, I think it should only have
"marvell,armada398" and don't add "marvell,armada395".

Rob