From: Takashi Iwai <tiwai@suse.de>
To: Huayu Zhang <932367230@qq.com>
Cc: tiwai@suse.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, james.schulman@cirrus.com,
david.rhodes@cirrus.com, rf@opensource.cirrus.com,
perex@perex.cz, sbinding@opensource.cirrus.com,
kailang@realtek.com, zhanghuayu.dev@gmail.com
Subject: Re: add DSD for ThinkBook 16p G4 IRH with Subsystem Id of :
Date: Mon, 08 Jan 2024 14:13:42 +0100 [thread overview]
Message-ID: <87a5pgt1bt.wl-tiwai@suse.de> (raw)
In-Reply-To: <tencent_0ED010E11594001F62B9EF66C41B0FABCC05@qq.com>
On Mon, 08 Jan 2024 13:51:36 +0100,
Huayu Zhang wrote:
>
> Sorry for missing the info within patch and not familiar with the
> mailing system using git. As mentioned in the subject,
> the patch is using to fix the sound issue of ThinkBook 16p G4 IRH with
> Subsystem Id of : 0x17aa38a9. But this just enable the downside (bass)
> speakers. When I tried to adjust the volumn, it atually mapped to the
> frequency division (the lower volumn actually set the bass speakers,
> and higher volumn map to the louder sound of up facing speakers).
> Wondering if this related to ALSA?
The amp behavior is a question to Cirrus people, I suppose.
In anyway, the patch can't be taken as is. You need to submit the
patch in a more formal way.
- Correct the subject line with a proper prefix, e.g.
[PATCH] ALSA: hda: Add DSD for ....
When resubmitting with some changes, put the revision number, too,
[PATCH v2] ALSA: hda: Add DSD for ....
- Give the proper patch description in the patch itself.
- Put your Signed-off-by line after the patch description.
It's a legal requirement.
Please refer to Documentation/process/submitting-patches.rst for
details.
thanks,
Takashi
prev parent reply other threads:[~2024-01-08 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 12:51 add DSD for ThinkBook 16p G4 IRH with Subsystem Id of : Huayu Zhang
2024-01-08 13:13 ` Takashi Iwai [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=87a5pgt1bt.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=932367230@qq.com \
--cc=david.rhodes@cirrus.com \
--cc=james.schulman@cirrus.com \
--cc=kailang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=rf@opensource.cirrus.com \
--cc=sbinding@opensource.cirrus.com \
--cc=tiwai@suse.com \
--cc=zhanghuayu.dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox