From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752994AbcGYSWP (ORCPT ); Mon, 25 Jul 2016 14:22:15 -0400 Received: from down.free-electrons.com ([37.187.137.238]:39633 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751036AbcGYSWM (ORCPT ); Mon, 25 Jul 2016 14:22:12 -0400 Date: Mon, 25 Jul 2016 20:22:09 +0200 From: Thomas Petazzoni To: Rob Herring Cc: Grzegorz Jaszczyk , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Mark Rutland , Jason Cooper , Andrew Lunn , Sebastian Hesselbarth , Russell King - ARM Linux , Gregory CLEMENT , Marcin Wojtas , Lior Amsalem Subject: Re: [PATCH 14/18] ARM: mvebu: add support for the Armada 395 SoC family Message-ID: <20160725202209.5fae4d98@free-electrons.com> In-Reply-To: References: <1469105055-25181-1-git-send-email-jaz@semihalf.com> <1469105055-25181-16-git-send-email-jaz@semihalf.com> <20160721221605.GA21883@rob-hp-laptop> <20160725155050.3aee974e@free-electrons.com> Organization: Free Electrons X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Subject: Re: [PATCH 14/18] ARM: mvebu: add support for the Armada 395 SoC family Date: Mon, 25 Jul 2016 20:22:09 +0200 Message-ID: <20160725202209.5fae4d98@free-electrons.com> References: <1469105055-25181-1-git-send-email-jaz@semihalf.com> <1469105055-25181-16-git-send-email-jaz@semihalf.com> <20160721221605.GA21883@rob-hp-laptop> <20160725155050.3aee974e@free-electrons.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Rob Herring Cc: Grzegorz Jaszczyk , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Mark Rutland , Jason Cooper , Andrew Lunn , Sebastian Hesselbarth , Russell King - ARM Linux , Gregory CLEMENT , Marcin Wojtas , Lior Amsalem List-Id: devicetree@vger.kernel.org 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. Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com From mboxrd@z Thu Jan 1 00:00:00 1970 From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni) Date: Mon, 25 Jul 2016 20:22:09 +0200 Subject: [PATCH 14/18] ARM: mvebu: add support for the Armada 395 SoC family In-Reply-To: References: <1469105055-25181-1-git-send-email-jaz@semihalf.com> <1469105055-25181-16-git-send-email-jaz@semihalf.com> <20160721221605.GA21883@rob-hp-laptop> <20160725155050.3aee974e@free-electrons.com> Message-ID: <20160725202209.5fae4d98@free-electrons.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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. Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com