On Thu, 2011-08-11 at 22:57 -0700, Dmitry Torokhov wrote:
On Fri, Aug 12, 2011 at 01:41:22PM +0900, Mark Brown wrote:
You tend to find that in a lot of systems only need a subset of the
platform data - some of it can get pretty esoteric - or perhaps none at
all so they'll be able to run
On Thu, Aug 11, 2011 at 10:53:43AM -0600, Grant Likely wrote:
On Thu, Aug 11, 2011 at 10:07 AM, Robin Holt h...@sgi.com wrote:
+- compatible : Should be fsl,processor-flexcan and fsl,flexcan
Don't do this. fsl,flexcan is far too generic. Be specific to the
soc part number or the ip core
Hi,
On Fri, Aug 12, 2011 at 01:02:18PM +1000, David Gibson wrote:
That seems to be pretty straightforward to implement, and as soon as
it is useful even for a couple of drivers, it worth adding it.
It is anyway better than having to add a custom property to get the
information we will
On powerpc, the OpenFirmware devices are not matched without specifying
an of_match array. Introduce that array as that is used for matching
on the Freescale P1010 processor.
Signed-off-by: Robin Holt h...@sgi.com
Acked-by: Marc Kleine-Budde m...@pengutronix.de
Acked-by: Wolfgang Grandegger
If our CAN device's device tree node has a clock-frequency property,
then use that value for the can devices clock frequency. If not, fall
back to asking the platform/mach code for the clock frequency associated
with the flexcan device.
Signed-off-by: Robin Holt h...@sgi.com
To: Kumar Gala
On 8/12/2011 6:10 AM, Shawn Guo wrote:
On Tue, Aug 09, 2011 at 11:37:10PM +0200, Cousson, Benoit wrote:
On 8/9/2011 11:16 PM, Grant Likely wrote:
On Tue, Aug 09, 2011 at 11:06:30PM +0200, Cousson, Benoit wrote:
On 8/9/2011 10:55 PM, Grant Likely wrote:
On Tue, Aug 09, 2011 at 07:47:20PM
On Thu, Aug 11, 2011 at 11:06:23AM -0500, Rob Herring wrote:
No, either you have 1 interrupt and it is the combined one. or you have
the 9? separate interrupts. Having both combined and separate hooked up
is a bit dumb, so I would not worry about that case. I would just define
the event
On Fri, Aug 12, 2011 at 10:56:13AM +0200, Cousson, Benoit wrote:
[...]
The devil is in the details, but the way the DMA lines are connected
in OMAP is similar to IRQ lines, and maybe a little bit simpler.
So starting with a copy/paste of the of_irq file should be a good start.
And then the
On 08/12/2011 10:45 AM, Robin Holt wrote:
If our CAN device's device tree node has a clock-frequency property,
then use that value for the can devices clock frequency. If not, fall
back to asking the platform/mach code for the clock frequency associated
with the flexcan device.
On Friday 12 August 2011, Felipe Balbi wrote:
On Fri, Aug 12, 2011 at 01:02:18PM +1000, David Gibson wrote:
the whole point of using *byname() is for the driver to not care about
the order of the resources. So if driver has to provided an ordered list
of names, what's the benefit ? Sounds
On Friday 12 August 2011, Cousson, Benoit wrote:
Arnd Bergmann:
But I really don't think there is value in using IORESOURCE_DMA for this.
We don't have the code to manage DMA resources for more than one DMA
controller AFAICT, and I think we should not add it. Globally
unique interrupt
On 8/12/2011 4:35 PM, Arnd Bergmann wrote:
On Friday 12 August 2011, Felipe Balbi wrote:
On Fri, Aug 12, 2011 at 01:02:18PM +1000, David Gibson wrote:
the whole point of using *byname() is for the driver to not care about
the order of the resources. So if driver has to provided an ordered list
On Fri, Aug 12, 2011 at 9:09 AM, Cousson, Benoit b-cous...@ti.com wrote:
On 8/12/2011 4:35 PM, Arnd Bergmann wrote:
It only make sense for drivers that support both device tree probing
and legacy probing of static platform devices.
Note how almost all drivers use only platform_get_resource
Thomas Abraham wrote at Friday, August 12, 2011 1:06 AM:
On 12 August 2011 01:36, Stephen Warren swar...@nvidia.com wrote:
Thomas Abraham wrote at Thursday, August 11, 2011 12:09 PM:
I did some work on the gpio and pinmux device tree support for exynos.
I thought to discuss with you about
Ben Dooks wrote at Thursday, August 11, 2011 6:48 PM:
On Tue, Aug 09, 2011 at 09:21:31AM -0700, Stephen Warren wrote:
Stephen Warren wrote at Monday, August 08, 2011 1:26 PM:
Rob Herring wrote at Sunday, August 07, 2011 8:38 AM:
On 08/05/2011 05:50 PM, Stephen Warren wrote:
The
This function retrieves a named child node of a given parent node.
Signed-off-by: Stephen Warren swar...@nvidia.com
---
drivers/of/base.c | 18 ++
include/linux/of.h |2 ++
2 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/drivers/of/base.c
This patch modifies Tegra's device tree support to remove the dependency
on harmony_pinmux_init(), thus making it completely board-independent.
Some notes:
* This series is built on top of linux-next with a bunch of patches
applied, in particular the removal of irq_to_gpio and custom
The Tegra GPIO driver will be converted from static registration via
postcore_initcall() to be a platform device later in this patch series.
A new Tegra pinmux platform device will also be added.
Prepare for this by modifying all boards to register the appropriate
platform devices before-hand, so
A future change will set up complete gpio and pinmux platform device
registration in device-tree files, via board-dt.c. When board-dt.c calls
into harmony/seaboard_pinmux_init(), this will cause a duplicate
registration of those platform devices, which will kernel boot failure.
To solve this,
Add AUXDATA so that Tegra GPIO and pinmux devices that are instantiated
from device-tree are named consistently with the static platform devices
in mach-tegra/devices.c. Note that the device-tree file tegra20.dtsi
already includes a node for the Tegra GPIO controller, whereas the node
for the
Add board-specific gpio node for Harmony and Seaboard. This lists the
GPIOs used by the board. Note that not all GPIOs that exist on the board
are listed; only those used by devices currently supported by device
tree.
Signed-off-by: Stephen Warren swar...@nvidia.com
---
Signed-off-by: Stephen Warren swar...@nvidia.com
---
drivers/gpio/gpio-tegra.c | 25 ++---
1 files changed, 14 insertions(+), 11 deletions(-)
diff --git a/drivers/gpio/gpio-tegra.c b/drivers/gpio/gpio-tegra.c
index df64536..4da4839 100644
--- a/drivers/gpio/gpio-tegra.c
+++
Signed-off-by: Stephen Warren swar...@nvidia.com
---
drivers/gpio/gpio-tegra.c | 31 +++
1 files changed, 31 insertions(+), 0 deletions(-)
diff --git a/drivers/gpio/gpio-tegra.c b/drivers/gpio/gpio-tegra.c
index 4da4839..923b413 100644
---
Signed-off-by: Stephen Warren swar...@nvidia.com
---
arch/arm/mach-tegra/pinmux.c | 21 +
1 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-tegra/pinmux.c b/arch/arm/mach-tegra/pinmux.c
index f80d507..05fa1a3 100644
---
Signed-off-by: Stephen Warren swar...@nvidia.com
---
arch/arm/mach-tegra/pinmux.c | 115 ++
1 files changed, 115 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-tegra/pinmux.c b/arch/arm/mach-tegra/pinmux.c
index 05fa1a3..33246c2 100644
---
Signed-off-by: Stephen Warren swar...@nvidia.com
---
arch/arm/mach-tegra/Makefile |1 -
arch/arm/mach-tegra/board-dt.c | 10 --
2 files changed, 0 insertions(+), 11 deletions(-)
diff --git a/arch/arm/mach-tegra/Makefile b/arch/arm/mach-tegra/Makefile
index f11b910..bab6544 100644
This reverts commit arm/tegra: Prevent duplicate gpio/pinmux pdev
registration with dt; board-dt.c no long calls harmony/
seaboard_pinmux_init(), so the workaround is no longer needed.
Signed-off-by: Stephen Warren swar...@nvidia.com
---
arch/arm/mach-tegra/board-harmony-pinmux.c |5 +
This series adds initial support for booting the MSM8660 via
devicetree. The target boots with a serial console, and no platform
data.
In order to test this with a devicetree boot, it is necessary to
include patches allowing the devicetree to be appended to the kernel,
and merge ATAG values into
Add devicetree support to the msm_serial driver. Clocks are still
queried by direct name from the driver until device tree clock support
is implemented.
Signed-off-by: David Brown dav...@codeaurora.org
---
.../devicetree/bindings/tty/serial/msm_serial.txt | 18 ++
Adds support for booting via device tree with a simple serial console.
Signed-off-by: David Brown dav...@codeaurora.org
---
arch/arm/boot/dts/msm8660-surf.dts | 24 +++
arch/arm/mach-msm/board-msm8x60.c | 58 +++
2 files changed, 75 insertions(+),
Device tree iomem resources are only accessible by index, and not by
name. The msm_serial devices always have either 1 or 2 iomem
resources, that are always in the same order. Convert the
platform_get_resource_byname into just platform_get_resource to
facilitate device tree conversion.
The MSM 8660 SURF development board contains a register-accessible
FPGA. By default, this FPGA configures the first UART in output-only
mode. On this target, reconfigure this FPGA to enable the UART to be
bidirectional.
Signed-off-by: David Brown dav...@codeaurora.org
---
32 matches
Mail list logo
