From: Mark Brown <broonie@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Maxime Ripard <maxime.ripard@free-electrons.com>,
linux-spi <linux-spi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>
Subject: Re: [PATCH] spi: Force the registration of the spidev devices
Date: Fri, 2 May 2014 09:55:46 -0700 [thread overview]
Message-ID: <20140502165546.GP3245@sirena.org.uk> (raw)
In-Reply-To: <CAMuHMdUWa1_n94sDvv=L_goc+SOnD9CAKi5DzifrY7GWYRdQmw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 374 bytes --]
On Fri, May 02, 2014 at 01:28:26AM +0200, Geert Uytterhoeven wrote:
> And then you want spidev to bind to it. Would it help if DT offered a feature
> to add a compatible entry to a driver at runtime, cfr.
> /sys/bus/pci/drivers/.../new_id on PCI?
Yes, that's what I'd been under the impression that the bind file did -
allowed modification of the list of devices to bind.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-02 16:56 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 17:22 [PATCH] spi: Force the registration of the spidev devices Maxime Ripard
2014-04-29 18:37 ` Mark Brown
2014-04-30 18:06 ` Maxime Ripard
2014-05-01 1:18 ` Mark Brown
2014-05-01 22:36 ` Maxime Ripard
2014-05-01 23:28 ` Geert Uytterhoeven
2014-05-02 16:55 ` Mark Brown [this message]
2014-05-05 4:17 ` Maxime Ripard
2014-05-05 7:10 ` Geert Uytterhoeven
2014-05-05 13:57 ` Alexandre Belloni
2014-05-05 14:22 ` Geert Uytterhoeven
2014-05-05 19:16 ` Mark Brown
2014-05-02 17:40 ` Mark Brown
2014-05-05 4:21 ` Maxime Ripard
2014-05-05 19:17 ` Mark Brown
2014-05-08 2:22 ` Maxime Ripard
-- strict thread matches above, loose matches on Subject: below --
2015-05-12 20:33 Maxime Ripard
2015-05-13 11:26 ` Mark Brown
2015-05-13 12:35 ` Michal Suchanek
2015-05-13 12:51 ` Maxime Ripard
2015-05-13 14:36 ` Mark Brown
2015-05-13 15:31 ` Michal Suchanek
2015-05-13 17:43 ` Mark Brown
2015-05-13 19:09 ` Maxime Ripard
2015-05-13 19:10 ` Geert Uytterhoeven
2015-05-13 19:41 ` Maxime Ripard
2015-05-13 15:37 ` Greg Kroah-Hartman
2015-05-13 15:52 ` Michal Suchanek
2015-05-13 17:13 ` Mark Brown
2015-05-13 17:20 ` Greg Kroah-Hartman
2015-05-13 17:39 ` Mark Brown
2015-05-13 18:16 ` Greg Kroah-Hartman
2015-05-13 18:32 ` Mark Brown
2015-05-13 18:36 ` Greg Kroah-Hartman
2015-05-13 18:51 ` Mark Brown
2015-05-13 19:17 ` Maxime Ripard
2015-05-13 17:50 ` Maxime Ripard
2015-05-13 18:12 ` Mark Brown
2015-05-13 18:17 ` Greg Kroah-Hartman
2015-05-13 19:23 ` Geert Uytterhoeven
2015-05-13 19:26 ` Maxime Ripard
2015-05-13 22:33 ` Greg Kroah-Hartman
2015-05-14 14:34 ` Mark Brown
2015-05-15 8:09 ` Maxime Ripard
2015-07-15 6:27 ` Lucas De Marchi
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=20140502165546.GP3245@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=maxime.ripard@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox