All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Jones <michael.jones-P0pTl12WyEgpBod+wgzj8A@public.gmane.org>
To: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Feng Tang <feng.tang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: does cs_change work in spi-dw.c?
Date: Tue, 12 Aug 2014 17:24:37 +0200	[thread overview]
Message-ID: <53EA31B5.4010201@matrix-vision.de> (raw)

Hello,

I'm using spi-dw.c via a userspace spidev device.  I'm doing an SPI read 
access via the ioctl SPI_IOC_MESSAGE().  I would like to execute two 
messages, with the chip select staying active between the two. If I 
understand correctly, this is what the member 'cs_change' in 'struct 
spi_ioc_transfer' is suppose to provide.  What I observe, though, is 
that the chip select deactivates between messages regardless of how I 
set 'cs_change'.

Can anybody confirm that they're able to use the cs_change switch with 
this driver?

I'm using an older kernel (3.10.31-LTSI), but I've browsed the more 
recent changes to this driver and didn't see anything that obviously 
effected this feature.

thanks,
Michael

MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Uwe Furtner, Erhard Meier
--
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-08-12 15:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12 15:24 Michael Jones [this message]
     [not found] ` <53EA31B5.4010201-P0pTl12WyEgpBod+wgzj8A@public.gmane.org>
2014-09-02  5:14   ` does cs_change work in spi-dw.c? Tang, Feng

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=53EA31B5.4010201@matrix-vision.de \
    --to=michael.jones-p0ptl12wyegpbod+wgzj8a@public.gmane.org \
    --cc=feng.tang-ral2JQCrhuEAvxtiuMwx3w@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 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.