Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>, Bjorn Helgaas <helgaas@kernel.org>
Cc: alsa-devel@alsa-project.org, 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 11:07:36 -0500	[thread overview]
Message-ID: <206f5a15-29f0-ec7c-1b85-50ace8ae7c2f@linux.intel.com> (raw)
In-Reply-To: <87fs51cu86.wl-tiwai@suse.de>



On 8/2/23 10:57, Takashi Iwai wrote:
> On Wed, 02 Aug 2023 17:52:26 +0200,
> Bjorn Helgaas wrote:
>>
>> 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).
> 
> Judging from the previous patterns, the same ID could be required for
> ASoC SOF driver, too, which isn't included in this patch set.  In
> that case, it's worth to put to pci_ids.h.
> (OTOH, it can be done at a later stage, too.)

I am not following. we just agreed a couple of weeks ago to record ALL
Intel/HDaudio PCI IDs in the same pci_ids.h include file.

ArrowLake-S is the first addition to first file after the work done by
Cezary/Amadeusz. Yes it's required to be added since it'll be used in
other parts later on. But even if there was ONE use of this PCI ID, why
would we not add it for consistency to the global pci_ids.h file?
Takashi's hda_intel.c file would look really bad if we have a mix of
single-use PCIs and shared ones...

Oh and heads-up that I have a change for LunarLake that will require
Mark to pull the branch from Takashi :-)

  reply	other threads:[~2023-08-02 16:11 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
2023-08-02 15:57     ` Takashi Iwai
2023-08-02 16:07       ` Pierre-Louis Bossart [this message]
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=206f5a15-29f0-ec7c-1b85-50ace8ae7c2f@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bhelgaas@google.com \
    --cc=broonie@kernel.org \
    --cc=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --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