public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Shijith Thotton <sthotton@marvell.com>
Cc: "bhelgaas@google.com" <bhelgaas@google.com>,
	"ilpo.jarvinen@linux.intel.com" <ilpo.jarvinen@linux.intel.com>,
	"Jonathan.Cameron@huawei.com" <Jonathan.Cameron@huawei.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"rafael@kernel.org" <rafael@kernel.org>,
	"scott@os.amperecomputing.com" <scott@os.amperecomputing.com>,
	Jerin Jacob <jerinj@marvell.com>,
	Srujana Challa <schalla@marvell.com>,
	Vamsi Krishna Attunuru <vattunuru@marvell.com>
Subject: Re: [PATCH v3] PCI: hotplug: Add OCTEON PCI hotplug controller driver
Date: Fri, 8 Nov 2024 06:39:08 -0600	[thread overview]
Message-ID: <20241108123908.GA1657702@bhelgaas> (raw)
In-Reply-To: <SJ0PR18MB44293B3E1A4860D44DD5CD8FD95D2@SJ0PR18MB4429.namprd18.prod.outlook.com>

On Fri, Nov 08, 2024 at 12:17:22PM +0000, Shijith Thotton wrote:
> >> This patch introduces a PCI hotplug controller driver for the OCTEON
> >> PCIe device, a multi-function PCIe device where the first function acts
> >> as a hotplug controller. It is equipped with MSI-x interrupts to notify
> >> the host of hotplug events from the OCTEON firmware.

> >> +config HOTPLUG_PCI_OCTEONEP
> >> +	bool "OCTEON PCI device Hotplug controller driver"
> >
> >s/Marvell PCI device/Cavium OCTEON PCI/ to match other entries.
> 
> Cavium was acquired by Marvell, but we are still using the PCI
> vendor ID  `PCI_VENDOR_ID_CAVIUM`. I hope using Marvell is
> acceptable; please let me  know if this poses any issues.

Oops, sorry, this was my mistake.  I meant to suggest "Marvell OCTEON
PCI Hotplug driver", but I messed up the editing.

> >> +#define OCTEP_DEVID_HP_CONTROLLER 0xa0e3
> >
> >Even though this is a private #define, I think something like
> >PCI_DEVICE_ID_CAVIUM_OCTEP_HP_CTLR would be nice because that's the
> >typical pattern of include/linux/pci_ids.h.
> 
> The same reason mentioned above for not using the name CAVIUM.
> Is it okay to use `PCI_DEVICE_ID_MARVELL_OCTEP_HP_CTLR`?

In this case, I think you should use PCI_DEVICE_ID_CAVIUM... because
the PCI_VENDOR_ID_CAVIUM identifies the Device ID namespace, so the
#defines for the Vendor ID and the Device IDs in that namespace should
match.

> >> +static struct pci_device_id octep_hp_pci_map[] = {
> >> +	{ PCI_DEVICE(PCI_VENDOR_ID_CAVIUM,
> >OCTEP_DEVID_HP_CONTROLLER) },
> >> +	{ },
> >> +};

  reply	other threads:[~2024-11-08 12:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-20 15:27 [PATCH] PCI: hotplug: Add OCTEON PCI hotplug controller driver Shijith Thotton
2024-08-20 16:52 ` Ilpo Järvinen
2024-08-21 10:00   ` Shijith Thotton
2024-08-23  5:22     ` [PATCH v2] " Shijith Thotton
2024-08-23 10:53       ` Ilpo Järvinen
2024-08-23 13:06         ` Shijith Thotton
2024-08-26 10:45       ` [PATCH v3] " Shijith Thotton
2024-09-16  4:43         ` Shijith Thotton
2024-09-26 13:01           ` Shijith Thotton
2024-10-14 12:01             ` Shijith Thotton
2024-10-23  9:06               ` Shijith Thotton
2024-11-06  7:45         ` Shijith Thotton
2024-11-07 20:32         ` Bjorn Helgaas
2024-11-08 12:17           ` Shijith Thotton
2024-11-08 12:39             ` Bjorn Helgaas [this message]
2024-11-10  5:20               ` Shijith Thotton
2024-11-11 13:45         ` [PATCH v4] " Shijith Thotton
2024-11-11 20:14           ` Bjorn Helgaas
2024-11-12  9:25             ` Shijith Thotton
2024-11-12 16:08               ` Bjorn Helgaas
2024-11-13 12:20                 ` Shijith Thotton
2024-11-14  0:03                   ` Bjorn Helgaas
2024-11-14  5:17                     ` Shijith Thotton
2024-08-21 11:24 ` [PATCH] " Jonathan Cameron
2024-08-22 14:49   ` Shijith Thotton
2024-08-23  5:29     ` Shijith Thotton
2024-08-21 13:49 ` kernel test robot

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=20241108123908.GA1657702@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=bhelgaas@google.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jerinj@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=schalla@marvell.com \
    --cc=scott@os.amperecomputing.com \
    --cc=sthotton@marvell.com \
    --cc=vattunuru@marvell.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