linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Giuseppe Lippolis" <giu.lippolis-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: <linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: RT5350 spi half duplex?
Date: Wed, 18 Jan 2017 21:39:06 +0100	[thread overview]
Message-ID: <008601d271ca$ea3e7560$bebb6020$@gmail.com> (raw)

Hi,
I’m experimenting the spi interface on a RT5350 target.
Its spi driver set the interface as half duplex

        master->dev.of_node = pdev->dev.of_node;
        master->mode_bits = RT2880_SPI_MODE_BITS;
        master->bits_per_word_mask = SPI_BPW_MASK(8);
        master->min_speed_hz = clk_get_rate(clk) / 128;
        master->max_speed_hz = clk_get_rate(clk) / 2;
        master->flags = SPI_MASTER_HALF_DUPLEX;
        master->setup = rt2880_spi_setup;
        master->prepare_message = rt2880_spi_prepare_message;
        master->set_cs = rt2880_spi_set_cs;
        master->transfer_one = rt2880_spi_transfer_one,

but from the datasheet it seems that the device is full duplex capable.
Is there any reason to set the driver in this way?

By the way my debug was not easy because the 

      static int __spi_validate(struct spi_device *spi, struct spi_message
*message)
      
in spi.c doesn’t report any error message when an error condition is found.
Is there any reason to do in this way?
Can I send a patch with some error message?

Thanks, bye. 


--
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:[~2017-01-18 20:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18 20:39 Giuseppe Lippolis [this message]
2017-01-21  7:57 ` AW: RT5350 spi half duplex? Giuseppe Lippolis

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='008601d271ca$ea3e7560$bebb6020$@gmail.com' \
    --to=giu.lippolis-re5jqeeqqe8avxtiumwx3w@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).