Hi,
I have a device tree where I have a GART device and a DRM device which uses
the GART. The GART is implemented by an IOMMU driver (tegra-gart) and
requires the user device to be a child of the GART device (it explicitly
checks for this when the user device is attached).
I've tried two
On 2012-03-13 at 19:13:24 +0100, Grant Likely grant.lik...@secretlab.ca wrote:
On Tue, 13 Mar 2012 12:31:26 +0100, Tobias Klauser tklau...@distanz.ch
wrote:
On 2012-03-12 at 17:04:18 +0100, Grant Likely grant.lik...@secretlab.ca
wrote:
On Mon, 6 Feb 2012 18:59:02 +0100, Tobias Klauser
Grant Likely grant.lik...@secretlab.ca writes:
I bet it is NR_IRQS related. You have SPARSE_IRQ enabled, which means
the maximum number of irq_descs is IRQ_BITMAP_BITS (NR_IRQS + 8192).
The actual definition uses NR_IRQS + 8196. Guess that's a typo. (Does
it really make sense to add NR_IRQS
On 03/04/12 16:35, Grant Likely wrote:
Hi Grant,
On Tue, 03 Apr 2012 10:53:44 +0100, Marc Zyngier marc.zyng...@arm.com wrote:
On 03/04/12 10:22, David Vrabel wrote:
Hi David,
On 02/04/12 17:30, Marc Zyngier wrote:
The GICv2 can have virtualization extension support, consisting
of an
On 05/04/12 13:59, Marc Zyngier wrote:
How about this?
gic: interrupt-controller@2c001000 {
compatible = arm,cortex-a15-gic;
#interrupt-cells = 3;
#address-cells = 1;
#size-cells = 1;
interrupt-controller;
On 04/05/2012 07:59 AM, Marc Zyngier wrote:
On 03/04/12 16:35, Grant Likely wrote:
Hi Grant,
On Tue, 03 Apr 2012 10:53:44 +0100, Marc Zyngier marc.zyng...@arm.com
wrote:
On 03/04/12 10:22, David Vrabel wrote:
Hi David,
On 02/04/12 17:30, Marc Zyngier wrote:
The GICv2 can have
On 05/04/12 14:34, Rob Herring wrote:
On 04/05/2012 07:59 AM, Marc Zyngier wrote:
On 03/04/12 16:35, Grant Likely wrote:
Hi Grant,
On Tue, 03 Apr 2012 10:53:44 +0100, Marc Zyngier marc.zyng...@arm.com
wrote:
On 03/04/12 10:22, David Vrabel wrote:
Hi David,
On 02/04/12 17:30, Marc
On 04/05/2012 09:07 AM, Marc Zyngier wrote:
On 05/04/12 14:34, Rob Herring wrote:
On 04/05/2012 07:59 AM, Marc Zyngier wrote:
On 03/04/12 16:35, Grant Likely wrote:
Hi Grant,
On Tue, 03 Apr 2012 10:53:44 +0100, Marc Zyngier marc.zyng...@arm.com
wrote:
On 03/04/12 10:22, David Vrabel
On 04/05/2012 02:42 AM, Thierry Reding wrote:
Hi,
I have a device tree where I have a GART device and a DRM device which uses
the GART. The GART is implemented by an IOMMU driver (tegra-gart) and
requires the user device to be a child of the GART device (it explicitly
checks for this when
* Stephen Warren wrote:
On 04/05/2012 02:42 AM, Thierry Reding wrote:
Hi,
I have a device tree where I have a GART device and a DRM device which uses
the GART. The GART is implemented by an IOMMU driver (tegra-gart) and
requires the user device to be a child of the GART device (it
On Wed, Apr 4, 2012 at 10:03 AM, Nicolas Ferre nicolas.fe...@atmel.com wrote:
Arnd, Olof,
I would like you to integrate this fist batch of AT91 related fixes. They
are covering DT and USB related issues that we have seen on top of 3.4-rc1.
I have also included modifications of the OHCI USB
* Thierry Reding wrote:
* Stephen Warren wrote:
On 04/05/2012 02:42 AM, Thierry Reding wrote:
Hi,
I have a device tree where I have a GART device and a DRM device which
uses
the GART. The GART is implemented by an IOMMU driver (tegra-gart) and
requires the user device to be
Some MSM SoCs have a small serial-type bus that is used to
communicate with the PMIC devices. This interface is always
point-to-point. I'm doing a device-tree conversion of the driver that
Ken Heitke posted last year https://lkml.org/lkml/2011/2/17/503.
A naive conversion to device tree, would
On 04/05/2012 10:23 AM, Thierry Reding wrote:
* Stephen Warren wrote:
On 04/05/2012 02:42 AM, Thierry Reding wrote:
Hi,
I have a device tree where I have a GART device and a DRM device which uses
the GART. The GART is implemented by an IOMMU driver (tegra-gart) and
requires the user device
On 04/05/2012 12:08 PM, Thierry Reding wrote:
* Thierry Reding wrote:
* Stephen Warren wrote:
On 04/05/2012 02:42 AM, Thierry Reding wrote:
Hi,
I have a device tree where I have a GART device and a DRM device which uses
the GART. The GART is implemented by an IOMMU driver (tegra-gart) and
On 04/05/2012 12:15 PM, David Brown wrote:
Some MSM SoCs have a small serial-type bus that is used to
communicate with the PMIC devices. This interface is always
point-to-point. I'm doing a device-tree conversion of the driver that
Ken Heitke posted last year
On Thu, Apr 05, 2012 at 01:23:46PM -0600, Stephen Warren wrote:
On 04/05/2012 12:15 PM, David Brown wrote:
Some MSM SoCs have a small serial-type bus that is used to
communicate with the PMIC devices. This interface is always
point-to-point. I'm doing a device-tree conversion of the
Allow a NAND chip using the orion_nand driver to be described using devicetree.
Signed-off-by: Jamie Lentin j...@lentin.co.uk
---
* WARN when bank-width is out of range, as suggested by Andrew Lunn
* Document all parameters.
* Convert bank-width to be in bytes
* Add explicit defaults for cle,
This adds timings for T20 and T25 Seaboards, using the bindings found here:
http://patchwork.ozlabs.org/patch/132928/
We supply both full speed options for normal running, and half speed options
for testing / development.
Signed-off-by: Simon Glass s...@chromium.org
---
Changes in v4:
- Remove
Hi,
On Tue, Apr 3, 2012 at 5:47 PM, Simon Glass s...@chromium.org wrote:
Hi Olof,
On Mon, Apr 2, 2012 at 10:22 PM, Olof Johansson o...@lixom.net wrote:
On Mon, Apr 2, 2012 at 4:19 PM, Simon Glass s...@chromium.org wrote:
This adds timings for T20 and T25 Seaboards, using the bindings found
Grant Likely grant.lik...@secretlab.ca writes:
Can you attach console output logs for each of configs above and also
with NR_IRQS=128? That might give me some clues as to which specific
code is causing the issues.
It really looks like the issue starts when irq_expand_nr_irqs is called
the
On Tue, 2012-03-13 at 01:57 +, Jason Cooper wrote:
+DT_MACHINE_START(KIRKWOOD_DT, Marvell Kirkwood (Flattened Device Tree))
This ends up as Machine: in /proc/cpuinfo, which seems to be normal?
Would it be worth trying to dynamically modify the machine string based
on the actual hardware
On Thu, Apr 05, 2012 at 11:07:36PM +0100, Ian Campbell wrote:
On Tue, 2012-03-13 at 01:57 +, Jason Cooper wrote:
+DT_MACHINE_START(KIRKWOOD_DT, Marvell Kirkwood (Flattened Device Tree))
This ends up as Machine: in /proc/cpuinfo, which seems to be normal?
Would it be worth trying to
From: David Daney david.da...@cavium.com
In commit 4bbdd45a (irq_domain/powerpc: eliminate irq_map; use
irq_alloc_desc() instead) code was added that ignores error returns
from irq_alloc_desc_from() by (silently) casting the return value to
unsigned. The negitive value error return now suddenly
-Original Message-
From: Kumar Gala [mailto:ga...@kernel.crashing.org]
Sent: Wednesday, April 04, 2012 9:09 PM
To: Jia Hongtao-B38951
Cc: linuxppc-...@lists.ozlabs.org; Li Yang-R58472; devicetree-
disc...@lists.ozlabs.org
Subject: Re: [RFC] powerpc/fsl-pci: Document the fsl,has-isa
On Fri, Mar 30, 2012 at 2:23, Thomas Abraham thomas.abra...@linaro.org wrote:
Subject: [PATCH v2] video: s3c-fb: Add device tree support
Add device tree based discovery support for Samsung's display controller
framebuffer driver.
Cc: Jingoo Han jg1@samsung.com
Cc: Grant Likely
On 04/05/2012 06:52 PM, David Daney wrote:
From: David Daney david.da...@cavium.com
In commit 4bbdd45a (irq_domain/powerpc: eliminate irq_map; use
irq_alloc_desc() instead) code was added that ignores error returns
from irq_alloc_desc_from() by (silently) casting the return value to
27 matches
Mail list logo
