Received: by 2002:a25:c205:0:0:0:0:0 with SMTP id s5csp2549462ybf; Mon, 2 Mar 2020 10:52:01 -0800 (PST) X-Google-Smtp-Source: ADFU+vui0lti6q+L6MO4wg9UT+0AdDoVbV4eXzLlia9fuU6Jwt7ZU1E0xRIF9ZFTTVpncqCHhL9y X-Received: by 2002:aca:be57:: with SMTP id o84mr368658oif.138.1583175121469; Mon, 02 Mar 2020 10:52:01 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1583175121; cv=none; d=google.com; s=arc-20160816; b=GCCdAs32iZL+dZyWBk0SVjz9/QyaqbuEKlmxoAz9SoIXipFRUPJXCJY9hz3Fj4QhgL Cz+FFgRgURdakSZcFj/xt1LtWSlR0DybkGmLcaisRTmmI6q59hRjcfJg9v+vOjGmvNnf cgHCH2gzJzMbBqLow20d6qp0VSn5/IJOOBHt49ue6Z5zeZceaSWMeklRMRVdw5UwEsjh Ad8xV9XskaDJ4PPSb2mcBbAhMHrzUA5UEBt0+zoXZIUtrK++R7iXAU8k2tyBiNVVn8IT v1gZNMDe7TrDkGwJsOWmdCjk1WMqk9jphYWZjBGIqMgqPxAm/nzRTrn78K7704zNEG5U x9sA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version; bh=cH1nDM4uwumr6KdthICcbpNTedeJBeY/wKjOC4m8TLQ=; b=dEA6cdnqMapGJNuhv2gSbS7+7thCo+taCGRqKB70l6hLM/qbzl3fZGcJqNxl8IZrqa efUFV+0BVfvZgyI0glX9KXIZCGDIobL8PsXQRx3e6oI4cBcLwEGFaMoTmKHoQsEpPx+Z u4f+tqq5vze9ch4b0f/QluNS54shWThFLX2Og5hvJEBiGG4pl1kjGGw1JE+THxKR0WoQ UJq7OxEhaLx4Y3B6RuiOmpG5thlLJADzX1LBTq60QiXvJ7T/DSq0h/uB8HtlflC1qiM/ TUc/WXv1NQyO87hUTq/WU0S6lfTFbL2HKj+/NSwbRshyBei8zs0MwYJMQJJcqg00dsd8 uQFA== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y186si6610571oig.241.2020.03.02.10.51.48; Mon, 02 Mar 2020 10:52:01 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727408AbgCBSvo (ORCPT + 99 others); Mon, 2 Mar 2020 13:51:44 -0500 Received: from mail-ot1-f68.google.com ([209.85.210.68]:42374 "EHLO mail-ot1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726451AbgCBSvn (ORCPT ); Mon, 2 Mar 2020 13:51:43 -0500 Received: by mail-ot1-f68.google.com with SMTP id 66so287124otd.9; Mon, 02 Mar 2020 10:51:41 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cH1nDM4uwumr6KdthICcbpNTedeJBeY/wKjOC4m8TLQ=; b=EeW/108PF8Vk/izFryec4ZmriJb9PlrBde9zT17X+01T01pL45SFvgGKJHoXT6ReI0 szDn6ySFYKq/+AWkI2bCuXEjaCuqGxyZnfijahD23dXZxDUacepckHcJHARuDvjRRoW8 AP7mo670oWS/Opofmxfj8c8BPsIqBtf+MMdNtH/5BgUS8MAusPYSb9tyVwz94QuWzV58 wIzrfctzMa3Al3z6+AAYd+eJH+zlDKDJiJK8j3Ha+t37ImBa5z7wlDwU2JsjsI8G0KNd pQCOITAQeljdm/u9UUgXMSUiR0+lQn9e3tl+16JV+lwRnnsqpN+6wtR/5W0azoyEL219 24Rw== X-Gm-Message-State: ANhLgQ2MbDrSdO6OpAVjDjFTaCuxzCiz3FIohkgLcIHKSmvSTguGOb17 85R7PqktzeBRoXbTGYL/Vvm9zU2vrNv4ViN0z/0= X-Received: by 2002:a05:6830:100e:: with SMTP id a14mr435280otp.297.1583175101255; Mon, 02 Mar 2020 10:51:41 -0800 (PST) MIME-Version: 1.0 References: <1582903131-160033-1-git-send-email-john.garry@huawei.com> <1582903131-160033-2-git-send-email-john.garry@huawei.com> In-Reply-To: <1582903131-160033-2-git-send-email-john.garry@huawei.com> From: Geert Uytterhoeven Date: Mon, 2 Mar 2020 19:51:29 +0100 Message-ID: Subject: Re: [PATCH RFC 1/3] spi: Allow SPI controller override device buswidth To: John Garry Cc: Mark Brown , linux-spi , Linuxarm , Linux Kernel Mailing List , MTD Maling List , Andy Shevchenko Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi John, On Fri, Feb 28, 2020 at 4:23 PM John Garry wrote: > Currently ACPI firmware description for a SPI device does not have any > method to describe the data buswidth on the board. > > So even through the controller and device may support higher modes than > standard SPI, it cannot be assumed that the board does - as such, that > device is limited to standard SPI in such a circumstance. > > As a workaround, allow the controller driver supply buswidth override bits, > which are used inform the core code that the controller driver knows the > buswidth supported on that board for that device. Just wondering: can't the controller just override this (e.g. in the .setuup() callback) without having to touch the generic code? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds