From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758950AbcG1QAF (ORCPT ); Thu, 28 Jul 2016 12:00:05 -0400 Received: from mail.kernel.org ([198.145.29.136]:41828 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757245AbcG1QAB (ORCPT ); Thu, 28 Jul 2016 12:00:01 -0400 MIME-Version: 1.0 In-Reply-To: <87y44mj9h8.fsf@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> <20160725202209.5fae4d98@free-electrons.com> <87y44mj9h8.fsf@free-electrons.com> From: Rob Herring Date: Thu, 28 Jul 2016 10:59:38 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 14/18] ARM: mvebu: add support for the Armada 395 SoC family To: Gregory CLEMENT Cc: Thomas Petazzoni , 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 , Marcin Wojtas , Lior Amsalem Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 28, 2016 at 6:19 AM, Gregory CLEMENT wrote: > Hi Rob, > > On lun., juil. 25 2016, Thomas Petazzoni 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Herring Subject: Re: [PATCH 14/18] ARM: mvebu: add support for the Armada 395 SoC family Date: Thu, 28 Jul 2016 10:59:38 -0500 Message-ID: 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> <20160725202209.5fae4d98@free-electrons.com> <87y44mj9h8.fsf@free-electrons.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <87y44mj9h8.fsf@free-electrons.com> Sender: linux-kernel-owner@vger.kernel.org To: Gregory CLEMENT Cc: Thomas Petazzoni , 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 , Marcin Wojtas , Lior Amsalem List-Id: devicetree@vger.kernel.org On Thu, Jul 28, 2016 at 6:19 AM, Gregory CLEMENT wrote: > Hi Rob, > > On lun., juil. 25 2016, Thomas Petazzoni 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: robh@kernel.org (Rob Herring) Date: Thu, 28 Jul 2016 10:59:38 -0500 Subject: [PATCH 14/18] ARM: mvebu: add support for the Armada 395 SoC family In-Reply-To: <87y44mj9h8.fsf@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> <20160725202209.5fae4d98@free-electrons.com> <87y44mj9h8.fsf@free-electrons.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, Jul 28, 2016 at 6:19 AM, Gregory CLEMENT wrote: > Hi Rob, > > On lun., juil. 25 2016, Thomas Petazzoni 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