From: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: Varun Wadekar <vwadekar-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: "sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org"
<sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Andy Ritger <ARitger-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Bharat Nihalani
<bnihalani-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] mfd: tps6586x: avoid burst writes
Date: Fri, 18 Feb 2011 18:43:54 +0000 [thread overview]
Message-ID: <20110218184354.GA21195@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4D5DF973.8080908-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On Fri, Feb 18, 2011 at 10:15:39AM +0530, Varun Wadekar wrote:
> Mark, confirmed with TI and they say that the entire tps6586x family has
> this behavior so this patch seems ok. The entire family has this
> limitation and so we have to write one byte at a time.
OK, that's good to have confirmed - in that case this should go into
2.6.38 as a bugfix since clearly any device which tries to do a bulk
operation is broken at the minute.
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-02-18 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 10:03 [PATCH] mfd: tps6586x: avoid burst writes vwadekar-DDmLM1+adcrQT0dZR+AlfA
[not found] ` <1297764222-29803-1-git-send-email-vwadekar-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-02-17 1:52 ` Mark Brown
[not found] ` <20110217015216.GE5824-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2011-02-18 4:45 ` Varun Wadekar
[not found] ` <4D5DF973.8080908-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-02-18 18:43 ` 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=20110218184354.GA21195@opensource.wolfsonmicro.com \
--to=broonie-yzvpicuk2aatku/dhu1wvuem+bqzidxxqq4iyu8u01e@public.gmane.org \
--cc=ARitger-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=bnihalani-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=vwadekar-DDmLM1+adcrQT0dZR+AlfA@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.