From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> To: Michael Grzeschik <mgr-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> Cc: Michael Grzeschik <m.grzeschik-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>, linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org Subject: Re: [PATCH 3/3] spi: psdev: add passive serial driver Date: Fri, 14 Mar 2014 10:22:23 +0000 [thread overview] Message-ID: <20140314102223.GR366@sirena.org.uk> (raw) In-Reply-To: <20140314101907.GF4234-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> [-- Attachment #1: Type: text/plain, Size: 740 bytes --] On Fri, Mar 14, 2014 at 11:19:07AM +0100, Michael Grzeschik wrote: > Second, the driver has "per se" nothing to do with SPI, beside it needs > a clock and data line to transfer an image to the FPGA. (One way, > therefor: passive). It needs to use some SPI controller to do that. Even > the SPI Bitbang driver. Because of this, it depends on the SPI > framework. Lots of drivers use SPI but they sit in the relevant frameworks rather than in the SPI framework. > It is actually not more than that. I took the spidev character device > driver as reference implementation. Any Idea where to put this driver > instead. Like I say somewhere where it sits with other FPGA programming stuff (if that's what it does) would be my first thought. [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 3/3] spi: psdev: add passive serial driver Date: Fri, 14 Mar 2014 10:22:23 +0000 [thread overview] Message-ID: <20140314102223.GR366@sirena.org.uk> (raw) In-Reply-To: <20140314101907.GF4234@pengutronix.de> On Fri, Mar 14, 2014 at 11:19:07AM +0100, Michael Grzeschik wrote: > Second, the driver has "per se" nothing to do with SPI, beside it needs > a clock and data line to transfer an image to the FPGA. (One way, > therefor: passive). It needs to use some SPI controller to do that. Even > the SPI Bitbang driver. Because of this, it depends on the SPI > framework. Lots of drivers use SPI but they sit in the relevant frameworks rather than in the SPI framework. > It is actually not more than that. I took the spidev character device > driver as reference implementation. Any Idea where to put this driver > instead. Like I say somewhere where it sits with other FPGA programming stuff (if that's what it does) would be my first thought. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140314/57c1f7d4/attachment-0001.sig>
next prev parent reply other threads:[~2014-03-14 10:22 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-03-12 15:53 [PATCH 0/3] spi: bitbang fixes and passive serial driver Michael Grzeschik 2014-03-12 15:53 ` Michael Grzeschik 2014-03-12 15:53 ` [PATCH 1/3] spi: bitbang: fix shift for getmosi Michael Grzeschik 2014-03-12 15:53 ` Michael Grzeschik 2014-03-12 16:24 ` Mark Brown 2014-03-12 16:24 ` Mark Brown [not found] ` <20140312162418.GU28112-GFdadSzt00ze9xe1eoZjHA@public.gmane.org> 2014-03-12 21:45 ` Gerhard Sittig 2014-03-12 21:45 ` Gerhard Sittig [not found] ` <1394639617-26917-1-git-send-email-m.grzeschik-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> 2014-03-12 15:53 ` [PATCH 2/3] spi: bitbang: add lsb first support Michael Grzeschik 2014-03-12 15:53 ` Michael Grzeschik 2014-03-12 15:53 ` [PATCH 3/3] spi: psdev: add passive serial driver Michael Grzeschik 2014-03-12 15:53 ` Michael Grzeschik 2014-03-13 17:14 ` Mark Rutland 2014-03-13 17:14 ` Mark Rutland [not found] ` <1394639617-26917-4-git-send-email-m.grzeschik-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> 2014-03-12 16:34 ` Mark Brown 2014-03-12 16:34 ` Mark Brown [not found] ` <20140312163427.GV28112-GFdadSzt00ze9xe1eoZjHA@public.gmane.org> 2014-03-14 10:19 ` Michael Grzeschik 2014-03-14 10:19 ` Michael Grzeschik [not found] ` <20140314101907.GF4234-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> 2014-03-14 10:22 ` Mark Brown [this message] 2014-03-14 10:22 ` Mark Brown [not found] ` <20140314102223.GR366-GFdadSzt00ze9xe1eoZjHA@public.gmane.org> 2014-03-14 13:59 ` Linus Walleij 2014-03-14 13:59 ` Linus Walleij [not found] ` <CACRpkdZoO_hXw-p5ZHeUzMHULq_DEJNzpim0mcO5DBOgP=d60A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2014-03-14 18:11 ` Michael Grzeschik 2014-03-14 18:11 ` Michael Grzeschik 2014-03-12 17:54 ` Alexander Shiyan 2014-03-12 17:54 ` Alexander Shiyan 2014-03-14 8:06 ` Lothar Waßmann 2014-03-14 8:06 ` Lothar Waßmann -- strict thread matches above, loose matches on Subject: below -- 2014-03-12 15:20 [PATCH 0/3] spi: bitbang fixes and " Michael Grzeschik [not found] ` <1394637636-29042-1-git-send-email-m.grzeschik-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> 2014-03-12 15:20 ` [PATCH 3/3] spi: psdev: add " Michael Grzeschik
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=20140314102223.GR366@sirena.org.uk \ --to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \ --cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \ --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \ --cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=m.grzeschik-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \ --cc=mgr-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.