From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 31B7BC33CAD for ; Mon, 13 Jan 2020 14:28:26 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 0627E207E0 for ; Mon, 13 Jan 2020 14:28:25 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="W3BCNgcR"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=sirena.org.uk header.i=@sirena.org.uk header.b="J4HQCkmv" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0627E207E0 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-mtd-bounces+linux-mtd=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender:Content-Type:Cc: List-Subscribe:List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id: In-Reply-To:MIME-Version:References:Message-ID:Subject:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=urKFFJiq1y1sQH05D9+wbBHzU6qHZ03LjduQolrK3iM=; b=W3BCNgcRR7S1M3RnOHEvJbPyb zr1UmXjT5FkxRPKgTbLCygkzrr4J956a1iNCMRTIU/P/alFik5vn6Pjte7WZ0Gi5NGKcSGuNWZB6/ hdRHAxf6/3tUkxW+pLszGkeSOE0TKmP01K2T5ihRYIGw4dboBsRrGeZ5fDJ0Dw1OBV9fVyh1aErBY dd/Ez/kztvxp0Y/dsBAY/EkWzajJVy/kQbQjVB1uler8iKrnoSNOaDb3ErCQFqidcGFBAKFHy5LyY cJ81vBBLHlVG9wtZ7P57xhwCPqZi+FjvsGuvD5jgAKlVAL4umYitp6pdulo8PV1WqqDZe+a86FiQ7 y/l6tBe0A==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1ir0hN-0007kC-Nx; Mon, 13 Jan 2020 14:28:09 +0000 Received: from heliosphere.sirena.org.uk ([172.104.155.198]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1ir0hK-0007jK-NG for linux-mtd@lists.infradead.org; Mon, 13 Jan 2020 14:28:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sirena.org.uk; s=20170815-heliosphere; h=In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=gI+gQL3pn7zMuCRzTvhyLR0rFsc7ORADzwCGXynvWCY=; b=J4HQCkmv5+4IoZU8+rmZFPCmr RjSnBLNhkSx+oYkIe0rQIqn+BusQ/aUEwMmsXdwifyEALwkwVaInpZIAE7DAeqRFoxqRc1PmqeVOP V8sKprrraFLtSt0PyG0LDwO6AX2Y1yuJtU29anR8mpuMJWlA3YV0u3dxOlJ6Gc0hWhCwI=; Received: from fw-tnat-cam7.arm.com ([217.140.106.55] helo=fitzroy.sirena.org.uk) by heliosphere.sirena.org.uk with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ir0h8-0002lN-Pj; Mon, 13 Jan 2020 14:27:54 +0000 Received: by fitzroy.sirena.org.uk (Postfix, from userid 1000) id 2ED9CD01965; Mon, 13 Jan 2020 14:27:54 +0000 (GMT) Date: Mon, 13 Jan 2020 14:27:54 +0000 From: Mark Brown To: Andy Shevchenko Subject: Re: [PATCH v2 2/3] spi: Add HiSilicon v3xx SPI NOR flash controller driver Message-ID: <20200113142754.GL3897@sirena.org.uk> References: <20200109212842.GK3702@sirena.org.uk> <20200110140726.GB5889@sirena.org.uk> <6db83881-927c-d11c-9c77-23a45892ddab@huawei.com> <20200110193119.GI32742@smile.fi.intel.com> <612a3c5d-69a4-af6b-5c79-c3fb853193ab@huawei.com> <20200113114256.GH3897@sirena.org.uk> <6dd45da9-9ccf-45f7-ed12-8f1406a0a56b@huawei.com> <20200113140627.GJ3897@sirena.org.uk> MIME-Version: 1.0 In-Reply-To: X-Cookie: Programming is an unnatural act. User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200113_062806_765110_EF5274C9 X-CRM114-Status: GOOD ( 14.24 ) X-BeenThere: linux-mtd@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: liusimin4@huawei.com, chenxiang66@hisilicon.com, John Garry , linux-spi , Linuxarm , Linux Kernel Mailing List , Marek Vasut , "open list:MEMORY TECHNOLOGY..." , tudor.ambarus@microchip.com, Jiancheng Xue , Andy Shevchenko , Mika Westerberg , wanghuiqiang , fengsheng5@huawei.com Content-Type: multipart/mixed; boundary="===============6281823099320252311==" Sender: "linux-mtd" Errors-To: linux-mtd-bounces+linux-mtd=archiver.kernel.org@lists.infradead.org --===============6281823099320252311== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="rnP2AJ7yb1j09OW/" Content-Disposition: inline --rnP2AJ7yb1j09OW/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jan 13, 2020 at 04:17:32PM +0200, Andy Shevchenko wrote: > On Mon, Jan 13, 2020 at 4:07 PM Mark Brown wrote: > > On Mon, Jan 13, 2020 at 01:01:06PM +0000, John Garry wrote: > > > On 13/01/2020 11:42, Mark Brown wrote: > > > > The idiomatic approach appears to be for individual board vendors > > > > to allocate IDs, you do end up with multiple IDs from multiple > > > > vendors for the same thing. > > > But I am not sure how appropriate that same approach would be for some 3rd > > > party memory part which we're simply wiring up on our board. Maybe it is. > > It seems to be quite common for Intel reference designs to assign > > Intel IDs to non-Intel parts on the board (which is where I > > became aware of this practice). > Basically vendor of component in question is responsible for ID, but > it seems they simple don't care. AFAICT a lot of the time it seems to be that whoever is writing the software ends up assigning an ID, that may not be the silicon vendor. --rnP2AJ7yb1j09OW/ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAl4cfmkACgkQJNaLcl1U h9C9SAf/QUGxpHCyO2c4xltDoYDcAjrwD0T5cZM7n1f3yKywuxkpNt6pJtFXI0Vy pHN6G5MnEma6TGY+6gO6mfUwgMeMedj8jy8ZlEhWNWEigXKm09SXXf7cNhz/z27G UFyxXenpV0xU9839bZ7PfRqgFGhQTOaXCbpqGiL+N9dU0V+jzkpMSL30FJFa8acS WSMZlt54a1f462AQepyauxqdCJ5/krBwV2/z1xRJ5z0NwlrqqYWWr77AoZP0chuL mjQWulsjgyUGRN7OIt9S51bHPF82uUg+rYKkNLZGmeAz2jVf1nI73h4T88NTlj9H msiLxupn8vvcpRM9fc5sYSH6Y0Zmcw== =y+l1 -----END PGP SIGNATURE----- --rnP2AJ7yb1j09OW/-- --===============6281823099320252311== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/ --===============6281823099320252311==--