From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: fsl_asrc: Add reg_defaults for regmap to fix kernel dump
Date: Tue, 28 Oct 2014 09:37:34 -0700 [thread overview]
Message-ID: <20141028163733.GA6480@Asurada> (raw)
In-Reply-To: <20141028104742.GP18557@sirena.org.uk>
On Tue, Oct 28, 2014 at 10:47:42AM +0000, Mark Brown wrote:
> On Mon, Oct 27, 2014 at 09:26:26PM -0700, Nicolin Chen wrote:
> > On Tue, Oct 28, 2014 at 12:19:04AM +0000, Mark Brown wrote:
>
> > > It's not a bug, it's not reasonable to default allocations to atomic and
> > > we can't really tell what context we're in. Anything used inside a
> > > heavily locked path should either have a default provided or arrange for
> > > a prior write to set up the cache.
>
> > I've a little trouble to understand the prior write over here. Inside my
> > probe() there's a register_init() call which has a set of regmap_write().
> > And then the first regmap_write() results the dump. Does that mean this
> > regmap_write() isn't prior write? If so, how should I do if not setting
>
> Oh, bother. We fixed things so that we're now always running with the
> spinlock held... never mind.
Okay...so only one choice left.
> > default values here -- Some IPs may have default value 0 for registers.
> > And this would make reg_defaults tedious since there's nothing special
> > to assign.
>
> Write a small script then, or a little bit of code to create the
> defaults dynamically.
It actually doesn't bother me at all. I just thought there might be
a simpler way. :)
Thank you
Nicolin
WARNING: multiple messages have this Message-ID (diff)
From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: fsl_asrc: Add reg_defaults for regmap to fix kernel dump
Date: Tue, 28 Oct 2014 09:37:34 -0700 [thread overview]
Message-ID: <20141028163733.GA6480@Asurada> (raw)
In-Reply-To: <20141028104742.GP18557@sirena.org.uk>
On Tue, Oct 28, 2014 at 10:47:42AM +0000, Mark Brown wrote:
> On Mon, Oct 27, 2014 at 09:26:26PM -0700, Nicolin Chen wrote:
> > On Tue, Oct 28, 2014 at 12:19:04AM +0000, Mark Brown wrote:
>
> > > It's not a bug, it's not reasonable to default allocations to atomic and
> > > we can't really tell what context we're in. Anything used inside a
> > > heavily locked path should either have a default provided or arrange for
> > > a prior write to set up the cache.
>
> > I've a little trouble to understand the prior write over here. Inside my
> > probe() there's a register_init() call which has a set of regmap_write().
> > And then the first regmap_write() results the dump. Does that mean this
> > regmap_write() isn't prior write? If so, how should I do if not setting
>
> Oh, bother. We fixed things so that we're now always running with the
> spinlock held... never mind.
Okay...so only one choice left.
> > default values here -- Some IPs may have default value 0 for registers.
> > And this would make reg_defaults tedious since there's nothing special
> > to assign.
>
> Write a small script then, or a little bit of code to create the
> defaults dynamically.
It actually doesn't bother me at all. I just thought there might be
a simpler way. :)
Thank you
Nicolin
next prev parent reply other threads:[~2014-10-28 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 2:03 [PATCH] ASoC: fsl_asrc: Add reg_defaults for regmap to fix kernel dump Nicolin Chen
2014-10-25 2:03 ` Nicolin Chen
2014-10-28 0:19 ` Mark Brown
2014-10-28 0:19 ` Mark Brown
2014-10-28 4:26 ` Nicolin Chen
2014-10-28 4:26 ` Nicolin Chen
2014-10-28 10:47 ` Mark Brown
2014-10-28 10:47 ` Mark Brown
2014-10-28 16:37 ` Nicolin Chen [this message]
2014-10-28 16:37 ` Nicolin Chen
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=20141028163733.GA6480@Asurada \
--to=nicoleotsuka@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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.