From: Grant Likely <grant.likely@secretlab.ca>
To: "André Schwarz" <andre.schwarz@matrix-vision.de>
Cc: LinuxPPC List <linuxppc-dev@ozlabs.org>,
DevTreeDiscuss <devicetree-discuss@lists.ozlabs.org>
Subject: Re: How to define an I2C-to-SPI bridge device ?
Date: Sun, 12 Sep 2010 22:39:57 -0600 [thread overview]
Message-ID: <20100913043957.GA2144@angua.secretlab.ca> (raw)
In-Reply-To: <1284304235.2913.8.camel@swa-e6500>
On Sun, Sep 12, 2010 at 05:10:35PM +0200, André Schwarz wrote:
> > > BTW: would "drivers/misc" be a proper location ?
> > > Who's supposed to pick that driver up and on what list shall I post it
> > > for review ?
> >
> > You should cc spi-devel-general, and feel free to cc me. drivers/misc
> > would probably be an okay place for it to live; but if it only appears
> > on a single machine, then it may make more sense in
> > arch/*/<board-directory>. What arch or SoC is this running on?
>
> ok - currently I'm preparing bring up of a MPC8377 based system.
> But we have this chips on multiple boards and also on generic PCIe
> grabber cards running on any desktop PC.
>
> Since we could use the driver directly after registering the various I2C
> masters I'd prefer to go with drivers/misc. After all it's a simple I2C
> slave device usable by anyone ...
If it is a video capture device, then wouldn't drivers/video
or drivers/media make sense? Search for "MEDIA INPUT" in the
MAINTAINERS file.
g.
next prev parent reply other threads:[~2010-09-13 4:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 8:36 How to define an I2C-to-SPI bridge device ? André Schwarz
2010-09-03 12:08 ` Anton Vorontsov
2010-09-06 11:40 ` Andre Schwarz
2010-09-06 14:37 ` André Schwarz
2010-09-09 18:23 ` Grant Likely
2010-09-10 8:11 ` André Schwarz
2010-09-10 17:37 ` Grant Likely
2010-09-10 18:14 ` André Schwarz
2010-09-10 18:27 ` Anton Vorontsov
2010-09-10 18:28 ` Grant Likely
2010-09-12 15:10 ` André Schwarz
2010-09-13 4:39 ` Grant Likely [this message]
2011-03-25 9:28 ` Andre Schwarz
2011-03-29 16:21 ` Andre Schwarz
2011-03-31 3:43 ` Grant Likely
2010-09-09 17:06 ` Grant Likely
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=20100913043957.GA2144@angua.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=andre.schwarz@matrix-vision.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).