All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH v2] gpio: octeon_gpio: Add GPIO controller driver for Octeon
Date: Fri, 17 Jul 2020 08:03:34 +0200	[thread overview]
Message-ID: <9c783cb4-9168-3a32-1e96-4fa39fe2c8f8@denx.de> (raw)
In-Reply-To: <f8186202c0aaa0ce491ec6e7b7b0b3b00b92de75.camel@gmail.com>

Hi Daniel,

On 16.07.20 20:44, Daniel Schwierzeck wrote:

<snip>

>> +U_BOOT_DRIVER(octeon_gpio) = {
>> +	.name	= "octeon_gpio",
>> +	.id	= UCLASS_GPIO,
>> +	.of_match = of_match_ptr(octeon_gpio_ids),
>> +	.probe = octeon_gpio_probe,
>> +	.priv_auto_alloc_size = sizeof(struct octeon_gpio),
>> +	.ops	= &octeon_gpio_ops,
>> +	.flags	= DM_FLAG_PRE_RELOC,
>> +};
>> +
>> +static struct pci_device_id octeon_gpio_supported[] = {
>> +	{ PCI_VDEVICE(CAVIUM, PCI_DEVICE_ID_CAVIUM_GPIO),
>> +	  .driver_data = (ulong)&gpio_octeontx_data },
>> +	{ },
>> +};
> 
> I can't build that with the Octeon base support because
> PCI_VENDOR_ID_CAVIUM and PCI_DEVICE_ID_CAVIUM_GPIO are missing in U-
> Boot's include/pci_ids.h. I can only find PCI_VENDOR_ID_CAVIUM in Linux
> but not PCI_DEVICE_ID_CAVIUM_GPIO.

Ah yes. Sorry, I missed sending this pci_ids.h patch that I have applied
in my local branches. Here a link to the patch, which has been updated
since the first RFC version:

https://www.mail-archive.com/u-boot at lists.denx.de/msg345960.html

I'll send the new version in a few minutes.

Thanks,
Stefan

  reply	other threads:[~2020-07-17  6:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 12:19 [PATCH v2] gpio: octeon_gpio: Add GPIO controller driver for Octeon Stefan Roese
2020-05-31 14:08 ` Simon Glass
2020-07-16 18:44 ` Daniel Schwierzeck
2020-07-17  6:03   ` Stefan Roese [this message]
2020-07-18 13:25 ` Daniel Schwierzeck
2020-07-21 11:03   ` Stefan Roese
2020-07-21 14:59     ` Daniel Schwierzeck
2020-07-22  8:54       ` Stefan Roese
2020-07-22 11:47         ` Daniel Schwierzeck
2020-07-23 10:07           ` Stefan Roese
2020-07-28 18:58           ` Simon Glass

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=9c783cb4-9168-3a32-1e96-4fa39fe2c8f8@denx.de \
    --to=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    /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.