From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
tiwai@suse.de, Arnaud Pouliquen <arnaud.pouliquen@st.com>,
liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
Yakir Yang <ykk@rock-chips.com>,
"Subhransu S. Prusty" <subhransu.s.prusty@intel.com>
Subject: Re: [PATCH v3 2/6] ASoC: hdac-hdmi: Add hdmi driver
Date: Mon, 2 Nov 2015 15:36:42 +0530 [thread overview]
Message-ID: <20151102100642.GK21326@localhost> (raw)
In-Reply-To: <20151101030231.GB17819@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1193 bytes --]
On Sun, Nov 01, 2015 at 12:02:31PM +0900, Mark Brown wrote:
> On Tue, Oct 27, 2015 at 04:42:13PM +0900, Vinod Koul wrote:
>
> > + if (err < 0)
> > + dev_err(&hdac->dev, "Failed to query pcm params for nid: %d\n", cvt->nid);
>
> That looks like the NID is being printed as an error code.
No this prints the NID for which query fails, but agree we should print the
error code too, that might be very helpful :)
> > + /*
> > + * Currently on board only 1 pin and 1 converter enabled for
> > + * simplification, more will be added eventually
> > + * So using fixed map for dai_id:pin:cvt
> > + */
> > + return hdac_hdmi_init_dai_map(edev, &hdmi->dai_map[0], hdmi->pin_nid[0],
> > + hdmi->cvt_nid[0], 0);
>
> I'm not entirely sure I understand what this is all doing. It looks
> like it's trying to translate the HDA widget map into a DAPM map which
> seems sensible but it appears it's making some simplifying assumptions
> about the device it's dealing with?
The device is actually quite simple and yes we simplified even further by
ignoring multiple pins for now. We will keep adding more features and adding
stuff to map as we go along..
--
~Vinod
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-11-02 10:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 7:42 [PATCH v3 0/6] ASoC: Add HDA HDMI codec driver Vinod Koul
2015-10-27 7:42 ` [PATCH v3 1/6] ALSA: hdac: structure definition for ext_dma_params Vinod Koul
2015-11-01 2:56 ` Mark Brown
2015-11-02 9:09 ` Takashi Iwai
2015-10-27 7:42 ` [PATCH v3 2/6] ASoC: hdac-hdmi: Add hdmi driver Vinod Koul
2015-11-01 3:02 ` Mark Brown
2015-11-02 10:06 ` Vinod Koul [this message]
2015-11-04 14:48 ` Mark Brown
2015-11-09 4:39 ` Vinod Koul
2015-11-09 7:51 ` Takashi Iwai
2015-11-09 8:13 ` Vinod Koul
2015-10-27 7:42 ` [PATCH v3 3/6] ASoC: hdac_hdmi: Add PM support for HDMI Vinod Koul
2015-10-27 7:42 ` [PATCH v3 4/6] ASoC: hdac_hdmi: Add hdac hdmi dai ops Vinod Koul
2015-10-27 7:42 ` [PATCH v3 5/6] ASoC: hdac_hdmi: Setup and start infoframe Vinod Koul
2015-10-27 7:42 ` [PATCH v3 6/6] ASoC: hdac_hdmi: Use i915 component framework for PM Vinod Koul
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=20151102100642.GK21326@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@st.com \
--cc=broonie@kernel.org \
--cc=lars@metafoo.de \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux@arm.linux.org.uk \
--cc=patches.audio@intel.com \
--cc=subhransu.s.prusty@intel.com \
--cc=tiwai@suse.de \
--cc=ykk@rock-chips.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.