From: "Andrea Tessadri" <tessadriandrea@gmail.com>
To: Eric Nelson <ericnelsonaz@gmail.com>
Cc: Andrey Zhizhikin <andrey.z@gmail.com>,
meta-freescale Mailing List <meta-freescale@yoctoproject.org>
Subject: Re: [meta-freescale] SPI for IMX6x with cyclic DMA
Date: Thu, 13 Aug 2020 17:34:11 +0200 [thread overview]
Message-ID: <CAD-cv=OAU3ZYiT60=OZ97LZcNbvG-zFSipCU75+LTcSo0=gudg@mail.gmail.com> (raw)
In-Reply-To: <6bd6ba74-1b5f-4f9d-cc68-73791014014a@nelint.com>
[-- Attachment #1: Type: text/plain, Size: 1768 bytes --]
Great, thanks!
Il gio 13 ago 2020, 17:17 Eric Nelson <ericnelsonaz@gmail.com> ha scritto:
> Hi Andrea,
>
> On 8/13/20 7:28 AM, Andrey Zhizhikin wrote:
> > On Thu, Aug 13, 2020 at 3:31 PM Andrea Tessadri
> > <tessadriandrea@gmail.com> wrote:
> >>
> >> I've just developed and tested cyclic DMA transfer for a SPI device on
> a IMX6UL with kernel 4.9.88
>
> Cool!
>
> >> I wanted to have a single SPI transfer repeated continuously in order
> to feed a DAC for generation of a particular waveform for a medical device,
> without interruption and minimal jitter (this is why I though to make the
> change at low level, instead of making the protocol driver to pump several
> identical messages to SPI subsystem)
> >> I am wondering if this feature could be interesting for other
> applications and if it is worth to submit a patch for drivers/spi/spi-imx.c
> >
> > This is definitely a wrong list for those changes, it should go to
> > LKML instead. This list is used for discussions regarding Yocto
> > Project distribution, and I believe you're interested in merging your
> > changes into Kernel. For that you should post this RFC to LKML.
> >
>
> Andrey is right that kernel patches aren't submitted through this list.
>
> Depending on how you've implemented this, the proper mailing list will
> be either or both linux-spi and dmaengine as noted here:
>
> http://vger.kernel.org/vger-lists.html
>
> That said, there are probably more potential users on this list,
> and posting it here might get more feedback than those lists.
>
> And to answer your question about whether it is worth submitting the
> patch set, I'd say "yes". Even if it's not accepted, it might prove
> useful to others.
>
> Regards,
>
>
> Eric
>
[-- Attachment #2: Type: text/html, Size: 2341 bytes --]
prev parent reply other threads:[~2020-08-13 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 13:31 SPI for IMX6x with cyclic DMA Andrea Tessadri
2020-08-13 14:28 ` [meta-freescale] " Andrey Zhizhikin
[not found] ` <6bd6ba74-1b5f-4f9d-cc68-73791014014a@nelint.com>
2020-08-13 15:34 ` Andrea Tessadri [this message]
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='CAD-cv=OAU3ZYiT60=OZ97LZcNbvG-zFSipCU75+LTcSo0=gudg@mail.gmail.com' \
--to=tessadriandrea@gmail.com \
--cc=andrey.z@gmail.com \
--cc=ericnelsonaz@gmail.com \
--cc=meta-freescale@yoctoproject.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 read-only IMAP folder(s) and NNTP newsgroup(s).