From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Micka <mickamusset-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Geert Uytterhoeven
<geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>,
linux-spi <linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: am335x: spi driver and two chip select
Date: Wed, 13 Apr 2016 05:57:47 +0100 [thread overview]
Message-ID: <20160413045747.GE14664@sirena.org.uk> (raw)
In-Reply-To: <CAF+MRtkyjeu6baWXX-hJathGjAkwz+REExzUBNWtJCROv5KrtA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
On Tue, Apr 12, 2016 at 01:56:27PM +0000, Micka wrote:
Please don't top post, reply in line with needed context. This allows
readers to readily follow the flow of conversation and understand what
you are talking about and also helps ensure that everything in the
discussion is being addressed.
> Do you know a way to fix that ? Idea ? How can I prevent the problem ?
The driver should store settings in driver data (probably using the
device controller_data) in setup() and only write them to the hardware
only when it starts to actually interact with the device.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-04-13 4:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 13:42 am335x: spi driver and two chip select Micka
[not found] ` <CAF+MRt=ZJP2fssLHRUoR9T9EPfWEPN1LC0CLxZ0CgJQy01S3Rw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-12 13:50 ` Geert Uytterhoeven
[not found] ` <CAMuHMdWtHYNLcbX65HzuV6fyPENMR75XrVQ8RkW=y_T=hN44+g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-13 4:51 ` Mark Brown
[not found] ` <CAF+MRtkyjeu6baWXX-hJathGjAkwz+REExzUBNWtJCROv5KrtA@mail.gmail.com>
[not found] ` <CAF+MRtkyjeu6baWXX-hJathGjAkwz+REExzUBNWtJCROv5KrtA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-13 4:57 ` Mark Brown [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=20160413045747.GE14664@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mickamusset-Re5JQEeQqe8AvxtiuMwx3w@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).