From: Mark Brown <broonie@kernel.org> To: Geert Uytterhoeven <geert@linux-m68k.org> Cc: John Garry <john.garry@huawei.com>, linux-spi <linux-spi@vger.kernel.org>, Linuxarm <linuxarm@huawei.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, MTD Maling List <linux-mtd@lists.infradead.org>, Andy Shevchenko <andriy.shevchenko@linux.intel.com> Subject: Re: [PATCH RFC 1/3] spi: Allow SPI controller override device buswidth Date: Mon, 2 Mar 2020 16:33:17 +0000 [thread overview] Message-ID: <20200302163317.GH4166@sirena.org.uk> (raw) In-Reply-To: <CAMuHMdV9v-7eRqi3JjcNaOBpRrC2-gLDCizYOJwhQCjZiLr5dA@mail.gmail.com> [-- Attachment #1: Type: text/plain, Size: 657 bytes --] On Mon, Mar 02, 2020 at 05:12:05PM +0100, Geert Uytterhoeven wrote: > On Fri, Feb 28, 2020 at 4:23 PM John Garry <john.garry@huawei.com> 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 :/ [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org> To: Geert Uytterhoeven <geert@linux-m68k.org> Cc: John Garry <john.garry@huawei.com>, linux-spi <linux-spi@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Linuxarm <linuxarm@huawei.com>, MTD Maling List <linux-mtd@lists.infradead.org>, Andy Shevchenko <andriy.shevchenko@linux.intel.com> Subject: Re: [PATCH RFC 1/3] spi: Allow SPI controller override device buswidth Date: Mon, 2 Mar 2020 16:33:17 +0000 [thread overview] Message-ID: <20200302163317.GH4166@sirena.org.uk> (raw) In-Reply-To: <CAMuHMdV9v-7eRqi3JjcNaOBpRrC2-gLDCizYOJwhQCjZiLr5dA@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 657 bytes --] On Mon, Mar 02, 2020 at 05:12:05PM +0100, Geert Uytterhoeven wrote: > On Fri, Feb 28, 2020 at 4:23 PM John Garry <john.garry@huawei.com> 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 :/ [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --] [-- Attachment #2: Type: text/plain, Size: 144 bytes --] ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-03-02 16:33 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-02-28 15:18 [PATCH RFC 0/3] spi/HiSilicon v3xx: Support dual and quad mode through DMI quirks John Garry 2020-02-28 15:18 ` John Garry 2020-02-28 15:18 ` John Garry 2020-02-28 15:18 ` [PATCH RFC 1/3] spi: Allow SPI controller override device buswidth John Garry 2020-02-28 15:18 ` John Garry 2020-02-28 18:25 ` Applied "spi: Allow SPI controller override device buswidth" to the spi tree Mark Brown 2020-02-28 18:25 ` Mark Brown 2020-02-28 18:25 ` Mark Brown 2020-03-01 10:04 ` [PATCH RFC 1/3] spi: Allow SPI controller override device buswidth Sergei Shtylyov 2020-03-01 10:04 ` Sergei Shtylyov 2020-03-01 10:04 ` Sergei Shtylyov 2020-03-02 9:30 ` John Garry 2020-03-02 9:30 ` John Garry 2020-03-02 12:22 ` Mark Brown 2020-03-02 12:22 ` Mark Brown 2020-03-02 12:22 ` Mark Brown 2020-03-02 16:12 ` Geert Uytterhoeven 2020-03-02 16:12 ` Geert Uytterhoeven 2020-03-02 16:33 ` Mark Brown [this message] 2020-03-02 16:33 ` Mark Brown 2020-03-02 18:51 ` Geert Uytterhoeven 2020-03-02 18:51 ` Geert Uytterhoeven 2020-03-02 18:51 ` Geert Uytterhoeven 2020-03-03 9:42 ` John Garry 2020-03-03 9:42 ` John Garry 2020-03-03 9:42 ` John Garry 2020-03-03 12:43 ` Mark Brown 2020-03-03 12:43 ` Mark Brown 2020-03-03 12:43 ` Mark Brown 2020-02-28 15:18 ` [PATCH RFC 2/3] spi: HiSilicon v3xx: Properly set CMD_CONFIG for Dual/Quad modes John Garry 2020-02-28 15:18 ` John Garry 2020-02-28 15:18 ` John Garry 2020-02-28 18:25 ` Applied "spi: HiSilicon v3xx: Properly set CMD_CONFIG for Dual/Quad modes" to the spi tree Mark Brown 2020-02-28 18:25 ` Mark Brown 2020-02-28 18:25 ` Mark Brown 2020-02-28 15:18 ` [PATCH RFC 3/3] spi: HiSilicon v3xx: Use DMI quirk to set controller buswidth override bits John Garry 2020-02-28 15:18 ` John Garry 2020-02-28 16:20 ` Mark Brown 2020-02-28 16:20 ` Mark Brown 2020-02-28 16:20 ` Mark Brown 2020-02-28 17:17 ` John Garry 2020-02-28 17:17 ` John Garry 2020-02-28 17:17 ` John Garry 2020-02-28 18:25 ` Applied "spi: HiSilicon v3xx: Use DMI quirk to set controller buswidth override bits" to the spi tree Mark Brown 2020-02-28 18:25 ` Mark Brown 2020-02-28 18:25 ` Mark Brown
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20200302163317.GH4166@sirena.org.uk \ --to=broonie@kernel.org \ --cc=andriy.shevchenko@linux.intel.com \ --cc=geert@linux-m68k.org \ --cc=john.garry@huawei.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mtd@lists.infradead.org \ --cc=linux-spi@vger.kernel.org \ --cc=linuxarm@huawei.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.