From: Takashi Iwai <tiwai@suse.de>
To: Reaper Li <reaperlioc@glenfly.com>
Cc: <tiwai@suse.com>, <perex@perex.cz>,
<linux-kernel@vger.kernel.org>, <alsa-devel@alsa-project.org>,
jasontao <jasontao@glenfly.com>
Subject: Re: [PATCH v2] ALSA: hda: Glenfly: add HD Audio PCI IDs and HDMI Codec Vendor IDs.
Date: Tue, 25 Apr 2023 16:17:45 +0200 [thread overview]
Message-ID: <875y9kujue.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230425101524.8020-1-reaperlioc@glenfly.com>
On Tue, 25 Apr 2023 12:15:24 +0200,
Reaper Li wrote:
>
> From: jasontao <jasontao@glenfly.com>
>
> Add a set of HD Audio PCI IDS, and the HDMI codec vendor IDs for
> Glenfly Gpus.
>
> - In default_bdl_pos_adj, set bdl to 128 as Glenfly Gpus have hardware
> limitation, need to increase hdac interrupt interval.
> - In azx_first_init, enable polling mode for Glenfly Gpu. When the codec
> complete the command, it sends interrupt and writes response entries to
> memory, howerver, the write requests sometimes are not actually
> synchronized to memory when driver handle hdac interrupt on Glenfly Gpus.
> If the RIRB status is not updated in the interrupt handler,
> azx_rirb_get_response keeps trying to recevie a response from rirb until
> 1s timeout. Enabling polling mode for Glenfly Gpu can fix the issue.
> - In patch_gf_hdmi, set Glenlfy Gpu Codec's no_sticky_stream as it need
> driver to do actual clean-ups for the linked codec when switch from one
> codec to another.
>
> Signed-off-by: jasontao <jasontao@glenfly.com>
> Signed-off-by: Reaper Li <reaperlioc@glenfly.com>
> ---
> v2: add some comments for code and details in the commit log.
This is almost fine, but could just correct minor warnings
scripts/checkpatch.pl complains?
thanks,
Takashi
next prev parent reply other threads:[~2023-04-25 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 10:15 [PATCH v2] ALSA: hda: Glenfly: add HD Audio PCI IDs and HDMI Codec Vendor IDs Reaper Li
2023-04-25 14:17 ` Takashi Iwai [this message]
2023-04-26 3:30 ` Reaper Li_OC
-- strict thread matches above, loose matches on Subject: below --
2023-04-14 10:29 ReaperLi
2023-04-14 12:17 ` Takashi Iwai
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=875y9kujue.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=jasontao@glenfly.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=reaperlioc@glenfly.com \
--cc=tiwai@suse.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