alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de, broonie@kernel.org,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org,
	Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
	Bard Liao <yung-chuan.liao@linux.intel.com>
Subject: Re: [PATCH 1/5] PCI: add ArrowLake-S PCI ID for Intel HDAudio subsystem.
Date: Wed, 2 Aug 2023 10:52:26 -0500	[thread overview]
Message-ID: <20230802155226.GA59821@bhelgaas> (raw)
In-Reply-To: <20230802150105.24604-2-pierre-louis.bossart@linux.intel.com>

On Wed, Aug 02, 2023 at 10:01:01AM -0500, Pierre-Louis Bossart wrote:
> Add part ID to common include file

Please drop period at end of subject and add one at the end of the
commit log.

Also mention the drivers that will use this new #define; looks like
hda_intel.c and ...

Well, actually, I only see that one use, which means we probably
shouldn't add this #define to pci_ids.h, per the comment at the top of
the file.  If there's only one use, use the hex ID in the driver (or
add a #define in the driver itself).

> Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> Reviewed-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
> Reviewed-by: Bard Liao <yung-chuan.liao@linux.intel.com>
> ---
>  include/linux/pci_ids.h | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
> index 3066660cd39b..a6411aa4c331 100644
> --- a/include/linux/pci_ids.h
> +++ b/include/linux/pci_ids.h
> @@ -3058,6 +3058,7 @@
>  #define PCI_DEVICE_ID_INTEL_HDA_RPL_S	0x7a50
>  #define PCI_DEVICE_ID_INTEL_HDA_ADL_S	0x7ad0
>  #define PCI_DEVICE_ID_INTEL_HDA_MTL	0x7e28
> +#define PCI_DEVICE_ID_INTEL_HDA_ARL_S	0x7f50
>  #define PCI_DEVICE_ID_INTEL_SCH_LPC	0x8119
>  #define PCI_DEVICE_ID_INTEL_SCH_IDE	0x811a
>  #define PCI_DEVICE_ID_INTEL_HDA_POULSBO	0x811b
> -- 
> 2.39.2
> 

  reply	other threads:[~2023-08-02 15:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 15:01 [PATCH 0/5] ALSA/PCI: hda: add ARL-S support, config for MTL/LNL Pierre-Louis Bossart
2023-08-02 15:01 ` [PATCH 1/5] PCI: add ArrowLake-S PCI ID for Intel HDAudio subsystem Pierre-Louis Bossart
2023-08-02 15:52   ` Bjorn Helgaas [this message]
2023-08-02 15:57     ` Takashi Iwai
2023-08-02 16:07       ` Pierre-Louis Bossart
2023-08-02 16:25         ` Bjorn Helgaas
2023-08-02 16:34           ` Mark Brown
2023-08-02 18:14             ` Pierre-Louis Bossart
2023-08-02 15:01 ` [PATCH 2/5] ALSA: hda: add HD Audio PCI ID for Intel Arrow Lake-S Pierre-Louis Bossart
2023-08-02 15:01 ` [PATCH 3/5] ALSA: hda: intel-dsp-cfg: use common include for MeteorLake Pierre-Louis Bossart
2023-08-02 15:01 ` [PATCH 4/5] ALSA: hda: intel-dsp-cfg: add LunarLake support Pierre-Louis Bossart
2023-08-02 15:01 ` [PATCH 5/5] ALSA: hda/i915: extend connectivity check to cover Intel ARL Pierre-Louis Bossart
2023-08-04 11:10 ` [PATCH 0/5] ALSA/PCI: hda: add ARL-S support, config for MTL/LNL 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=20230802155226.GA59821@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=bhelgaas@google.com \
    --cc=broonie@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=tiwai@suse.de \
    --cc=yung-chuan.liao@linux.intel.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;
as well as URLs for NNTP newsgroup(s).