[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdVyU4nOXna-+ThyCjaugGqVknuCHVzzoE-NuN6q3m_grw@mail.gmail.com>
Date: Sun, 3 May 2015 12:02:13 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Martin Sperl <kernel@...tin.sperl.org>
Cc: Mark Brown <broonie@...nel.org>,
Michal Suchanek <hramrach@...il.com>,
"Eric D." <eric.dillmann@...il.com>,
linux-sunxi <linux-sunxi@...glegroups.com>,
Jonathan Corbet <corbet@....net>,
Hans de Goede <hdegoede@...hat.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Maxime Ripard <maxime.ripard@...e-electrons.com>,
linux-spi <linux-spi@...r.kernel.org>
Subject: Re: [linux-sunxi] [PATCH 2/3] spidev: Add DT binding example.
On Sun, May 3, 2015 at 11:01 AM, Martin Sperl <kernel@...tin.sperl.org> wrote:
>> On 30.04.2015, at 21:58, Mark Brown <broonie@...nel.org> wrote:
>> A big reason for that is that it's not in my inbox for me to review,
>> these messages I flagged as unhelpful aren't going to help with that if
>> only because I don't want to create the impression that such behaviour
>> achieves results.
>
> What about implementing it like this:
> echo -n “spi32761.4” > /sys/bus/spi/drivers/spidev/bind
>
> Would this be an acceptable solution?
>
> This is actually mentioned in Documentation/spi/spidev as a
> possible option for the future - quote:
>
>> (Sysfs also supports userspace driven binding/unbinding of drivers to
>> devices. That mechanism might be supported here in the future.)
>
> Not sure why it does not work right now (but it works for “real”
> device-drivers), but I guess it has to do with compatibility checks.
IIRC, PCI drivers support adding more compatible entries through /sysfs.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists