linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>
To: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: spi_finalize_current_transfer()?
Date: Mon, 13 Jan 2014 13:25:48 +0100	[thread overview]
Message-ID: <CAMuHMdVu503YveDyMqJS7Z5fMMzQq5tAgu-72fJGLmvD4acj1A@mail.gmail.com> (raw)

include/linux/spi/spi.h says:

 * @transfer_one: transfer a single spi_transfer. When the
 *                driver is finished with this transfer it must call
 *                spi_finalize_current_transfer() so the subsystem can issue
 *                the next transfer

However, none of the current drivers implementing transfer_on() calls
spi_finalize_current_transfer() (which just does
"complete(&master->xfer_completion)").
They also don't kick master->xfer_completion theirselves, they all have
their own private xfer_completion.

What am I missing?

Thanks!

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2014-01-13 12:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 12:25 Geert Uytterhoeven [this message]
     [not found] ` <CAMuHMdVu503YveDyMqJS7Z5fMMzQq5tAgu-72fJGLmvD4acj1A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-01-13 13:41   ` spi_finalize_current_transfer()? Geert Uytterhoeven

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=CAMuHMdVu503YveDyMqJS7Z5fMMzQq5tAgu-72fJGLmvD4acj1A@mail.gmail.com \
    --to=geert-td1emuhucqxl1znqvxdv9g@public.gmane.org \
    --cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@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: 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).