From: Mark Brown <broonie@kernel.org>
To: unlisted-recipients:; (no To-header on input)
Cc: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.de,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
nikesh <Nikesh.Oswal@wolfsonmicro.com>
Subject: Re: [PATCH] ASOC: dapm: add param_fixup callback
Date: Tue, 25 Feb 2014 10:05:23 +0900 [thread overview]
Message-ID: <20140225010523.GJ25940@sirena.org.uk> (raw)
In-Reply-To: <1393250058-18430-1-git-send-email-Nikesh.Oswal@wolfsonmicro.com>
[-- Attachment #1: Type: text/plain, Size: 1689 bytes --]
On Mon, Feb 24, 2014 at 01:54:18PM +0000, NikeshOswal wrote:
> From: nikesh <Nikesh.Oswal@wolfsonmicro.com>
You need to fix both your git and e-mail setups, you should be using
"Nikesh Oswal" or similar as your real name and more importantly your
mail setup is sending mail as "NikeshOswal" with no even a domain part
which means you can't be replied to. It is very important that you are
able to get review comments at the address you post from.
> dai-link params for codec-codec links were fixed.
> The fixed link between codec and another chip which
> may be another codec, baseband, bluetooth codec etc
Please use the full width for your changelog.
> Change-Id: Iad6ee3951bc4e8b8bc519c62642a2b4bcd949c18
Don't include noise like this in upstream submissions.
> - const struct snd_soc_pcm_stream *params;
> + struct snd_soc_pcm_stream *params;
> + /* optional params re-writing for dai links */
> + int (*params_fixup)(struct snd_soc_dapm_widget *w, int event);
This isn't a great interface, it relies on the driver peering inside the
core data structures and it means that we have to drop the consts from
users. Systems not using this feature ought to be able to declare their
parameters as static const but this breaks that ability. Similarly
users that are fully dynamic need to allocate some static data to work
with this interface.
If you look at the existing interface you'll also see that it takes an
array of parameters rather than just a single parameter. The idea was
to extend the interface to provide a control to userspace allowing
selection of one of the configurations from a list for use with cases
like modems which can switch between 8kHz and 16kHz modes.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-02-25 1:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 13:54 Nikesh, Oswal
2014-02-25 1:05 ` 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=20140225010523.GJ25940@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Nikesh.Oswal@wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®