search for: phandl

...sful "Get Device" means that "device" is non-NULL; that's built into the name. Anyway, if acpi_bus_get_device() fails either something else will fail or we will Oops in the call to acpi_driver_data(). 172 goto end; 173 174 status = acpi_get_parent(handle, &phandle); 175 if (ACPI_FAILURE(status)) { 176 pr_warn(PREFIX "Cannot find acpi parent\n"); 177 return -EINVAL; 178 } 179 180 /* Get the parent device */ 181 result = acpi_bus_get_device(phandle, &pdevice); 182 if (result) { 183 pr_warn(PREFIX "Cann...

...sful "Get Device" means that "device" is non-NULL; that's built into the name. Anyway, if acpi_bus_get_device() fails either something else will fail or we will Oops in the call to acpi_driver_data(). 172 goto end; 173 174 status = acpi_get_parent(handle, &phandle); 175 if (ACPI_FAILURE(status)) { 176 pr_warn(PREFIX "Cannot find acpi parent\n"); 177 return -EINVAL; 178 } 179 180 /* Get the parent device */ 181 result = acpi_bus_get_device(phandle, &pdevice); 182 if (result) { 183 pr_warn(PREFIX "Cann...

...llowing properties shall be under the /firmware/ node. > +Some properties are specific to a transport type. > + > +shmem-based transports (mailbox, smc/hvc): > > - compatible : shall be "arm,scmi" or "arm,scmi-smc" for smc/hvc transports > - mboxes: List of phandle and mailbox channel specifiers. It should contain > @@ -21,6 +24,17 @@ The scmi node with the following properties shall be under the /firmware/ node. > supported. > - shmem : List of phandle pointing to the shared memory(SHM) area as per > generic mailbox client binding. >...

...c2b3 100644 --- a/drivers/gpu/drm/nouveau/core/core/handle.c +++ b/drivers/gpu/drm/nouveau/core/core/handle.c @@ -109,7 +109,7 @@ nouveau_handle_create(struct nouveau_object *parent, u32 _parent, u32 _handle, while (!nv_iclass(namedb, NV_NAMEDB_CLASS)) namedb = namedb->parent; - handle = *phandle = kzalloc(sizeof(*handle), GFP_KERNEL); + handle = kzalloc(sizeof(*handle), GFP_KERNEL); if (!handle) return -ENOMEM; @@ -146,6 +146,9 @@ nouveau_handle_create(struct nouveau_object *parent, u32 _parent, u32 _handle, } hprintk(handle, TRACE, "created\n"); + + *phandle = hand...

This series of patches makes Xen pass a (somewhat) valid device tree to dom0. The device tree for dom0 is the same as the one supplied to Xen except the memory and chosen nodes are adjusted appropriately. We don''t yet make use of the device tree to map MMIO regions or setup interrupts for the guest and we still include the UART used for Xen''s console. Note that loading Linux

...- int ret; /* * Allocate the archdata iommu structure for DT-based devices. @@ -1657,7 +1655,7 @@ static int omap_iommu_add_device(struct device *dev) * IOMMU users. */ if (!dev->of_node) - return 0; + return ERR_PTR(-ENODEV); /* * retrieve the count of IOMMU nodes using phandle size as element size @@ -1670,27 +1668,27 @@ static int omap_iommu_add_device(struct device *dev) arch_data = kcalloc(num_iommus + 1, sizeof(*arch_data), GFP_KERNEL); if (!arch_data) - return -ENOMEM; + return ERR_PTR(-ENOMEM); for (i = 0, tmp = arch_data; i < num_iommus; i++, tmp++...

...bits have only been tested on a software model and are unlikely to work on actual hardware, but I also tested virtio on an ARM Juno. [1] http://www.spinics.net/lists/kvm/msg147624.html Jean-Philippe Brucker (15): virtio: synchronize virtio-iommu headers with Linux FDT: (re)introduce a dynamic phandle allocator virtio: add virtio-iommu Add a simple IOMMU iommu: describe IOMMU topology in device-trees irq: register MSI doorbell addresses virtio: factor virtqueue initialization virtio: add vIOMMU instance for virtio devices virtio: access vring and buffers through IOMMU mappings v...

...cific device, which allows user space to determine info about device regions (e.g. registers) and interrupt info -support for mmapping device regions -mechanism to set how interrupts are signaled Platform devices can get complicated-- potentially with a tree hierarchy of nodes, and links/phandles pointing to other platform devices. The kernel doesn't expose relationships between devices. The kernel just exposes mappable register regions and interrupts. It's up to user space to work out relationships between devices if it needs to-- this can be determined in the device tree exp...

...cific device, which allows user space to determine info about device regions (e.g. registers) and interrupt info -support for mmapping device regions -mechanism to set how interrupts are signaled Platform devices can get complicated-- potentially with a tree hierarchy of nodes, and links/phandles pointing to other platform devices. The kernel doesn't expose relationships between devices. The kernel just exposes mappable register regions and interrupts. It's up to user space to work out relationships between devices if it needs to-- this can be determined in the device tree exp...

...c > @@ -0,0 +1,59 @@ > +/* use the NT native API to create registry key and value that contain > + a zero character */ > + > +#include <ntdef.h> > +#include <stdio.h> > +#include <ddk/wdm.h> > +#include <windef.h> > + > +void create_key_value (PHANDLE handle, WCHAR* key, int key_len, WCHAR* val, int val_len) > +{ > + UNICODE_STRING key_name = { key_len, key_len, key }; > + UNICODE_STRING value_name = { val_len, val_len, val }; > + OBJECT_ATTRIBUTES key_obj; > + InitializeObjectAttributes (&key_obj, &key_name, > +...

...gt; determine > info about device regions (e.g. registers) and interrupt info > -support for mmapping device regions > -mechanism to set how interrupts are signaled > > Platform devices can get complicated-- potentially with a tree > hierarchy > of nodes, and links/phandles pointing to other platform > devices. The kernel doesn't expose relationships between > devices. The kernel just exposes mappable register regions and > interrupts. > It's up to user space to work out relationships between devices > if it needs to-- this can be determi...

....a95794a --- /dev/null +++ b/images/mkzero/mkzero.c @@ -0,0 +1,59 @@ +/* use the NT native API to create registry key and value that contain + a zero character */ + +#include <ntdef.h> +#include <stdio.h> +#include <ddk/wdm.h> +#include <windef.h> + +void create_key_value (PHANDLE handle, WCHAR* key, int key_len, WCHAR* val, int val_len) +{ + UNICODE_STRING key_name = { key_len, key_len, key }; + UNICODE_STRING value_name = { val_len, val_len, val }; + OBJECT_ATTRIBUTES key_obj; + InitializeObjectAttributes (&key_obj, &key_name, + OB...

...tware model and are unlikely to > work on actual hardware, but I also tested virtio on an ARM Juno. > > [1] http://www.spinics.net/lists/kvm/msg147624.html > > Jean-Philippe Brucker (15): > virtio: synchronize virtio-iommu headers with Linux > FDT: (re)introduce a dynamic phandle allocator > virtio: add virtio-iommu > Add a simple IOMMU > iommu: describe IOMMU topology in device-trees > irq: register MSI doorbell addresses > virtio: factor virtqueue initialization > virtio: add vIOMMU instance for virtio devices > virtio: access vring and...

...tware model and are unlikely to > work on actual hardware, but I also tested virtio on an ARM Juno. > > [1] http://www.spinics.net/lists/kvm/msg147624.html > > Jean-Philippe Brucker (15): > virtio: synchronize virtio-iommu headers with Linux > FDT: (re)introduce a dynamic phandle allocator > virtio: add virtio-iommu > Add a simple IOMMU > iommu: describe IOMMU topology in device-trees > irq: register MSI doorbell addresses > virtio: factor virtqueue initialization > virtio: add vIOMMU instance for virtio devices > virtio: access vring and...

https://bugs.freedesktop.org/show_bug.cgi?id=58087 Priority: medium Bug ID: 58087 Assignee: nouveau at lists.freedesktop.org Summary: [-next] nouveau corrupts kernel mm allocator QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: peter at

...with multiple regions and interrupts, new mechanisms are needed in vfio to correlate the regions/interrupts with the device tree structure that drivers use to determine the meaning of device resources. In some cases there are relationships between device, and devices reference other devices using phandle links. The kernel won't expose relationships between devices, but just exposes mappable register regions and interrupts. The changes needed for vfio are around some of the device tree related info that needs to be available with the device fd. 1. VFIO_GROUP_GET_DEVICE_FD User space know...

...with multiple regions and interrupts, new mechanisms are needed in vfio to correlate the regions/interrupts with the device tree structure that drivers use to determine the meaning of device resources. In some cases there are relationships between device, and devices reference other devices using phandle links. The kernel won't expose relationships between devices, but just exposes mappable register regions and interrupts. The changes needed for vfio are around some of the device tree related info that needs to be available with the device fd. 1. VFIO_GROUP_GET_DEVICE_FD User space know...

...NT native API to create registry key and value that contain > > + a zero character */ > > + > > +#include <ntdef.h> > > +#include <stdio.h> > > +#include <ddk/wdm.h> > > +#include <windef.h> > > + > > +void create_key_value (PHANDLE handle, WCHAR* key, int key_len, WCHAR* > val, int val_len) > > +{ > > + UNICODE_STRING key_name = { key_len, key_len, key }; > > + UNICODE_STRING value_name = { val_len, val_len, val }; > > + OBJECT_ATTRIBUTES key_obj; > > + InitializeObjectAttributes (&ke...

...d interrupts, new mechanisms are needed in vfio to correlate the > regions/interrupts with the device tree structure that drivers use > to determine the meaning of device resources. > > In some cases there are relationships between device, and devices > reference other devices using phandle links. The kernel won't expose > relationships between devices, but just exposes mappable register > regions and interrupts. > > The changes needed for vfio are around some of the device tree > related info that needs to be available with the device fd. > > 1. VFIO_GRO...

...user space to determine > info about device regions (e.g. registers) and interrupt info > -support for mmapping device regions > -mechanism to set how interrupts are signaled > > Platform devices can get complicated-- potentially with a tree hierarchy > of nodes, and links/phandles pointing to other platform > devices. The kernel doesn't expose relationships between > devices. The kernel just exposes mappable register regions and interrupts. > It's up to user space to work out relationships between devices > if it needs to-- this can be determined in...