From: Chris Ruehl <chris.ruehl-CR359r9tUDPXPF5Rlphj1Q@public.gmane.org>
To: Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
Fabio Estevam <festevam-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Anton Bondarenko
<anton.bondarenko.sama-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Sascha Hauer <kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
"linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: spi-imx: add support for single burst mode (8,16,32)
Date: Wed, 1 Jun 2016 09:54:39 +0800 [thread overview]
Message-ID: <574E405F.9090000@gtsys.com.hk> (raw)
In-Reply-To: <20160531110608.GG31666-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
On Tuesday, May 31, 2016 07:06 PM, Sascha Hauer wrote:
> On Tue, May 31, 2016 at 07:43:37AM -0300, Fabio Estevam wrote:
>> [Adding Sascha and Anton in Cc]
>>
>> On Tue, May 31, 2016 at 6:40 AM, Chris Ruehl <chris.ruehl-CR359r9tUDPXPF5Rlphj1Q@public.gmane.org> wrote:
>>> Hi,
>>>
>>> as imx6 using multiple burst to send data to spi slaves and drop the
>>> chipselect between the words by default my sensor NXP MPL115A1 wasn't
>>> working.
>
> I generally recommend to use GPIO Chip selects. The SPI controller has
> its own ideas when to assert the chipselects which is hard to match (if
> possible at all) with what Linux SPI expects. See the cs-gpios device
> tree property.
>
> Sascha
Sascha that's a good approach to fight this problem, if you have the
choice. Sadly my hardware design is finished and I can only switch to
a gpio by run wires on the finished PCB.. and that's not what I want.
With the single burst mode patch, the logic analyser shows a very nice and
and clean and accurate chipselect clock MOSI and MISO.
Chris
--
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
next prev parent reply other threads:[~2016-06-01 1:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 9:40 spi-imx: add support for single burst mode (8,16,32) Chris Ruehl
[not found] ` <574D5C2B.1000400-CR359r9tUDPXPF5Rlphj1Q@public.gmane.org>
2016-05-31 10:43 ` Fabio Estevam
[not found] ` <CAOMZO5CiW3J+naHfitjv59i4xisYB1R3ATs2qvz4mLh_FMyf+g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-05-31 11:06 ` Sascha Hauer
[not found] ` <20160531110608.GG31666-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2016-06-01 1:54 ` Chris Ruehl [this message]
[not found] ` <574E405F.9090000-CR359r9tUDPXPF5Rlphj1Q@public.gmane.org>
2016-06-01 6:30 ` Sascha Hauer
[not found] ` <20160601063029.GB11074-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2016-06-01 6:39 ` Chris Ruehl
2016-05-31 11:20 ` Vladimir Zapolskiy
[not found] ` <574D7366.5050203-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2016-06-01 1:48 ` Chris Ruehl
2016-05-31 13:08 ` Mark Brown
[not found] ` <20160531130828.GB29837-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-06-01 1:58 ` Chris Ruehl
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=574E405F.9090000@gtsys.com.hk \
--to=chris.ruehl-cr359r9tudpxpf5rlphj1q@public.gmane.org \
--cc=anton.bondarenko.sama-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=festevam-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=s.hauer-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: 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.