Received: by 2002:a25:c205:0:0:0:0:0 with SMTP id s5csp2435858ybf; Mon, 2 Mar 2020 08:34:53 -0800 (PST) X-Google-Smtp-Source: ADFU+vuiplOGbUTN3PBfV//QFZ6HBVrL1rWfliEZJfY3V6NbgINM4J/M49jtUtTbhv3yurCXD2us X-Received: by 2002:a9d:3f4b:: with SMTP id m69mr46255otc.146.1583166892926; Mon, 02 Mar 2020 08:34:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1583166892; cv=none; d=google.com; s=arc-20160816; b=MO/NUPQjQlKbtuFT73oiUwAd9agahWqBTgbsymZpF0+pH7wu/jq7WMXUKtcSbxSLI1 ctQM8Rw2l0ZiIEphaX+xMhadg+PYtR6/Lqo+Zzr36Nddsw6QKkAY6/MCH9GTlZXsIzIj uCleZRFNlVvaIVvEhT7ROnPzpyDegOHHRm09IBf0D/C++qN2uTgaYFVcgqoak6Bkkb7A 6nMasOVNYny2lbTW7i4cf/ygw3HELgieT9tN+6rGtIJwiXWylBWagIiZqdc5sgMpbqCR iK7oIpwJb8D8pGsoLww22Ez1fz2FWWRCR/yQaC9ma7QK8BLo+gTfqOr6QA8ZBFokrEIl ctqA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=MUZAdoRRlsq7OtF/8Q53fyl9CL5XsFtZrYt5viQpT3c=; b=uCMBhe3HADmb5T/P2ofQPS9yMtC7kyFtQ9GttK0m05V+r8K32VD6dCLkrjxWcX9L/n +fNAmav7ij8SioTZ/PImsg9tWjz+oevfxkfoigGKYjcg1Dt497cCzN9RaZ4TCn0tgjqY MCLtjpvJ3Pgah9AN6PSKj7/iRrjPnFX/iN/kKgb6wiFAlhAl5K9ZzBwqWpgKR8oJRj/6 P9Ez5VzYAyk1pBrX3cvV8ZyDMwDEV9oEzk0litRCQrbQxS4oGZLdXaU2YkqwQCBqCHds Gwj5uXU06jFFRmvmtugFYpwh+cByuMoxqzvfbCeEmqRsbxkae9CYBhc2Wq00ttUXd+6r B/lw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a190si3233756oii.21.2020.03.02.08.34.40; Mon, 02 Mar 2020 08:34:52 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727359AbgCBQdU (ORCPT + 99 others); Mon, 2 Mar 2020 11:33:20 -0500 Received: from foss.arm.com ([217.140.110.172]:35120 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726775AbgCBQdT (ORCPT ); Mon, 2 Mar 2020 11:33:19 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 798BFFEC; Mon, 2 Mar 2020 08:33:19 -0800 (PST) Received: from localhost (unknown [10.37.6.21]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id F22793F534; Mon, 2 Mar 2020 08:33:18 -0800 (PST) Date: Mon, 2 Mar 2020 16:33:17 +0000 From: Mark Brown To: Geert Uytterhoeven Cc: John Garry , linux-spi , Linuxarm , Linux Kernel Mailing List , MTD Maling List , Andy Shevchenko Subject: Re: [PATCH RFC 1/3] spi: Allow SPI controller override device buswidth Message-ID: <20200302163317.GH4166@sirena.org.uk> References: <1582903131-160033-1-git-send-email-john.garry@huawei.com> <1582903131-160033-2-git-send-email-john.garry@huawei.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="tT3UgwmDxwvOMqfu" Content-Disposition: inline In-Reply-To: X-Cookie: Whistler's mother is off her rocker. User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --tT3UgwmDxwvOMqfu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Mar 02, 2020 at 05:12:05PM +0100, Geert Uytterhoeven wrote: > On Fri, Feb 28, 2020 at 4:23 PM John Garry wrote: > > A host controller driver might know this info from DMI tables, for example. > Can't acpi_register_spi_device() obtain that info from DMI tables, > to avoid contaminating the generic code? The DMI tables are going to boil down to per board quirks which we *could* put in the core but you end up with a lot of them and chances are that at some point we'll end up with device specific quirks which don't fit so well in the core. Handling stuff in the drivers is fairly idiomatic. Much ACPI, so standards :/ --tT3UgwmDxwvOMqfu Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAl5dNUwACgkQJNaLcl1U h9AexAf/aeE9iGeVv7pH09/MjY36txVc4+qNNLl4dd0LN6yt222WVl1jNMjvWnTl LrJ94pJcXCAPNZMpzkOMFJHdSK2n9PCuoA9KprkrZ2UUUpQe96q+Ll2qGnO3R7Wo qcL0FtJEGfuo9znEMdKSAxp2Buc6RW3AgPYp/9N7s+JT17mm9dL50BrujpvgaE6C LTSQ7KZ+rJFDBejSFD8T81zT80tVWXqyzWH9xdDFc9RkvBlX2iFqkUHXDP73Z1ik v/6mYFfXLjz0ekOn4/YKkTip2/EQ/EA4SrPYF80UOIzFFGYECBSdGXU3ZEHvkQBV jodU2vNG5FKyZOVlc4YxD5faKm8peA== =zK3/ -----END PGP SIGNATURE----- --tT3UgwmDxwvOMqfu--