From: Mark Brown <broonie@kernel.org>
To: John Garry <john.garry@huawei.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
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: Tue, 3 Mar 2020 12:43:38 +0000 [thread overview]
Message-ID: <20200303124338.GD3866@sirena.org.uk> (raw)
In-Reply-To: <f6f21e75-7cee-89da-bb87-95327a4ec2cc@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 376 bytes --]
On Tue, Mar 03, 2020 at 09:42:45AM +0000, John Garry wrote:
> However, maybe another callback could be introduced, .early_setup().
One thing I like about the explicit core code is that it makes it much
easier to see which drivers are doing the worrying thing, with just
overwriting things in a callback everything is very freeform and you
have to audit things individually.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: John Garry <john.garry-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: Geert Uytterhoeven
<geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>,
linux-spi <linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linuxarm <linuxarm-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
MTD Maling List
<linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Andy Shevchenko
<andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Subject: Re: [PATCH RFC 1/3] spi: Allow SPI controller override device buswidth
Date: Tue, 3 Mar 2020 12:43:38 +0000 [thread overview]
Message-ID: <20200303124338.GD3866@sirena.org.uk> (raw)
In-Reply-To: <f6f21e75-7cee-89da-bb87-95327a4ec2cc-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 376 bytes --]
On Tue, Mar 03, 2020 at 09:42:45AM +0000, John Garry wrote:
> However, maybe another callback could be introduced, .early_setup().
One thing I like about the explicit core code is that it makes it much
easier to see which drivers are doing the worrying thing, with just
overwriting things in a callback everything is very freeform and you
have to audit things individually.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: John Garry <john.garry@huawei.com>
Cc: linux-spi <linux-spi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linuxarm <linuxarm@huawei.com>,
Geert Uytterhoeven <geert@linux-m68k.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: Tue, 3 Mar 2020 12:43:38 +0000 [thread overview]
Message-ID: <20200303124338.GD3866@sirena.org.uk> (raw)
In-Reply-To: <f6f21e75-7cee-89da-bb87-95327a4ec2cc@huawei.com>
[-- Attachment #1.1: Type: text/plain, Size: 376 bytes --]
On Tue, Mar 03, 2020 at 09:42:45AM +0000, John Garry wrote:
> However, maybe another callback could be introduced, .early_setup().
One thing I like about the explicit core code is that it makes it much
easier to see which drivers are doing the worrying thing, with just
overwriting things in a callback everything is very freeform and you
have to audit things individually.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 484 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-03 12:43 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
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 [this message]
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=20200303124338.GD3866@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: link
Be 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.