From: Takashi Iwai <tiwai@suse.de>
To: reaperli <reaperlioc@glenfly.com>
Cc: tiwai@suse.com, linux-kernel@vger.kernel.org,
jasontao <jasontao@glenfly.com>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: hda: Glenfly: add HD Audio PCI IDs and HDMI Codec Vendor IDs.
Date: Tue, 18 Apr 2023 11:44:53 +0200 [thread overview]
Message-ID: <87leip4j8q.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230418083312.5208-1-reaperlioc@glenfly.com>
On Tue, 18 Apr 2023 10:33:12 +0200,
reaperli wrote:
>
> From: jasontao <jasontao@glenfly.com>
>
> Add a set of HD Audio PCI IDS, and the HDMI codec vendor IDs for
> Glenfly Arise.
>
> Signed-off-by: jasontao <jasontao@glenfly.com>
> Signed-off-by: reaperli <reaperlioc@glenfly.com>
The patch looks OK now, but could you submit to alsa-devel ML at the
next time?
About details in the patch:
> @@ -1743,6 +1745,8 @@ static int default_bdl_pos_adj(struct azx *chip)
> }
>
> switch (chip->driver_type) {
> + case AZX_DRIVER_GFHDMI:
> + return 128;
So this looks pretty high in comparison with other chips.
It means that the actual position is much behind the reported
position. Due to a large FIFO? Or what reason?
> @@ -1859,6 +1863,9 @@ static int azx_first_init(struct azx *chip)
> }
> #endif
>
> + if (chip->driver_type == AZX_DRIVER_GFHDMI)
> + bus->polling_mode = 1;
This looks odd, too. Doesn't the hardware give any interrupt back
upon the CORB/RIRB response?
> --- a/sound/pci/hda/patch_hdmi.c
> +++ b/sound/pci/hda/patch_hdmi.c
> @@ -4489,6 +4489,18 @@ static int patch_via_hdmi(struct hda_codec *codec)
> return patch_simple_hdmi(codec, VIAHDMI_CVT_NID, VIAHDMI_PIN_NID);
> }
>
> +static int patch_gf_hdmi(struct hda_codec *codec)
> +{
> + int err;
> +
> + err = patch_generic_hdmi(codec);
> + if (err)
> + return err;
> +
> + codec->no_sticky_stream = 1;
This hack is needed for what reason?
thanks,
Takashi
WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: reaperli <reaperlioc@glenfly.com>
Cc: <perex@perex.cz>, <tiwai@suse.com>,
<linux-kernel@vger.kernel.org>, jasontao <jasontao@glenfly.com>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: hda: Glenfly: add HD Audio PCI IDs and HDMI Codec Vendor IDs.
Date: Tue, 18 Apr 2023 11:44:53 +0200 [thread overview]
Message-ID: <87leip4j8q.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230418083312.5208-1-reaperlioc@glenfly.com>
On Tue, 18 Apr 2023 10:33:12 +0200,
reaperli wrote:
>
> From: jasontao <jasontao@glenfly.com>
>
> Add a set of HD Audio PCI IDS, and the HDMI codec vendor IDs for
> Glenfly Arise.
>
> Signed-off-by: jasontao <jasontao@glenfly.com>
> Signed-off-by: reaperli <reaperlioc@glenfly.com>
The patch looks OK now, but could you submit to alsa-devel ML at the
next time?
About details in the patch:
> @@ -1743,6 +1745,8 @@ static int default_bdl_pos_adj(struct azx *chip)
> }
>
> switch (chip->driver_type) {
> + case AZX_DRIVER_GFHDMI:
> + return 128;
So this looks pretty high in comparison with other chips.
It means that the actual position is much behind the reported
position. Due to a large FIFO? Or what reason?
> @@ -1859,6 +1863,9 @@ static int azx_first_init(struct azx *chip)
> }
> #endif
>
> + if (chip->driver_type == AZX_DRIVER_GFHDMI)
> + bus->polling_mode = 1;
This looks odd, too. Doesn't the hardware give any interrupt back
upon the CORB/RIRB response?
> --- a/sound/pci/hda/patch_hdmi.c
> +++ b/sound/pci/hda/patch_hdmi.c
> @@ -4489,6 +4489,18 @@ static int patch_via_hdmi(struct hda_codec *codec)
> return patch_simple_hdmi(codec, VIAHDMI_CVT_NID, VIAHDMI_PIN_NID);
> }
>
> +static int patch_gf_hdmi(struct hda_codec *codec)
> +{
> + int err;
> +
> + err = patch_generic_hdmi(codec);
> + if (err)
> + return err;
> +
> + codec->no_sticky_stream = 1;
This hack is needed for what reason?
thanks,
Takashi
next prev parent reply other threads:[~2023-04-18 9:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 8:33 [PATCH] ALSA: hda: Glenfly: add HD Audio PCI IDs and HDMI Codec Vendor IDs reaperli
2023-04-18 9:44 ` Takashi Iwai [this message]
2023-04-18 9:44 ` Takashi Iwai
2023-04-23 9:15 ` 答复: [可能是垃圾邮件] " Reaper Li_OC
2023-04-24 14:08 ` Takashi Iwai
2023-04-24 14:08 ` Takashi Iwai
2023-04-23 9:24 ` Reaper Li_OC
2023-04-23 9:24 ` Reaper Li_OC
-- strict thread matches above, loose matches on Subject: below --
2023-04-18 8:23 reaperli
2023-04-14 8:50 ReaperLi
2023-04-14 9:39 ` 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=87leip4j8q.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=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 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.