From: Mark Brown <broonie@kernel.org>
To: Ben Zhang <benzh@chromium.org>
Cc: John Hsu <KCHSU0@nuvoton.com>,
alsa-devel <alsa-devel@alsa-project.org>,
Anatol Pomozov <anatol@google.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Chih-Chiang Chang <ccchang12@nuvoton.com>
Subject: Re: [PATCH v4 2/2] ASoC: nau8825: Show device properties
Date: Sat, 24 Oct 2015 00:49:07 +0900 [thread overview]
Message-ID: <20151023154907.GG29919@sirena.org.uk> (raw)
In-Reply-To: <CAOV7By+yBAiCOB=QBE3i6pc=0hs04ZNsBF_Rhzr_fqG_Lp-QXg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 827 bytes --]
On Thu, Oct 22, 2015 at 06:48:50PM -0700, Ben Zhang wrote:
> On Thu, Oct 22, 2015 at 9:17 AM, Mark Brown <broonie@kernel.org> wrote:
> > Hrm... we do already have multiple ways of dumping the DT...
> Could you point me to some of the ways of dumping DT? Is there a
The entire device tree is available via /proc/device-tree.
> generic way of dumping device properties provided by ACPI _DSD?
You can also dump the entire ACPI using acpudump from acpica-tools (it
may be packaged under a different name in your distribution).
> Sometimes devices may be flashed with different versions of coreboot
> firmware which contain different _DSD values. When debugging, it's
> helpful to know the exact platform data seen by a codec driver.
Sure, but that's hardly driver specific so the firmwares provide
infrastructure for this.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2015-10-23 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 23:49 [PATCH v4 0/2] ASoC: nau8825: Add FLL config and device property debug Ben Zhang
2015-10-19 23:49 ` [PATCH v4 1/2] ASoC: nau8825: Add FLL configuration Ben Zhang
2015-10-19 23:49 ` [PATCH v4 2/2] ASoC: nau8825: Show device properties Ben Zhang
2015-10-22 16:17 ` Mark Brown
2015-10-23 1:48 ` Ben Zhang
2015-10-23 15:49 ` 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=20151023154907.GG29919@sirena.org.uk \
--to=broonie@kernel.org \
--cc=KCHSU0@nuvoton.com \
--cc=alsa-devel@alsa-project.org \
--cc=anatol@google.com \
--cc=benzh@chromium.org \
--cc=ccchang12@nuvoton.com \
--cc=lgirdwood@gmail.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.