From: Mark Brown <broonie@kernel.org>
To: shumingf@realtek.com
Cc: oder_chiou@realtek.com, jack.yu@realtek.com,
alsa-devel@alsa-project.org, lars@metafoo.de,
cychiang@google.com, lgirdwood@gmail.com, derek.fang@realtek.com,
flove@realtek.com
Subject: Re: [alsa-devel] [PATCH] ASoC: rt1011: Read and apply r0 and temperature device property
Date: Wed, 16 Oct 2019 12:23:49 +0100 [thread overview]
Message-ID: <20191016112349.GC4881@sirena.co.uk> (raw)
In-Reply-To: <20191016085845.11672-1-shumingf@realtek.com>
[-- Attachment #1.1: Type: text/plain, Size: 403 bytes --]
On Wed, Oct 16, 2019 at 04:58:45PM +0800, shumingf@realtek.com wrote:
> +static int rt1011_parse_dp(struct rt1011_priv *rt1011, struct device *dev)
> +{
> + device_property_read_u32(dev, "realtek,temperature_calib",
> + &rt1011->temperature_calib);
> + device_property_read_u32(dev, "realtek,r0_calib",
> + &rt1011->r0_calib);
These are new DT bindings and need to be added to the binding document.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
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-16 11:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 8:58 [alsa-devel] [PATCH] ASoC: rt1011: Read and apply r0 and temperature device property shumingf
2019-10-16 10:49 ` Cheng-yi Chiang
2019-10-16 11:23 ` Mark Brown [this message]
[not found] ` <fb55fba1f6e8441983fbd563e4b89e45@realtek.com>
2019-10-16 11:30 ` Cheng-yi Chiang
2019-10-16 11:38 ` Mark Brown
2019-10-16 12:58 ` [alsa-devel] Applied "ASoC: rt1011: Read and apply r0 and temperature device property" to the asoc tree 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=20191016112349.GC4881@sirena.co.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=cychiang@google.com \
--cc=derek.fang@realtek.com \
--cc=flove@realtek.com \
--cc=jack.yu@realtek.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=oder_chiou@realtek.com \
--cc=shumingf@realtek.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