From: Mark Brown <broonie@kernel.org>
To: Trent Piepho <tpiepho@impinj.com>
Cc: "kyle.roeschley@ni.com" <kyle.roeschley@ni.com>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"geert@linux-m68k.org" <geert@linux-m68k.org>
Subject: Re: [PATCH] spi: Add a sysfs interface to instantiate devices
Date: Fri, 22 Dec 2017 15:56:03 +0000 [thread overview]
Message-ID: <20171222155603.GM1827@finisterre> (raw)
In-Reply-To: <1513890342.26695.4.camel@impinj.com>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
On Thu, Dec 21, 2017 at 09:05:43PM +0000, Trent Piepho wrote:
> On Thu, 2017-12-21 at 14:03 -0600, Kyle Roeschley wrote:
> > Add a sysfs interface to instantiate and delete SPI devices using the
> > spidev driver. This can be used when developing a driver on a
> > self-soldered board which doesn't yet have proper SPI device declaration
> > at the platform level, and presumably for various debugging situations.
> > Inspired by 99cd8e25875a ("i2c: Add a sysfs interface to instantiate
> > devices").
> The i2c interface allows one to specify the type of device to create.
> Why must this interface be linked to spidev and only capable of
> creating spidev devices?
Right, that doesn't seem good. I also can't see anything in the actual
code which suggests that this is tied to spidev except the log messages.
> > + dev);
> > + struct spi_device *spi, *next;
> > + int ret = -ENXIO;
> > + u16 cs;
Please delete unneeded context from mails when replying. Doing this
makes it much easier to find your reply in the message, helping ensure
it won't be missed by people scrolling through the irrelevant quoted
material.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-12-22 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 20:03 [PATCH] spi: Add a sysfs interface to instantiate devices Kyle Roeschley
2017-12-21 20:11 ` Randy Dunlap
2017-12-21 21:05 ` Trent Piepho
2017-12-22 15:56 ` Mark Brown [this message]
2017-12-22 17:11 ` Kyle Roeschley
2017-12-23 8:58 ` Geert Uytterhoeven
2017-12-27 10:31 ` 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=20171222155603.GM1827@finisterre \
--to=broonie@kernel.org \
--cc=geert@linux-m68k.org \
--cc=kyle.roeschley@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=tpiepho@impinj.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