From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Eric Millbrandt <emillbrandt@dekaresearch.com>,
Wolfgang Denk <wd@denx.de>
Subject: Re: [PATCH 0/2] mpc5200 ac97 gpio reset
Date: Wed, 9 Jun 2010 16:11:25 +0100 [thread overview]
Message-ID: <20100609151124.GB17945@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTinxoQ7PL2OssJc5dZi2WnhkXMaTTGR7OVWxqL2g@mail.gmail.com>
On Wed, Jun 09, 2010 at 10:41:23AM -0400, Jon Smirl wrote:
> On Wed, Jun 9, 2010 at 10:32 AM, Mark Brown
> > Please include this quote in the changelog for the patch, if this a
> > documented workaround from the vendor that's a very different thing to
> > something that you've found happens to work on your systems (which is
> > more what your changelog sounded like).
> Mark, is there a way to ask the chip if it is in test mode? We need to
> be sure that's whats happening and it isn't some other glitch.
I'd need to work with the hardware teams to obtain this information, but
I can confirm that having SYNC high while doing a reset is not supported
and so fixing the driver to not do that is a good idea independantly of
what it actually does to the chip.
prev parent reply other threads:[~2010-06-09 15:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 16:46 [PATCH 0/2] mpc5200 ac97 gpio reset Eric Millbrandt
2010-06-08 16:46 ` [PATCH 1/2] powerpc/5200: Export port-config Eric Millbrandt
2010-06-08 16:46 ` [PATCH 2/2] sound/soc: mpc5200_psc_ac97: Use gpio pins for cold reset Eric Millbrandt
2010-06-09 10:25 ` Mark Brown
2010-06-10 22:11 ` [PATCH 1/2] powerpc/5200: Export port-config Grant Likely
2010-06-09 0:24 ` [PATCH 0/2] mpc5200 ac97 gpio reset Jon Smirl
2010-06-09 6:13 ` Wolfgang Denk
2010-06-09 10:30 ` Mark Brown
2010-06-09 14:24 ` Eric Millbrandt
2010-06-10 22:07 ` Grant Likely
2010-06-10 23:14 ` Mark Brown
2010-06-10 23:31 ` Grant Likely
2010-06-09 12:21 ` Jon Smirl
2010-06-09 14:21 ` Eric Millbrandt
2010-06-09 14:32 ` Mark Brown
2010-06-09 14:41 ` Jon Smirl
2010-06-09 15:11 ` 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=20100609151124.GB17945@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=emillbrandt@dekaresearch.com \
--cc=jonsmirl@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=wd@denx.de \
/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.