From: Sriram Periyasamy <sriramx.periyasamy@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA ML <alsa-devel@alsa-project.org>,
Patches Audio <patches.audio@intel.com>,
Guneshwor Singh <guneshwor.o.singh@intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Mark Brown <broonie@kernel.org>, Jeeja KP <jeeja.kp@intel.com>,
Sanyog Kale <sanyog.r.kale@intel.com>
Subject: Re: [RESEND][PATCH] ASoC: hdac_hdmi: Program pin-port-mux during jack report event
Date: Thu, 21 Jun 2018 13:24:20 +0530 [thread overview]
Message-ID: <20180621075419.GA10037@intel.com> (raw)
In-Reply-To: <s5ho9g5mx2e.wl-tiwai@suse.de>
On Wed, Jun 20, 2018 at 03:01:13PM +0200, Takashi Iwai wrote:
> On Wed, 20 Jun 2018 13:08:21 +0200,
> Sriram Periyasamy wrote:
> >
> > During d3/d0 cycle, the connection selection index of all pins points
> > to the default value. This needs to be restored to ensure audio is
> > restored after d3/d0 cycle.
> >
> > So store the connection selection index and program it during jack
> > report event which gets invoked in cases like d3/d0 cycle, hot plug
> > detection when multiple displays are connected.
>
> Hm, I thought *_CONNECT_SEL being cached and restored at resume
> already by regmap?
>
Yes, legacy HDA HDMI driver has this method whereas ASoC based HDAC HDMI
driver doesn't use regmap. Hence we needed this solution.
Thanks,
Sriram.
next prev parent reply other threads:[~2018-06-21 8:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 11:08 [RESEND][PATCH] ASoC: hdac_hdmi: Program pin-port-mux during jack report event Sriram Periyasamy
2018-06-20 13:01 ` Takashi Iwai
2018-06-21 7:54 ` Sriram Periyasamy [this message]
2018-06-21 8:28 ` Takashi Iwai
2018-06-21 10:45 ` Sriram Periyasamy
2018-06-21 11:14 ` Takashi Iwai
2018-06-22 5:57 ` Sriram Periyasamy
2018-07-09 12:32 ` Sriram Periyasamy
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=20180621075419.GA10037@intel.com \
--to=sriramx.periyasamy@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=guneshwor.o.singh@intel.com \
--cc=jeeja.kp@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@intel.com \
--cc=sanyog.r.kale@intel.com \
--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 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.