Hi Daniel,
Nice job!
On Fri, Dec 14, 2012 at 7:36 AM, Daniel Mack zon...@gmail.com wrote:
This patch adds basic DT bindings for OMAP GPMC.
The actual peripherals are instantiated from child nodes within the GPMC
node, and the only type of device that is currently supported is NAND.
Code
These regulators are common to igep0020 and igep0030 boards
and are needed by smsc911x controller.
Cc: Benoît Cousson b-cous...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc: Enric Balletbo i Serra eballe...@gmail.com
Cc: Javier Martinez Canillas jav...@dowhile0.org
Signed-off-by: Ezequiel Garcia
Cc: Lior Amsalem al...@marvell.com
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc: Gregory CLEMENT gregory.clem...@free-electrons.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/configs/mvebu_defconfig |5 -
1 files changed, 4 insertions
Cc: Lior Amsalem al...@marvell.com
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc: Gregory CLEMENT gregory.clem...@free-electrons.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/boot/dts/armada-370-db.dts |8
1 files changed, 8
gregory.clem...@free-electrons.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/boot/dts/armada-370-xp.dtsi | 15 +++
arch/arm/boot/dts/armada-370.dtsi|9 +
arch/arm/boot/dts/armada-xp.dtsi | 17 +
arch/arm/mach-mvebu
Cc: Lior Amsalem al...@marvell.com
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc: Gregory CLEMENT gregory.clem...@free-electrons.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/boot/dts/armada-370-mirabox.dts |8
1 files changed, 8
Hi,
This small patch set enables USB support on Armada 370 and Armada XP platforms.
It's based on Jason Cooper's mvebu/dt branch.
Any comments or feedback are welcome.
Ezequiel Garcia (6):
arm: mvebu: Add support for USB host controllers in Armada 370/XP
arm: mvebu: Enable USB controllers
Cc: Lior Amsalem al...@marvell.com
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc: Gregory CLEMENT gregory.clem...@free-electrons.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts |9 +
1 files
Hi Florian,
On 01/15/2013 07:23 AM, Florian Fainelli wrote:
Le 01/15/13 10:54, Ezequiel Garcia a écrit :
diff --git a/arch/arm/mach-mvebu/Kconfig b/arch/arm/mach-mvebu/Kconfig
index 440b13e..5e4fcde 100644
--- a/arch/arm/mach-mvebu/Kconfig
+++ b/arch/arm/mach-mvebu/Kconfig
@@ -24,6 +24,7
Hi Arnd,
On 01/15/2013 10:07 AM, Arnd Bergmann wrote:
On Tuesday 15 January 2013, Ezequiel Garcia wrote:
Cc: Lior Amsalem al...@marvell.com
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc: Gregory CLEMENT gregory.clem...@free-electrons.com
Signed-off-by: Ezequiel Garcia
On Tue, Jan 15, 2013 at 3:03 PM, Tony Lindgren t...@atomide.com wrote:
* Daniel Mack zon...@gmail.com [130114 15:30]:
On Jan 15, 2013 2:06 AM, Tony Lindgren t...@atomide.com wrote:
* Ezequiel Garcia elezegar...@gmail.com [121223 13:49]:
On Fri, Dec 14, 2012 at 7:36 AM, Daniel Mack zon
Florian,
On 01/15/2013 04:54 PM, Florian Fainelli wrote:
On Tuesday 15 January 2013 06:59:57 Ezequiel Garcia wrote:
Hi,
This small patch set enables USB support on Armada 370 and Armada XP
platforms.
It's based on Jason Cooper's mvebu/dt branch.
Any comments or feedback are welcome.
I
Hi Nobuhiro,
On Tue, Jan 15, 2013 at 9:01 PM, Nobuhiro Iwamatsu iwama...@nigauri.org wrote:
Hi,
On Tue, Jan 15, 2013 at 6:54 PM, Ezequiel Garcia
ezequiel.gar...@free-electrons.com wrote:
Cc: Lior Amsalem al...@marvell.com
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc
Tony,
On Tue, Jan 15, 2013 at 3:03 PM, Tony Lindgren t...@atomide.com wrote:
* Daniel Mack zon...@gmail.com [130114 15:30]:
On Jan 15, 2013 2:06 AM, Tony Lindgren t...@atomide.com wrote:
* Ezequiel Garcia elezegar...@gmail.com [121223 13:49]:
On Fri, Dec 14, 2012 at 7:36 AM, Daniel Mack
On Fri, Jan 18, 2013 at 6:11 PM, Tony Lindgren t...@atomide.com wrote:
* Ezequiel Garcia elezegar...@gmail.com [130118 11:43]:
Tony,
On Tue, Jan 15, 2013 at 3:03 PM, Tony Lindgren t...@atomide.com wrote:
* Daniel Mack zon...@gmail.com [130114 15:30]:
On Jan 15, 2013 2:06 AM, Tony Lindgren
Bityutskiy artem.bityuts...@linux.intel.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
drivers/mtd/onenand/omap2.c |4 +++-
include/linux/platform_data/mtd-onenand-omap2.h |3 +++
2 files changed, 6 insertions(+), 1 deletions(-)
diff --git
gpmc_onenand_init() will be called from another driver's probe() function,
so drop the __init annotation, in order to prevent section mismatches.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/mach-omap2/gpmc-onenand.c |2 +-
1 files changed, 1 insertions
This patch adds device tree bindings for OMAP OneNAND devices.
Tested on an OMAP3 3430 IGEPv2 board.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
Changes from v1:
* Fix typo in Documentation/devicetree/bindings/mtd/gpmc-onenand.txt
.../devicetree/bindings/mtd/gpmc
Hi Mark,
On Mon, Jan 21, 2013 at 9:30 AM, Mark Rutland mark.rutl...@arm.com wrote:
[...]
diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c
index 01ce462..f7de9eb 100644
--- a/arch/arm/mach-omap2/gpmc.c
+++ b/arch/arm/mach-omap2/gpmc.c
@@ -39,6 +39,7 @@
#include
Hi Thomas and Gregory,
On Mon, Jan 21, 2013 at 11:07:10PM +0100, Gregory CLEMENT wrote:
On 01/21/2013 07:17 PM, Thomas Petazzoni wrote:
+ irq_set_percpu_devid(virq);
+ irq_set_chip_and_handler(virq, armada_370_xp_irq_chip,
+
On Mon, Jan 21, 2013 at 10:32 PM, Daniel Mack zon...@gmail.com wrote:
Hi Tony, Mark, Ezequiel,
Tony Lindgren t...@atomide.com wrote:
* Ezequiel Garcia elezegar...@gmail.com [130121 09:00]:
Hi Mark,
On Mon, Jan 21, 2013 at 9:30 AM, Mark Rutland mark.rutl...@arm.com
wrote:
[...]
diff
On Tue, Jan 22, 2013 at 3:27 PM, Tony Lindgren t...@atomide.com wrote:
* Ezequiel Garcia elezegar...@gmail.com [130122 10:17]:
On Mon, Jan 21, 2013 at 10:32 PM, Daniel Mack zon...@gmail.com wrote:
I'm currently far away from my computer and can't prepare a patch for
this, sorry. But I
: Gregory CLEMENT gregory.clem...@free-electrons.com
Tested-by: Nobuhiro Iwamatsu iwama...@nigauri.org
Tested-by: Florian Fainelli flor...@openwrt.org
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
Changes from v1:
* Squashed separate per-board patches into this one
Cc: Lior Amsalem al...@marvell.com
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc: Gregory CLEMENT gregory.clem...@free-electrons.com
Tested-by: Nobuhiro Iwamatsu iwama...@nigauri.org
Tested-by: Florian Fainelli flor...@openwrt.org
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free
Hi Nobuhiro,
On Wed, Jan 23, 2013 at 12:26 PM, Ezequiel Garcia
ezequiel.gar...@free-electrons.com wrote:
This patch activates every USB port provided by each SoC.
Except for Armada XP Openblocks AX3-4 board,
where we enable only the first two USB ports
until we have more information
Jason,
On Wed, Jan 23, 2013 at 12:26 PM, Ezequiel Garcia
ezequiel.gar...@free-electrons.com wrote:
The Armada 370 and Armada XP SoC has an Orion EHCI USB controller.
This patch adds support for this controller in Armada 370
and Armada XP SoC common device tree files.
Cc: Lior Amsalem al
Hi Thomas,
On Wed, Jan 23, 2013 at 3:03 PM, Thomas Petazzoni
thomas.petazz...@free-electrons.com wrote:
On Wed, 23 Jan 2013 14:04:42 -0300, Ezequiel Garcia wrote:
from the OpenBlocks AX3-4 board dts file, since you mentioned this
board uses that USB
port for a PCIe connector -- if I
Bityutskiy artem.bityuts...@linux.intel.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
drivers/mtd/onenand/omap2.c |4 +++-
include/linux/platform_data/mtd-onenand-omap2.h |3 +++
2 files changed, 6 insertions(+), 1 deletions(-)
diff --git
gpmc_onenand_init() will be called from another driver's probe() function,
so drop the __init annotation, in order to prevent section mismatches.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/mach-omap2/gpmc-onenand.c |2 +-
1 files changed, 1 insertions
Hi Mark,
First of all: thanks for reviewing.
On Fri, Jan 25, 2013 at 12:56 PM, Mark Rutland mark.rutl...@arm.com wrote:
Hi,
I have a couple more comments after looking though this a bit more thoroughly.
On Fri, Jan 25, 2013 at 12:23:11PM +, Ezequiel Garcia wrote:
This patch adds device
Hi Jason,
On Wed, Jan 23, 2013 at 2:40 PM, Jason Cooper ja...@lakedaemon.net wrote:
On Wed, Jan 23, 2013 at 02:06:12PM -0300, Ezequiel Garcia wrote:
Jason,
On Wed, Jan 23, 2013 at 12:26 PM, Ezequiel Garcia
ezequiel.gar...@free-electrons.com wrote:
The Armada 370 and Armada XP SoC has
-gp.dts | 101
2 files changed, 102 insertions(+)
create mode 100644 arch/arm/boot/dts/armada-xp-gp.dts
Tested-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
Regards,
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android
Cc: Gregory Clement gregory.clem...@free-electrons.com
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc: Lior Amsalem al...@marvell.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/configs/mvebu_defconfig |2 ++
1 files changed, 2 insertions(+), 0
...@marvell.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/boot/dts/armada-370-xp.dtsi | 22 ++
1 files changed, 22 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/armada-370-xp.dtsi
b/arch/arm/boot/dts/armada-370-xp.dtsi
index
Hi,
This patchset adds support for the SPI controller
available in Armada 370 and Armada XP SoC.
The patches are based in Jason Cooper's mvebu/dt branch.
Feel free to test and/or provide feedback.
Ezequiel Garcia (2):
ARM: mvebu: Update defconfig to select SPI support
ARM: mvebu: Add support
Jason,
On Mon, Feb 04, 2013 at 01:37:33PM -0500, Jason Cooper wrote:
This series looks good. just a few comments:
On Mon, Feb 04, 2013 at 01:51:20PM -0300, Ezequiel Garcia wrote:
Hi,
This patchset adds support for the SPI controller
available in Armada 370 and Armada XP SoC
Andrew,
On Mon, Feb 04, 2013 at 08:03:26PM +0100, Andrew Lunn wrote:
On Mon, Feb 04, 2013 at 01:51:20PM -0300, Ezequiel Garcia wrote:
Hi,
This patchset adds support for the SPI controller
available in Armada 370 and Armada XP SoC.
Hi Ezequiel
Do any of the boards we have
Jason,
On Mon, Feb 4, 2013 at 4:47 PM, Jason Cooper ja...@lakedaemon.net wrote:
Ezequiel,
On Mon, Feb 04, 2013 at 04:29:15PM -0300, Ezequiel Garcia wrote:
On Mon, Feb 04, 2013 at 01:37:33PM -0500, Jason Cooper wrote:
On Mon, Feb 04, 2013 at 01:51:20PM -0300, Ezequiel Garcia wrote
: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc: Lior Amsalem al...@marvell.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
This patch depends on:
1. Gregory's patch for Armada XP GP board:
arm: mvebu: support for the new Armada XP development board(DB-MV784MP-GP
On Tue, Feb 05, 2013 at 07:48:33AM -0500, Jason Cooper wrote:
Morning-ish Andrew,
On Tue, Feb 05, 2013 at 01:38:27PM +0100, Andrew Lunn wrote:
And don't forget to compile the SPI flash driver, CONFIG_MTD_M25P80=y
Maybe it makes sense to provide a patch to mvebu_defconfig to add
On Tue, Feb 05, 2013 at 06:07:05PM +0100, Thomas Petazzoni wrote:
Dear Gregory CLEMENT,
On Tue, 05 Feb 2013 17:20:02 +0100, Gregory CLEMENT wrote:
So that means we should enable the drivers for all the devices present
on all the boards?
Yes. For example my mvsdio patch set enables
Hi Gregory,
On Tue, Feb 05, 2013 at 09:17:02PM +0100, Gregory CLEMENT wrote:
On 02/05/2013 05:28 PM, Gregory CLEMENT wrote:
Hi Ezequiel,
On 02/05/2013 12:24 PM, Ezequiel Garcia wrote:
This patch adds an SPI master device node for Armada XP-GP board.
This master node is an SPI flash
: mvebu: i2c come back in defconfig
Feel free to test or provide any feedback!
Ezequiel Garcia (4):
arm: mvebu: Add support for SPI controller in Armada 370/XP
ARM: mvebu: Update defconfig to select SPI support
arm: mvebu: Add SPI flash on Armada XP-GP board
ARM: mvebu: Update defconfig
of the two.
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc: Lior Amsalem al...@marvell.com
Acked-by: Gregory Clement gregory.clem...@free-electrons.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
Changes from v1:
* Register offset must be 0x28 instead of 0x50
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc: Lior Amsalem al...@marvell.com
Acked-by: Gregory Clement gregory.clem...@free-electrons.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/configs/mvebu_defconfig |2 ++
1 files changed, 2 insertions
: Lior Amsalem al...@marvell.com
Tested-by: Gregory Clement gregory.clem...@free-electrons.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
Depends on Gregory's patch for Armada XP GP board:
arm: mvebu: support for the new Armada XP development board(DB-MV784MP-GP)
arch/arm
The Armada XP DB-MV784MP-GP board has an SPI flash device.
These options allow to access that device over MTD.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
Depends on patch: arm: mvebu: i2c come back in defconfig
arch/arm/configs/mvebu_defconfig |3 +++
1 files
(Adding mtd in Cc)
On Wed, Feb 06, 2013 at 07:54:31AM -0300, Ezequiel Garcia wrote:
Hi Gregory,
On Tue, Feb 05, 2013 at 09:17:02PM +0100, Gregory CLEMENT wrote:
On 02/05/2013 05:28 PM, Gregory CLEMENT wrote:
Hi Ezequiel,
On 02/05/2013 12:24 PM, Ezequiel Garcia wrote:
This patch
Hi Michal,
On Thu, Jan 10, 2013 at 12:40 PM, Michal Simek mon...@monstr.eu wrote:
Hi guys,
we want to add static memory controller driver for xilinx zynq to the
linux kernel. (It will go to drivers/memory/ folder)
Just need to clear dts fragment which describe it.
I'm working on a
On Tue, Feb 12, 2013 at 02:48:47PM +0100, Michal Simek wrote:
2013/2/12 Ezequiel Garcia elezegar...@gmail.com:
Hi Michal,
On Thu, Jan 10, 2013 at 12:40 PM, Michal Simek mon...@monstr.eu wrote:
Hi guys,
we want to add static memory controller driver for xilinx zynq to the
linux
On Wed, Feb 13, 2013 at 09:13:27AM -0600, Jon Hunter wrote:
On 02/13/2013 05:13 AM, Ezequiel Garcia wrote:
GPMC stands for General Purpose Memory Controller, and it's primarily
used to handle memories such as NOR, NAND, SRAM.
Note that this controller is also used to handle network
Hi Anil,
On Sat, Feb 16, 2013 at 05:08:27PM +0530, Anil Kumar wrote:
Add gpmc DT node.
Signed-off-by: Anil Kumar anilk...@gmail.com
---
:100644 100644 1acc261... 9f36531... March/arm/boot/dts/omap3.dtsi
arch/arm/boot/dts/omap3.dtsi | 11 +++
1 files changed, 11
Hi Jason,
On Sat, Feb 16, 2013 at 10:02:28AM -0500, Jason Cooper wrote:
On Wed, Feb 06, 2013 at 10:06:24AM -0300, Ezequiel Garcia wrote:
The Armada XP DB-MV784MP-GP board has an SPI flash device.
These options allow to access that device over MTD.
Signed-off-by: Ezequiel Garcia
Hi Jon,
On Tue, Feb 26, 2013 at 2:30 PM, Jon Hunter jon-hun...@ti.com wrote:
[...]
+ if (!of_property_read_u32(np, gpmc,bus-turnaround, val))
+ gpmc_t-bus_turnaround = val;
+
AFAIK, you don't need to test if the property is defined.
You can just read it straightforward,
On Fri, Mar 1, 2013 at 5:11 PM, Ezequiel Garcia elezegar...@gmail.com wrote:
Hi Jon,
On Tue, Feb 26, 2013 at 2:30 PM, Jon Hunter jon-hun...@ti.com wrote:
[...]
+ if (!of_property_read_u32(np, gpmc,bus-turnaround, val))
+ gpmc_t-bus_turnaround = val;
+
AFAIK, you don't
Hi Jon,
On Tue, Feb 26, 2013 at 2:30 PM, Jon Hunter jon-hun...@ti.com wrote:
[...]
+static int gpmc_probe_nor_child(struct platform_device *pdev,
+ struct device_node *child)
+{
+ struct gpmc_settings gpmc_s;
+ struct gpmc_timings gpmc_t;
+
Hi Jon,
On Tue, Feb 26, 2013 at 2:30 PM, Jon Hunter jon-hun...@ti.com wrote:
+
+Example:
+
+gpmc: gpmc@6e00 {
+ compatible = ti,omap3430-gpmc, simple-bus;
I'm concern about using simple-bus, and I'm not entirely sure this will work.
AFAIK, you can't correlate a parent-child
Hi Jon,
On Tue, Mar 5, 2013 at 2:30 PM, Jon Hunter jon-hun...@ti.com wrote:
This really highlights a weakness in the GPMC driver, particularly
for NOR, where the child device can only be probed once the parent
is probed. I don't see this as being DT specific issue, because
even on older OMAP
Jon,
On Tue, Mar 5, 2013 at 6:34 PM, Jon Hunter jon-hun...@ti.com wrote:
By the way, with this version you should remove simple-bus from your
gpmc node compatible strings. I now call of_platform_device_create() to
create the child device during the GPMC probe. I think that this is a
safer
On Wed, Mar 6, 2013 at 1:46 PM, Jon Hunter jon-hun...@ti.com wrote:
On 03/06/2013 05:58 AM, Ezequiel Garcia wrote:
I'll submit this driver by the end of this week, in case you want
to take a look at it.
Ok, but this is not for omap right?
No, this is a new driver for a memory controller
On Wed, Mar 6, 2013 at 1:54 PM, Ezequiel Garcia elezegar...@gmail.com wrote:
On Wed, Mar 6, 2013 at 1:46 PM, Jon Hunter jon-hun...@ti.com wrote:
On 03/06/2013 05:58 AM, Ezequiel Garcia wrote:
I'll submit this driver by the end of this week, in case you want
to take a look at it.
Ok
On Fri, Mar 8, 2013 at 10:25 PM, Javier Martinez Canillas
jav...@dowhile0.org wrote:
On Fri, Mar 8, 2013 at 10:41 PM, Jon Hunter jon-hun...@ti.com wrote:
Yes you are correct. In general, I have been trying to stay some-what
consistent with what hwmod was doing as this was being auto-generated
On Thu, Mar 14, 2013 at 12:50 PM, Jon Hunter jon-hun...@ti.com wrote:
Yes, I full agree with that as well. The size should be purely HW
related. So we should not take any assumption about the page size /
alignment.
Ok, what is best to use? The size from hwmod structures or the size from
the
Hi Jon,
On Fri, Mar 15, 2013 at 10:21:00AM -0500, Jon Hunter wrote:
The GPMC has wait-pin signals that can be assigned to a chip-select
to monitor the ready signal of an external device. Add a variable to
indicate the total number of wait-pins for a given device. This will
allow us to detect
Hi Jon,
I have some tiny nitpicks...
On Fri, Mar 15, 2013 at 10:21:08AM -0500, Jon Hunter wrote:
Adds a function to read the various GPMC chip-select settings from
device-tree and store them in the gpmc_settings structure.
Update the GPMC device-tree binding documentation to describe these
mode, burst settings, wait monitoring etc.
Therefore, to simplify the GPMC code and add device-tree support for
NOR, it was first necessary to consolidate how these settings are
programmed.
Series based upon Mark Jackson's patch [1] and Ezequiel Garcia GPMC
clean-up series [2]. Entire series
Thomas,
On Tue, Mar 26, 2013 at 05:52:15PM +0100, Thomas Petazzoni wrote:
This set of patches introduces Message Signaled Interrupt support in
the Marvell EBU PCIe driver. It has been successfully tested on the
Armada XP GP platform and the Armada 370 DB platform with an Intel
e1000e PCIe
On Wed, May 15, 2013 at 03:25:21PM +0200, Thomas Petazzoni wrote:
[..]
+
+static int __init mvebu_pcie_probe(struct platform_device *pdev)
+{
+ struct mvebu_pcie *pcie;
+ struct device_node *np = pdev-dev.of_node;
+ struct of_pci_range range;
+ struct of_pci_range_parser
In order to clean message printing, we replace pr_info with pr_fmt.
This is purely cosmetic change, with the sole purpose of making
the code a bit more readable.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
drivers/bus/mvebu-mbus.c | 8 +---
1 file changed, 5
From: Ezequiel Garcia ezequ...@free-electrons.com
This patchset introduces the MBus DT binding.
The MBus DT binding is in charge of several different tasks:
1. Allows the MBus driver to be probed through the Device Tree.
2. Allocates statically declared decoding windows, such as those
This patch adds static window allocation to the device tree binding.
Each first-child of the mbus-compatible node, with a suitable 'ranges'
property, declaring an address translation, will trigger an address
decoding window allocation.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free
programatically, whenever a decoding window is allocated.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
drivers/bus/mvebu-mbus.c | 177 ++-
1 file changed, 160 insertions(+), 17 deletions(-)
diff --git a/drivers/bus/mvebu-mbus.c b
thomas.petazz...@free-electrons.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
drivers/bus/mvebu-mbus.c | 47 ++-
1 file changed, 30 insertions(+), 17 deletions(-)
diff --git a/drivers/bus/mvebu-mbus.c b/drivers/bus/mvebu-mbus.c
thomas.petazz...@free-electrons.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
drivers/bus/mvebu-mbus.c | 36
include/linux/mbus.h | 1 +
2 files changed, 37 insertions(+)
diff --git a/drivers/bus/mvebu-mbus.c b/drivers/bus/mvebu
Now that the mbus device tree binding has been introduced, we can
switch over to it.
Also, and since the initialization of the mbus driver is quite
fundamental for the system to work properly, this patch adds a BUG()
in case mbus fails to initialize.
Signed-off-by: Ezequiel Garcia ezequiel.gar
behind the mbus, thus describing the
hardware accurately.
A translation entry has been added for the internal-regs mapping.
This can't be done in the common armada-370-xp.dtsi because A370
and AXP have different addressing width.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
In order to access the SoC BootROM, we need to declare a mapping
(through a ranges property). The mbus driver will use this property
to allocate a suitable address decoding window.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/boot/dts/armada-370.dtsi | 6
Now that mbus device tree binding has been introduced, remove the address
decoding window management from this driver.
A suitable 'ranges' entry should be added to the devbus-compatible node in
the device tree, as described by the mbus binding documentation.
Signed-off-by: Ezequiel Garcia
The address decoding window to access the BootROM should not be
allocated programatically, but instead declared in the device tree.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/mach-mvebu/platsmp.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/mach
Now that mbus has been added to the device tree, it's possible to
move the DeviceBus out of internal registers, placing it directly
below the mbus. This is a more accurate representation of the hardware.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/boot/dts
These properties are not needed so it's safe to remove them.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/boot/dts/armada-370.dtsi | 4
1 file changed, 4 deletions(-)
diff --git a/arch/arm/boot/dts/armada-370.dtsi
b/arch/arm/boot/dts/armada-370.dtsi
index
Now that mbus has been added to the device tree, it's possible to
move the PCIe nodes out of internal registers, placing it directly
below the mbus. This is a more accurate representation of the
hardware.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/boot/dts
Now that mbus has been added to the device tree, it's possible to
move the PCIe nodes out of internal registers, placing it directly
below the mbus. This is a more accurate representation of the
hardware.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/boot/dts
Hi Jason, Arnd:
Thanks for your reviews!
I agree with most of your suggestions so far. However, I'd like to discuss
one point before we move forward with the other (imo, less importants)
issues. See below.
On Fri, Jun 07, 2013 at 02:00:54PM -0600, Jason Gunthorpe wrote:
[...]
Is the ranges
On Sun, Jun 09, 2013 at 03:42:24PM +0200, Arnd Bergmann wrote:
On Saturday 08 June 2013 15:38:52 Ezequiel Garcia wrote:
On Fri, Jun 07, 2013 at 02:00:54PM -0600, Jason Gunthorpe wrote:
Right. I think we have two options here for laying the DT ranges.
1) This is the proposal implied
On Sat, Jun 08, 2013 at 07:45:06PM -0600, Jason Gunthorpe wrote:
On Sat, Jun 08, 2013 at 03:38:52PM -0300, Ezequiel Garcia wrote:
[...]
There are lots and lots of solutions using the pre-processor, please
take a look and find one that you feel works for you...
Ok, I will.
We can always
on my Kirkwood Openblocks A6 using the latest
branch orion-irqchip-for-v3.11-v4. Everything works fine so:
Tested-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
For patches 3 to 6 I'm wondering if there's any reason why the irqchip and
clocksource changes are not separated. I'm probably
Hi Arnd,
I have another question!
On Fri, Jun 07, 2013 at 09:01:44PM +0200, Arnd Bergmann wrote:
[...]
+Example:
+
+ soc {
+ compatible = marvell,armada370-mbus, simple-bus;
+ reg = 0xd002 0x100, 0xd0020180 0x20;
+ };
+
+** How does it work?
+
+The
Jason, Arnd:
On Sat, Jun 08, 2013 at 07:45:06PM -0600, Jason Gunthorpe wrote:
[...]
This is the mangling I was referring to. It needs to be the offset
into the target, it can't be something else.
I see both of you have explained this already, but I can't seem
to catch it yet.
Mind
Jason,
On Tue, Jun 11, 2013 at 03:50:23PM -0600, Jason Gunthorpe wrote:
On Tue, Jun 11, 2013 at 05:26:47PM +0200, Arnd Bergmann wrote:
That looks ok to me, yes. If you have just one device under some of the
nodes
however, I think it's easier use an empty ranges property and do
On Wed, Jun 12, 2013 at 10:45:55PM +0200, Arnd Bergmann wrote:
On Wednesday 12 June 2013, Grant Likely wrote:
I think we should have almost everything needed already to do this.
of_bus allows arbitrary mapping code to be used at any stage in the
translation. We might need to add some glue
On Wed, Jun 12, 2013 at 03:26:42PM -0600, Jason Gunthorpe wrote:
On Wed, Jun 12, 2013 at 06:12:22PM -0300, Ezequiel Garcia wrote:
[...]
This departs considerably from what I'm aiming right now.
Are you suggesting to not put *any* mapping in the mbus 'ranges' node in
the DT (other
: Introduce Marvell EBU Device Bus driver
Thanks a lot!
Ezequiel Garcia (12):
bus: mvebu-mbus: Factor out initialization details
bus: mvebu-mbus: Introduce device tree binding
bus: mvebu-mbus: Add static window allocation to the DT binding
ARM: mvebu: Initialize MBus using the DT binding
ARM
thomas.petazz...@free-electrons.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
drivers/bus/mvebu-mbus.c | 47 ++-
1 file changed, 30 insertions(+), 17 deletions(-)
diff --git a/drivers/bus/mvebu-mbus.c b/drivers/bus/mvebu-mbus.c
thomas.petazz...@free-electrons.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
drivers/bus/mvebu-mbus.c | 36
include/linux/mbus.h | 1 +
2 files changed, 37 insertions(+)
diff --git a/drivers/bus/mvebu-mbus.c b/drivers/bus/mvebu
Now that the mbus device tree binding has been introduced, we can
switch over to it.
Also, and since the initialization of the mbus driver is quite
fundamental for the system to work properly, this patch adds a BUG()
in case mbus fails to initialize.
Signed-off-by: Ezequiel Garcia ezequiel.gar
In order to access the SoC BootROM, we need to declare a mapping
(through a ranges property). The mbus driver will use this property
to allocate a suitable address decoding window.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/boot/dts/armada-370-xp.dtsi | 2
Now that mbus device tree binding has been introduced, remove the address
decoding window management from this driver.
A suitable 'ranges' entry should be added to the devbus-compatible node in
the device tree, as described by the mbus binding documentation.
Signed-off-by: Ezequiel Garcia
Now that mbus has been added to the device tree, it's possible to
move the DeviceBus out of internal registers, placing it directly
below the mbus. This is a more accurate representation of the hardware.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/boot/dts
behind the mbus, thus describing the
hardware accurately.
A translation entry has been added for the internal-regs mapping.
This can't be done in the common armada-370-xp.dtsi because A370
and AXP have different addressing width.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
1 - 100 of 242 matches
Mail list logo
