From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Stephen Boyd <swboyd@chromium.org>,
Cheng-yi Chiang <cychiang@chromium.org>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Tzung-Bi Shih <tzungbi@chromium.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hung-Te Lin <hungte@chromium.org>,
Tzung-Bi Shih <tzungbi@google.com>,
Mark Brown <broonie@kernel.org>,
Sean Paul <seanpaul@chromium.org>,
Dylan Reid <dgreid@chromium.org>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [alsa-devel] [PATCH] firmware: vpd: Add an interface to read VPD value
Date: Wed, 9 Oct 2019 15:05:12 +0100 [thread overview]
Message-ID: <e968e478-bb48-5b05-b6c4-ae1bf77f714f@linaro.org> (raw)
In-Reply-To: <5d9ca7e4.1c69fb81.7f8fa.3f7d@mx.google.com>
On 08/10/2019 16:14, Stephen Boyd wrote:
>> 3) As my use case does not use device tree, it is hard for ASoC
>> machine to access nvmem device. I am wondering if I can use
>> nvm_cell_lookup so machine driver can find the nvmem device using a
>> con_id. But currently the cell lookup API requires a matched device,
>> which does not fit my usage because there will be different machine
>> drivers requesting the value.
>> I think I can still workaround this by adding the lookup table in
>> machine driver. This would seem to be a bit weird because I found that
>> most lookup table is added in provider side, not consumer side. Not
>> sure if this is logically correct.
> Maybe Srini has some input here. It looks like your main concern is
> consumer to provider mapping?
>
In non-DT setup, there are various ways to lookup nvmem provider.
1> nvmem_device_get()/put() using provider devid/name. I think you
should be able to use this in your case.
2> nvmem_register_notifier() which notifies when nvmem provider is added
to system.
3> nvmem_device_find() with own match function this will be merged in
next window (https://lkml.org/lkml/2019/10/3/215)
If none of these are of any help, could explain what exactly are you
looking for w.r.t nvmem to be able to move to what Stephen Boyd suggested?
--srini
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-10-09 14:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 7:16 [alsa-devel] [PATCH] firmware: vpd: Add an interface to read VPD value Cheng-Yi Chiang
2019-10-07 8:03 ` Tzung-Bi Shih
2019-10-07 8:52 ` Cheng-yi Chiang
2019-10-07 12:27 ` Guenter Roeck
2019-10-07 13:58 ` Cheng-yi Chiang
2019-10-07 15:35 ` Stephen Boyd
2019-10-07 18:50 ` Cheng-yi Chiang
2019-10-08 15:14 ` Stephen Boyd
2019-10-09 13:37 ` Mark Brown
2019-10-09 14:05 ` Srinivas Kandagatla [this message]
2019-10-14 3:21 ` Cheng-yi Chiang
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=e968e478-bb48-5b05-b6c4-ae1bf77f714f@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cychiang@chromium.org \
--cc=dgreid@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=hungte@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=seanpaul@chromium.org \
--cc=swboyd@chromium.org \
--cc=tzungbi@chromium.org \
--cc=tzungbi@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).