From: Mark Brown <broonie@kernel.org>
To: Michal Suchanek <hramrach@gmail.com>
Cc: Maxime Ripard <maxime.ripard@free-electrons.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
linux-spi <linux-spi@vger.kernel.org>,
Martin Sperl <kernel@martin.sperl.org>
Subject: Re: [PATCH] spi: Force the registration of the spidev devices
Date: Wed, 13 May 2015 18:43:08 +0100 [thread overview]
Message-ID: <20150513174308.GG2761@sirena.org.uk> (raw)
In-Reply-To: <CAOMqctTd7xG6mwX9AojTH4uaGDY06xOgDFUP437VDiE0rp0sXA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 394 bytes --]
On Wed, May 13, 2015 at 05:31:05PM +0200, Michal Suchanek wrote:
> But you know, unused i2c bus can be also connected to "make the board
> catch fire" trace and nobody would notice until somebody has the great
> idea to probe it. Incidentally, both i2c and spi cs are active-low
> iirc.
Someone would need to go and explicitly mark an I2C controller as
enabled on a board for that to happen.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-05-13 17:43 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 20:33 Maxime Ripard
2015-05-13 9:34 ` [PATCH] spi: Add option to bind spidev to all chipselects Michal Suchanek
2015-05-13 10:16 ` Maxime Ripard
2015-05-13 10:40 ` Michal Suchanek
2015-05-13 11:05 ` Mark Brown
2015-05-13 11:26 ` [PATCH] spi: Force the registration of the spidev devices 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2014-04-28 17:22 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
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
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=20150513174308.GG2761@sirena.org.uk \
--to=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=hramrach@gmail.com \
--cc=kernel@martin.sperl.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
all inboxes | Powered by JetHome®