From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: michael.hennerich@analog.com
Cc: linux-input@vger.kernel.org,
device-drivers-devel@blackfin.uclinux.org, drivers@analog.com
Subject: Re: [PATCH 1/3] Input: touchscreen: ad7877 implement specified chip select behavior
Date: Fri, 15 Oct 2010 09:56:11 -0700 [thread overview]
Message-ID: <20101015165610.GB19112@core.coreip.homeip.net> (raw)
In-Reply-To: <1287139250-24777-1-git-send-email-michael.hennerich@analog.com>
On Fri, Oct 15, 2010 at 12:40:48PM +0200, michael.hennerich@analog.com wrote:
> From: Michael Hennerich <michael.hennerich@analog.com>
>
> According to the AD7877 datasheet:
> Each transfer operation is 16-bit. If multiple read/write operations are
> to be performed, CS must be taken high after the end of each read/write
> operation before another read/write operation can be performed by
> taking CS low again.
>
> Make sure CS toggles after each transfer in the message.
>
> Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
Will apply all 3, thanks Michael.
--
Dmitry
next prev parent reply other threads:[~2010-10-15 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 10:40 [PATCH 1/3] Input: touchscreen: ad7877 implement specified chip select behavior michael.hennerich
2010-10-15 10:40 ` [PATCH 2/3] Input: touchscreen: ad7877 implement EV_KEY:BTN_TOUCH reporting michael.hennerich
2010-10-15 10:40 ` [PATCH 3/3] Input: touchscreen: ad7877 filter events where pressure is beyond the maximum michael.hennerich
2010-10-16 1:51 ` [Device-drivers-devel] " Mike Frysinger
2010-10-18 4:08 ` Dmitry Torokhov
2010-10-18 4:24 ` Dmitry Torokhov
2010-10-18 4:25 ` Dmitry Torokhov
2010-10-18 8:13 ` Hennerich, Michael
2010-10-18 8:22 ` Dmitry Torokhov
2010-10-18 8:12 ` Hennerich, Michael
2010-10-15 16:56 ` Dmitry Torokhov [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-15 10:36 [PATCH 1/3] Input: touchscreen: ad7877 implement specified chip select behavior michael.hennerich
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=20101015165610.GB19112@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=drivers@analog.com \
--cc=linux-input@vger.kernel.org \
--cc=michael.hennerich@analog.com \
/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.