search for: bus_flags

...ry, although I admit to not >>>> having debugged it that far). How do I, as a nouveau driver developer, >>>> know not to call pci_enable_msi? Or alternatively how can >>>> pci_enable_msi be taught not to succeed in this case? >>> >>> You can set bus_flags or global pci_msi_enable flag by add quirk function. >>> You can refer to examples in drivers/pci/quirk.c >>> >>> Linux support some broken chipsets or devices to disable msi during device initialization by add quirk. >> >> So let me get this straight -- you...

...struct versatile_panel_type versatile_panels[] = { > > .vsync_start = 220 + 0, > > .vsync_end = 220 + 0 + 2, > > .vtotal = 220 + 0 + 2 + 1, > > - .vrefresh = 390, > > .flags = DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC, > > }, > > .bus_flags = DRM_BUS_FLAG_PIXDATA_DRIVE_NEGEDGE, > > @@ -214,7 +211,6 @@ static const struct versatile_panel_type versatile_panels[] = { > > .vsync_start = 320 + 2, > > .vsync_end = 320 + 2 + 2, > > .vtotal = 320 + 2 + 2 + 2, > > - .vrefresh = 116, > > .fl...

...esumably due to lack of interrupt delivery, although I admit to not >> having debugged it that far). How do I, as a nouveau driver developer, >> know not to call pci_enable_msi? Or alternatively how can >> pci_enable_msi be taught not to succeed in this case? > > You can set bus_flags or global pci_msi_enable flag by add quirk function. > You can refer to examples in drivers/pci/quirk.c > > Linux support some broken chipsets or devices to disable msi during device initialization by add quirk. So let me get this straight -- you're suggesting I add a quirk for every...

...t; @@ -190,7 +188,6 @@ static const struct versatile_panel_type versatile_panels[] = { > .vsync_start = 220 + 0, > .vsync_end = 220 + 0 + 2, > .vtotal = 220 + 0 + 2 + 1, > - .vrefresh = 390, > .flags = DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC, > }, > .bus_flags = DRM_BUS_FLAG_PIXDATA_DRIVE_NEGEDGE, > @@ -214,7 +211,6 @@ static const struct versatile_panel_type versatile_panels[] = { > .vsync_start = 320 + 2, > .vsync_end = 320 + 2 + 2, > .vtotal = 320 + 2 + 2 + 2, > - .vrefresh = 116, > .flags = DRM_MODE_FLAG_NHSYNC | D...

...el_type versatile_panels[] = { >>> .vsync_start = 220 + 0, >>> .vsync_end = 220 + 0 + 2, >>> .vtotal = 220 + 0 + 2 + 1, >>> - .vrefresh = 390, >>> .flags = DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC, >>> }, >>> .bus_flags = DRM_BUS_FLAG_PIXDATA_DRIVE_NEGEDGE, >>> @@ -214,7 +211,6 @@ static const struct versatile_panel_type versatile_panels[] = { >>> .vsync_start = 320 + 2, >>> .vsync_end = 320 + 2 + 2, >>> .vtotal = 320 + 2 + 2 + 2, >>> - .vrefresh = 116, &g...

...to not >>>>> having debugged it that far). How do I, as a nouveau driver developer, >>>>> know not to call pci_enable_msi? Or alternatively how can >>>>> pci_enable_msi be taught not to succeed in this case? >>>> >>>> You can set bus_flags or global pci_msi_enable flag by add quirk function. >>>> You can refer to examples in drivers/pci/quirk.c >>>> >>>> Linux support some broken chipsets or devices to disable msi during device initialization by add quirk. >>> >>> So let me get th...

...of interrupt delivery, although I admit to not >>> having debugged it that far). How do I, as a nouveau driver developer, >>> know not to call pci_enable_msi? Or alternatively how can >>> pci_enable_msi be taught not to succeed in this case? >> >> You can set bus_flags or global pci_msi_enable flag by add quirk function. >> You can refer to examples in drivers/pci/quirk.c >> >> Linux support some broken chipsets or devices to disable msi during device initialization by add quirk. > > So let me get this straight -- you're suggesting I...

...NC | DRM_MODE_FLAG_PVSYNC, }, }, @@ -190,7 +188,6 @@ static const struct versatile_panel_type versatile_panels[] = { .vsync_start = 220 + 0, .vsync_end = 220 + 0 + 2, .vtotal = 220 + 0 + 2 + 1, - .vrefresh = 390, .flags = DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC, }, .bus_flags = DRM_BUS_FLAG_PIXDATA_DRIVE_NEGEDGE, @@ -214,7 +211,6 @@ static const struct versatile_panel_type versatile_panels[] = { .vsync_start = 320 + 2, .vsync_end = 320 + 2 + 2, .vtotal = 320 + 2 + 2 + 2, - .vrefresh = 116, .flags = DRM_MODE_FLAG_NHSYNC | DRM_MODE_FLAG_NVSYNC, },...

On Thu, Jul 3, 2014 at 11:09 PM, Yijing Wang <wangyijing at huawei.com> wrote: > On 2014/7/4 10:43, Ilia Mirkin wrote: >> On Thu, Jul 3, 2014 at 10:35 PM, Yijing Wang <wangyijing at huawei.com> wrote: >>> Hi Brian, >>> From your 01:00.0 VGA compatible controller PCI config register, it supports 1 MSI vector, so I think this >>> card has no

...n't work > (presumably due to lack of interrupt delivery, although I admit to not > having debugged it that far). How do I, as a nouveau driver developer, > know not to call pci_enable_msi? Or alternatively how can > pci_enable_msi be taught not to succeed in this case? You can set bus_flags or global pci_msi_enable flag by add quirk function. You can refer to examples in drivers/pci/quirk.c Linux support some broken chipsets or devices to disable msi during device initialization by add quirk. > > Thanks, > > -ilia > > . > -- Thanks! Yijing

...67,10 @@ static struct pci_bus *pci_alloc_child_bus(struct pci_bus *parent, if (!child) return NULL; - child->self = bridge; child->parent = parent; child->ops = parent->ops; child->sysdata = parent->sysdata; child->bus_flags = parent->bus_flags; - child->bridge = get_device(&bridge->dev); /* initialize some portions of the bus device, but don't register it * now as the parent is not properly set up yet. This device will get @@ -496,6 +487,11 @@ static struct pci_bus *pci_alloc_...

...67,10 @@ static struct pci_bus *pci_alloc_child_bus(struct pci_bus *parent, if (!child) return NULL; - child->self = bridge; child->parent = parent; child->ops = parent->ops; child->sysdata = parent->sysdata; child->bus_flags = parent->bus_flags; - child->bridge = get_device(&bridge->dev); /* initialize some portions of the bus device, but don't register it * now as the parent is not properly set up yet. This device will get @@ -496,6 +487,11 @@ static struct pci_bus *pci_alloc_...

..., pci_bar_rom, res, rom); } } @@ -462,12 +461,10 @@ static struct pci_bus *pci_alloc_child_bus(struct pci_bus *parent, if (!child) return NULL; - child->self = bridge; child->parent = parent; child->ops = parent->ops; child->sysdata = parent->sysdata; child->bus_flags = parent->bus_flags; - child->bridge = get_device(&bridge->dev); /* initialize some portions of the bus device, but don't register it * now as the parent is not properly set up yet. This device will get @@ -484,6 +481,11 @@ static struct pci_bus *pci_alloc_child_bus(struct...

..., pci_bar_rom, res, rom); } } @@ -462,12 +461,10 @@ static struct pci_bus *pci_alloc_child_bus(struct pci_bus *parent, if (!child) return NULL; - child->self = bridge; child->parent = parent; child->ops = parent->ops; child->sysdata = parent->sysdata; child->bus_flags = parent->bus_flags; - child->bridge = get_device(&bridge->dev); /* initialize some portions of the bus device, but don't register it * now as the parent is not properly set up yet. This device will get @@ -484,6 +481,11 @@ static struct pci_bus *pci_alloc_child_bus(struct...

..., pci_bar_rom, res, rom); } } @@ -462,12 +461,10 @@ static struct pci_bus *pci_alloc_child_bus(struct pci_bus *parent, if (!child) return NULL; - child->self = bridge; child->parent = parent; child->ops = parent->ops; child->sysdata = parent->sysdata; child->bus_flags = parent->bus_flags; - child->bridge = get_device(&bridge->dev); /* initialize some portions of the bus device, but don't register it * now as the parent is not properly set up yet. This device will get @@ -484,6 +481,11 @@ static struct pci_bus *pci_alloc_child_bus(struct...

...-190,7 +188,6 @@ static const struct versatile_panel_type > versatile_panels[] = { > .vsync_start = 220 + 0, > .vsync_end = 220 + 0 + 2, > .vtotal = 220 + 0 + 2 + 1, > - .vrefresh = 390, > .flags = DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC, > }, > .bus_flags = DRM_BUS_FLAG_PIXDATA_DRIVE_NEGEDGE, > @@ -214,7 +211,6 @@ static const struct versatile_panel_type > versatile_panels[] = { > .vsync_start = 320 + 2, > .vsync_end = 320 + 2 + 2, > .vtotal = 320 + 2 + 2 + 2, > - .vrefresh = 116, > .flags = DRM_MODE_FLAG_NHSYN...

...NC | DRM_MODE_FLAG_PVSYNC, }, }, @@ -190,7 +188,6 @@ static const struct versatile_panel_type versatile_panels[] = { .vsync_start = 220 + 0, .vsync_end = 220 + 0 + 2, .vtotal = 220 + 0 + 2 + 1, - .vrefresh = 390, .flags = DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC, }, .bus_flags = DRM_BUS_FLAG_PIXDATA_DRIVE_NEGEDGE, @@ -214,7 +211,6 @@ static const struct versatile_panel_type versatile_panels[] = { .vsync_start = 320 + 2, .vsync_end = 320 + 2 + 2, .vtotal = 320 + 2 + 2 + 2, - .vrefresh = 116, .flags = DRM_MODE_FLAG_NHSYNC | DRM_MODE_FLAG_NVSYNC, },...

...NC | DRM_MODE_FLAG_PVSYNC, }, }, @@ -190,7 +188,6 @@ static const struct versatile_panel_type versatile_panels[] = { .vsync_start = 220 + 0, .vsync_end = 220 + 0 + 2, .vtotal = 220 + 0 + 2 + 1, - .vrefresh = 390, .flags = DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC, }, .bus_flags = DRM_BUS_FLAG_PIXDATA_DRIVE_NEGEDGE, @@ -214,7 +211,6 @@ static const struct versatile_panel_type versatile_panels[] = { .vsync_start = 320 + 2, .vsync_end = 320 + 2 + 2, .vtotal = 320 + 2 + 2 + 2, - .vrefresh = 116, .flags = DRM_MODE_FLAG_NHSYNC | DRM_MODE_FLAG_NVSYNC, },...

...p;msi->msi_list, list) { if (entry->irq != 0) avail++; } @@ -777,7 +808,7 @@ out_avail: ret = avail; } - free_msi_irqs(dev); + free_msi_irqs(msi); return ret; } @@ -820,7 +851,7 @@ static int pci_msi_check_device(struct pci_dev *dev, int nvec, int type) if (bus->bus_flags & PCI_BUS_FLAGS_NO_MSI) return -EINVAL; - ret = arch_msi_check_device(dev, nvec, type); + ret = arch_msi_check_device(dev->msi, nvec, type); if (ret) return ret; @@ -861,12 +892,12 @@ void pci_msi_shutdown(struct pci_dev *dev) !pci_dev_msi_enabled(dev, MSI_TYPE)) return;...

Greetings, Following patches are intended to support SR-IOV capability in the Linux kernel. With these patches, people can turn a PCI device with the capability into multiple ones from software perspective, which will benefit KVM and achieve other purposes such as QoS, security, and etc. [PATCH 1/8 v4] PCI: define PCI resource names in a 'enum' [PATCH 2/8 v4] PCI: export __pci_read_base