From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932364AbdBQEXO (ORCPT ); Thu, 16 Feb 2017 23:23:14 -0500 Received: from [202.36.163.20] ([202.36.163.20]:37793 "EHLO gate2.alliedtelesis.co.nz" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S932224AbdBQEXN (ORCPT ); Thu, 16 Feb 2017 23:23:13 -0500 From: Chris Packham To: Arnd Bergmann , "linux-arm-kernel@lists.infradead.org" CC: Andrew Lunn , Jason Cooper , Russell King , "linux-kernel@vger.kernel.org" , Gregory Clement , Sebastian Hesselbarth Subject: Re: [PATCH v3 5/6] ARM: mvebu: Add driver for mv98dx3236-soc-id Thread-Topic: [PATCH v3 5/6] ARM: mvebu: Add driver for mv98dx3236-soc-id Thread-Index: AQHSiDHMiYS4YzaxAUig2dkf/f7Kkw== Date: Fri, 17 Feb 2017 04:22:54 +0000 Message-ID: References: <20170216085041.28337-1-chris.packham@alliedtelesis.co.nz> <20170216085041.28337-6-chris.packham@alliedtelesis.co.nz> <28604982.PnlvXC13kC@wuerfel> Accept-Language: en-NZ, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [2001:df5:b000:22:c4c8:a7e4:fd6a:de28] Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id v1H4NKMR019090 Hi Arnd, On 17/02/17 02:28, Arnd Bergmann wrote: > On Thursday, February 16, 2017 9:50:39 PM CET Chris Packham wrote: >> The DFX server on the 98dx3236 and compatible SoCs has an ID register >> that provides revision information that the PCI based ID register >> doesn't have. Use this if it's available. >> >> Signed-off-by: Chris Packham >> > > How about putting this new code into a separate driver in > drivers/soc/? I don't think you need the early probing we have > here, and not that much is shared otherwise. > Not putting it there means we'll get the pci fall-back behaviour which will result in a incorrect rev value. Having said that no callers of mvebu_get_soc_id() currently care about these specific SoCs so not having the right rev is not an issue at the moment.