From: Ashish Chavan <ashish.chavan@kpitcummins.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
"kuninori.morimoto.gx" <kuninori.morimoto.gx@renesas.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
David@alsa-project.org, Chen <david.chen@diasemi.com>,
lrg <lrg@ti.com>
Subject: Re: [PATCH] ASoC: da7210: Add support for spi regmap
Date: Wed, 21 Mar 2012 22:35:53 +0530 [thread overview]
Message-ID: <1332349553.21744.33.camel@matrix> (raw)
In-Reply-To: <20120321163811.GH3226@opensource.wolfsonmicro.com>
> > Actually I don't have enough details about the problem that you
> > mentioned with this. I am waiting for inputs from some body else. Can
>
> ...and didn't bother asking any questions so it's unlikely anyone will
> say anything...
No, actually it's not like that. You mentioned that the sequence should
be changed, which will fix an issue that the driver has with suspend and
resume. I asked other users of this driver about the issue and waiting
for their feedback. I just wanted to have clear picture about the issue
before I commit any change there. Just to make sure that only changing
of sequence is enough or some thing extra need to be done.
>
> > you please elaborate the problem if you have details? so that I can
> > correct it.
>
> What is unclear in the previous feedback? You should be converting this
> to use a regmap patch...
OK, thanks!
next prev parent reply other threads:[~2012-03-21 16:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 15:52 [PATCH] ASoC: da7210: Add support for spi regmap Ashish Chavan
2012-03-21 15:56 ` [alsa-devel] " Mark Brown
2012-03-21 16:41 ` Ashish Chavan
2012-03-21 16:38 ` Mark Brown
2012-03-21 16:38 ` [alsa-devel] " Mark Brown
2012-03-21 17:05 ` Ashish Chavan [this message]
2012-03-21 17:22 ` Mark Brown
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=1332349553.21744.33.camel@matrix \
--to=ashish.chavan@kpitcummins.com \
--cc=David@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=david.chen@diasemi.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.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.