Andrew,
On Sat, Jul 20, 2013 at 07:38:47PM +0200, Andrew Lunn wrote:
> On Sat, Jul 20, 2013 at 06:58:55PM +0200, Andrew Lunn wrote:
> > On Mon, Jul 15, 2013 at 11:57:29AM -0300, Ezequiel Garcia wrote:
> > > Here's the new MBus DT binding, implementing the changes proposed
Andrew,
On Sat, Jul 20, 2013 at 07:38:47PM +0200, Andrew Lunn wrote:
> On Sat, Jul 20, 2013 at 06:58:55PM +0200, Andrew Lunn wrote:
> > On Mon, Jul 15, 2013 at 11:57:29AM -0300, Ezequiel Garcia wrote:
> > > Here's the new MBus DT binding, implementing the changes proposed
Hi Grant, Arnd, Jason:
On Mon, Jul 15, 2013 at 11:57:29AM -0300, Ezequiel Garcia wrote:
> Here's the new MBus DT binding, implementing the changes proposed
> by Thomas when we discussed the previous patchset:
>
> http://www.spinics.net/lists/arm-kernel/msg257170.html
>
Gerlando,
On Tue, Jul 16, 2013 at 08:51:37PM +0200, Gerlando Falauto wrote:
[...]
> >
> > Also, speaking of "device bus" this nand node should be behind a devicebus
> > node.
> >
> > ranges = > internal-regs */
> > MBUS_ID(0x01, 0x2f) 0 0 0xf400 0x400>;
> >
Hi Gerlando,
On Wed, Jul 17, 2013 at 08:35:38AM +0200, Gerlando Falauto wrote:
> On 07/16/2013 02:56 PM, Ezequiel Garcia wrote:
> [...]
> > Also, speaking of "device bus" this nand node should be behind a devicebus
> > node.
> >
> &g
Andrew,
On Tue, Jul 16, 2013 at 04:04:15PM +0200, Andrew Lunn wrote:
> On Mon, Jul 15, 2013 at 08:32:38PM -0300, Ezequiel Garcia wrote:
> > Instead of accessing the RSTOUT register directly, this commit
> > adds a platform memory resource to map this register into the driver.
&
On Tue, Jul 16, 2013 at 09:44:22AM -0400, Jason Cooper wrote:
> On Tue, Jul 16, 2013 at 09:14:33AM -0300, Ezequiel Garcia wrote:
> > On the other side, I'm much interested in knowing if you are OK with
> > breaking the watchdog DT compatibility. If you NACK this, then I'
Hi Gerlando,
On Tue, Jul 16, 2013 at 11:37:30AM +0200, Gerlando Falauto wrote:
>
> apologies in advance for commenting on an already-merged patch.
Sure, no problem.
>
> On 06/18/2013 05:31 PM, Ezequiel Garcia wrote:
> > Although the internal register window size is 1
Hi Sebastian,
On Tue, Jul 16, 2013 at 09:48:56AM +0200, Sebastian Hesselbarth wrote:
>
> In the discussion about orion clocksource Russell was proposing a generic
> thread-safe write. That puts a single lock around all those writes. Of
> course, it will also blocked by totally unrelated thread-
Hi Thomas, Andrew:
Thanks for looking at this!
On Tue, Jul 16, 2013 at 09:31:01AM +0200, Andrew Lunn wrote:
> On Tue, Jul 16, 2013 at 09:20:59AM +0200, Thomas Petazzoni wrote:
> >
> > On Tue, 16 Jul 2013 08:59:52 +0200, Andrew Lunn wrote:
> >
> > > Maybe i'm missing something here. You are maki
With the introduction of the orion irqchip driver, now the BRIDGE_CAUSE
bit is cleared by it. There's no longer a need to do it in the watchdog
driver, so we can simply remove it.
Signed-off-by: Ezequiel Garcia
---
drivers/watchdog/orion_wdt.c | 7 ---
1 file changed, 7 deletions(-)
Now that the 'reg' property meaning has been changed,
this commit updates the deivce-tree binding documentation.
Signed-off-by: Ezequiel Garcia
---
Documentation/devicetree/bindings/watchdog/orion-wdt.txt | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/Doc
The mach/bridge-regs.h header is not needed anymore, so we can remove it.
This commit allows to use this driver on multiplatforms builds.
Signed-off-by: Ezequiel Garcia
---
drivers/watchdog/orion_wdt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/watchdog
This is a purely cosmetic commit: we replace hardcoded values that
representing bits by BIT(), which is slightly more readable.
Signed-off-by: Ezequiel Garcia
---
drivers/watchdog/orion_wdt.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/watchdog/orion_wdt.c b
The watchdog driver now needs two 'reg' property cells. The first one
is for the register containing the watchdog counter, while the second
one is for the RSTOUT register.
Signed-off-by: Ezequiel Garcia
---
arch/arm/boot/dts/kirkwood.dtsi | 3 ++-
1 file changed, 2 insertions(+),
Instead of accessing the RSTOUT register directly, this commit
adds a platform memory resource to map this register into the driver.
Note that by adding a required 2nd-cell for the reg property,
this change breaks the device-tree binding compatibility.
Signed-off-by: Ezequiel Garcia
---
arch
direct use of it. Note that this breaks the current device-tree binding
compatibility since it changes the meaning of the 'reg' property.
Signed-off-by: Ezequiel Garcia
---
arch/arm/mach-kirkwood/include/mach/bridge-regs.h | 1 +
arch/arm/mach-orion5x/include/mach/bridge-regs.h | 1 +
arc
Name this file to something a bit more judicious.
Signed-off-by: Ezequiel Garcia
---
Documentation/devicetree/bindings/watchdog/{marvel.txt => orion-wdt.txt} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename Documentation/devicetree/bindings/watchdog/{marvel.txt =>
orion-w
Add a header declaration to allow drivers (such as watchdog)
to access this exported API.
Signed-off-by: Ezequiel Garcia
---
include/linux/time-orion.h | 7 +++
1 file changed, 7 insertions(+)
create mode 100644 include/linux/time-orion.h
diff --git a/include/linux/time-orion.h b/include
The TIMER_CTRL register allows to control timer and watchdog counters,
so it's a register shared between the clocksource and the watchdog
drivers. In order to prevent race-conditions the clocksource driver
exposed a thread-safe API. Use the API.
Signed-off-by: Ezequiel Garcia
---
dr
27;m not sure how 'stable' the
Kirkwood DT is considered. So, given we're currently moving things around,
maybe there is still a chance to do this.
This patchset applies on top of Sebastian Hesselbarth's branch:
git://github.com/shesselba/linux-dove.git orion-irqchip-for-
From: Thomas Petazzoni
After replacing the MBus name-based by the new ID-based API
let's fix the general description of the driver at the beginning
of the file.
Signed-off-by: Thomas Petazzoni
---
drivers/bus/mvebu-mbus.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff -
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
---
arch/arm/boot/dts/armada-370-xp.dtsi
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
---
arch/arm
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
---
arch/arm/mach-mvebu/platsmp.c | 25 -
1 file changed, 24 insertions(+), 1 deletion(-)
diff --git a/arch
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
---
arch/arm/boot/dts/armada-370-db.dts | 3 ++-
arch/arm/boot/dts
From: Thomas Petazzoni
These structures were only different in the mapping tables.
Now that those tables have been removed, it doesn't make any sense
to keep different structures.
Signed-off-by: Thomas Petazzoni
---
drivers/bus/mvebu-mbus.c | 14 +++---
1 file changed, 3 insertions(+),
et ID and attribute. Since this depends on
the PCIe port, we split the ranges translation entries, to correspond
to each MBus window.
Signed-off-by: Thomas Petazzoni
Signed-off-by: Ezequiel Garcia
---
arch/arm/boot/dts/armada-370-mirabox.dts | 32 +-
arch/arm/boot/dts/armada-370-xp
akes all of them sit 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
---
arch/arm/b
Signed-off-by: Ezequiel Garcia
---
arch/arm/boot/dts/armada-370-db.dts | 2 +-
arch/arm/boot/dts/armada-370-mirabox.dts | 2 +-
arch/arm/boot/dts/armada-370-rd.dts | 2 +-
arch/arm/boot/dts/armada-370.dtsi| 2 +-
arch/arm/boot/dts/armada-xp
From: Thomas Petazzoni
The new device tree layout encodes the window's target ID and attribute
in the PCIe controller node's ranges property. This allows to parse
such entries to obtain such information and use the recently introduced
MBus API to create the windows, instead of using the current n
From: Thomas Petazzoni
Now that every user of the deprecated name-based API has been
converted to using the ID-based API, let's remove the former one.
Signed-off-by: Thomas Petazzoni
---
drivers/bus/mvebu-mbus.c | 38 --
include/linux/mbus.h | 5 -
From: Thomas Petazzoni
This tables were used together with the name-based MBus window
creation API. Since that's has been removed, we can also remove
the tables.
Signed-off-by: Thomas Petazzoni
---
drivers/bus/mvebu-mbus.c | 150 +++
1 file changed,
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
---
.../devicetre
.
Signed-off-by: Ezequiel Garcia
---
.../devicetree/bindings/bus/mvebu-mbus.txt | 14 +++
drivers/bus/mvebu-mbus.c | 49 ++
include/linux/mbus.h | 4 ++
3 files changed, 67 insertions(+)
diff --git a
From: Thomas Petazzoni
With the introduction of the ID based MBus API, it's better
to switch to use it instead of the current name based scheme.
This will allow to deprecate the name based API, once every
user is removed.
Signed-off-by: Thomas Petazzoni
---
arch/arm/mach-dove/common.c | 68 ++
From: Thomas Petazzoni
With the introduction of the ID based MBus API, it's better
to switch to use it instead of the current name based scheme.
This will allow to deprecate the name based API, once every
user is removed.
Signed-off-by: Thomas Petazzoni
---
arch/arm/mach-orion5x/common.c
zzoni
Signed-off-by: Ezequiel Garcia
---
drivers/bus/mvebu-mbus.c | 49
include/linux/mbus.h | 1 +
2 files changed, 50 insertions(+)
diff --git a/drivers/bus/mvebu-mbus.c b/drivers/bus/mvebu-mbus.c
index 1b17954..44a07c4 100644
--- a/driver
Signed-off-by: Ezequiel Garcia
---
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
index 827468a..1b17954 100644
--- a/drivers/bus/mvebu-mbus.c
+++ b
an
Signed-off-by: Ezequiel Garcia
---
drivers/memory/mvebu-devbus.c | 64 ++-
1 file changed, 2 insertions(+), 62 deletions(-)
diff --git a/drivers/memory/mvebu-devbus.c b/drivers/memory/mvebu-devbus.c
index 978e8e3..94c9248 100644
--- a/drivers/memory/mveb
From: Thomas Petazzoni
With the introduction of the ID based MBus API, it's better
to switch to use it instead of the current name based scheme.
This will allow to deprecate the name based API, once every
user is removed.
Signed-off-by: Thomas Petazzoni
---
arch/arm/mach-mv78xx0/pcie.c | 23 +
From: Thomas Petazzoni
We add an API to create MBus address decoding windows from the target
ID and attribute. This function will be used later and deprecate the
current name based scheme.
Signed-off-by: Thomas Petazzoni
---
drivers/bus/mvebu-mbus.c | 33 +
incl
};
};
internal-regs {
compatible = "simple-bus";
#address-cells = <1>;
#size-cells = <1>;
ranges = <0 MBUS_ID(0xf0, 0x01) 0 0x10>;
mbusc: mbus-controller@2 {
reg = &
From: Thomas Petazzoni
With the introduction of the ID based MBus API, it's better
to switch to use it instead of the current name based scheme.
This will allow to deprecate the name based API, once every
user is removed.
Signed-off-by: Thomas Petazzoni
---
arch/arm/mach-kirkwood/common.c | 1
On Tue, Jul 09, 2013 at 12:50:47PM -0600, Bjorn Helgaas wrote:
> On Tue, Jul 9, 2013 at 12:20 PM, Jason Cooper wrote:
> > On Tue, Jul 09, 2013 at 01:41:13PM -0300, Ezequiel Garcia wrote:
> >> From: Thomas Petazzoni
> >>
> >> The new device tree layout encodes
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
---
arch/arm
From: Thomas Petazzoni
We add an API to create MBus address decoding windows from the target
ID and attribute. This function will be used later and deprecate the
current name based scheme.
Signed-off-by: Thomas Petazzoni
---
drivers/bus/mvebu-mbus.c | 33 +
incl
From: Thomas Petazzoni
Now that every user of the deprecated name-based API has been
converted to using the ID-based API, let's remove the former one.
Signed-off-by: Thomas Petazzoni
---
drivers/bus/mvebu-mbus.c | 38 --
include/linux/mbus.h | 5 -
Signed-off-by: Ezequiel Garcia
---
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
index 827468a..1b17954 100644
--- a/drivers/bus/mvebu-mbus.c
+++ b
From: Thomas Petazzoni
These structures were only different in the mapping tables.
Now that those tables have been removed, it doesn't make any sense
to keep different structures.
Signed-off-by: Thomas Petazzoni
---
drivers/bus/mvebu-mbus.c | 14 +++---
1 file changed, 3 insertions(+),
Signed-off-by: Ezequiel Garcia
---
arch/arm/boot/dts/armada-370-db.dts | 2 +-
arch/arm/boot/dts/armada-370-mirabox.dts | 2 +-
arch/arm/boot/dts/armada-370-rd.dts | 2 +-
arch/arm/boot/dts/armada-370.dtsi| 2 +-
arch/arm/boot/dts/armada-xp
From: Thomas Petazzoni
With the introduction of the ID based MBus API, it's better
to switch to use it instead of the current name based scheme.
This will allow to deprecate the name based API, once every
user is removed.
Signed-off-by: Thomas Petazzoni
---
arch/arm/mach-mv78xx0/pcie.c | 23 +
From: Thomas Petazzoni
With the introduction of the ID based MBus API, it's better
to switch to use it instead of the current name based scheme.
This will allow to deprecate the name based API, once every
user is removed.
Signed-off-by: Thomas Petazzoni
---
arch/arm/mach-orion5x/common.c
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
---
.../devicetre
= <0>;
clocks = <&gateclk 9>;
status = "disabled";
};
};
internal-regs {
compatible = "simple-bus";
#address-cells = <1>;
#size-cells
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
---
arch/arm/boot/dts/armada-370-xp.dtsi
et ID and attribute. Since this depends on
the PCIe port, we split the ranges translation entries, to correspond
to each MBus window.
Signed-off-by: Thomas Petazzoni
Signed-off-by: Ezequiel Garcia
---
arch/arm/boot/dts/armada-370-mirabox.dts | 32 +-
arch/arm/boot/dts/armada-370-xp
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
---
arch/arm/boot/dts/armada-370-db.dts | 3 ++-
arch/arm/boot/dts
akes all of them sit 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
---
arch/arm/b
From: Thomas Petazzoni
After replacing the MBus name-based by the new ID-based API
let's fix the general description of the driver at the beginning
of the file.
Signed-off-by: Thomas Petazzoni
---
drivers/bus/mvebu-mbus.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff -
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
---
arch/arm/mach-mvebu/platsmp.c | 25 -
1 file changed, 24 insertions(+), 1 deletion(-)
diff --git a/arch
.
Signed-off-by: Ezequiel Garcia
---
.../devicetree/bindings/bus/mvebu-mbus.txt | 14 +++
drivers/bus/mvebu-mbus.c | 49 ++
include/linux/mbus.h | 4 ++
3 files changed, 67 insertions(+)
diff --git a
From: Thomas Petazzoni
This tables were used together with the name-based MBus window
creation API. Since that's has been removed, we can also remove
the tables.
Signed-off-by: Thomas Petazzoni
---
drivers/bus/mvebu-mbus.c | 150 +++
1 file changed,
From: Thomas Petazzoni
The new device tree layout encodes the window's target ID and attribute
in the PCIe controller node's ranges property. This allows to parse
such entries to obtain such information and use the recently introduced
MBus API to create the windows, instead of using the current n
zzoni
Signed-off-by: Ezequiel Garcia
---
drivers/bus/mvebu-mbus.c | 49
include/linux/mbus.h | 1 +
2 files changed, 50 insertions(+)
diff --git a/drivers/bus/mvebu-mbus.c b/drivers/bus/mvebu-mbus.c
index 1b17954..44a07c4 100644
--- a/driver
From: Thomas Petazzoni
With the introduction of the ID based MBus API, it's better
to switch to use it instead of the current name based scheme.
This will allow to deprecate the name based API, once every
user is removed.
Signed-off-by: Thomas Petazzoni
---
arch/arm/mach-dove/common.c | 68 ++
an
Signed-off-by: Ezequiel Garcia
---
drivers/memory/mvebu-devbus.c | 64 ++-
1 file changed, 2 insertions(+), 62 deletions(-)
diff --git a/drivers/memory/mvebu-devbus.c b/drivers/memory/mvebu-devbus.c
index 978e8e3..94c9248 100644
--- a/drivers/memory/mveb
From: Thomas Petazzoni
With the introduction of the ID based MBus API, it's better
to switch to use it instead of the current name based scheme.
This will allow to deprecate the name based API, once every
user is removed.
Signed-off-by: Thomas Petazzoni
---
arch/arm/mach-kirkwood/common.c | 1
On Mon, Jul 08, 2013 at 10:42:25AM -0600, Jason Gunthorpe wrote:
> On Sat, Jul 06, 2013 at 01:38:35AM +0200, Arnd Bergmann wrote:
> > On Saturday 06 July 2013, Thomas Petazzoni wrote:
> > > Arnd, Jason, if you could confirm that you both agree with this DT
> > > binding soon, Ezequiel and I would q
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
---
arch/arm/boot/dts/armada-370-db.dts | 3 ++-
arch/arm/boot/dts
akes all of them sit 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
---
arch/arm/b
et ID and attribute. Since this depends on
the PCIe port, we split the ranges translation entries, to correspond
to each MBus window.
Signed-off-by: Thomas Petazzoni
Signed-off-by: Ezequiel Garcia
---
arch/arm/boot/dts/armada-370-mirabox.dts | 32 +-
arch/arm/boot/dts/armada-370
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
---
arch/arm/boot/dts/armada-370-xp.dtsi
Signed-off-by: Ezequiel Garcia
---
arch/arm/boot/dts/armada-370-db.dts | 2 +-
arch/arm/boot/dts/armada-370-mirabox.dts | 2 +-
arch/arm/boot/dts/armada-370-rd.dts | 2 +-
arch/arm/boot/dts/armada-370.dtsi| 2 +-
arch/arm/boot/dts/armada-xp
From: Thomas Petazzoni
After replacing the MBus name-based by the new ID-based API
let's fix the general description of the driver at the beginning
of the file.
Signed-off-by: Thomas Petazzoni
---
drivers/bus/mvebu-mbus.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff -
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
---
arch/arm/mach-mvebu/platsmp.c | 25 -
1 file changed, 24 insertions(+), 1 deletion(-)
diff --git a/arch
From: Thomas Petazzoni
These structures were only different in the mapping tables.
Now that those tables have been removed, it doesn't make any sense
to keep different structures.
Signed-off-by: Thomas Petazzoni
---
drivers/bus/mvebu-mbus.c | 14 +++---
1 file changed, 3 insertions(+),
From: Thomas Petazzoni
This tables were used together with the name-based MBus window
creation API. Since that's has been removed, we can also remove
the tables.
Signed-off-by: Thomas Petazzoni
---
drivers/bus/mvebu-mbus.c | 150 +++
1 file changed,
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
---
arch/arm
From: Thomas Petazzoni
The new device tree layout encodes the window's target ID and attribute
in the PCIe controller node's ranges property. This allows to parse
such entries to obtain such information and use the recently introduced
MBus API to create the windows, instead of using the current n
From: Thomas Petazzoni
Now that every user of the deprecated name-based API has been
converted to using the ID-based API, let's remove the former one.
Signed-off-by: Thomas Petazzoni
---
drivers/bus/mvebu-mbus.c | 38 --
include/linux/mbus.h | 5 -
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
---
.../devicetre
zzoni
Signed-off-by: Ezequiel Garcia
---
drivers/bus/mvebu-mbus.c | 49
include/linux/mbus.h | 1 +
2 files changed, 50 insertions(+)
diff --git a/drivers/bus/mvebu-mbus.c b/drivers/bus/mvebu-mbus.c
index 1b17954..44a07c4 100644
--- a/driver
Signed-off-by: Ezequiel Garcia
---
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
index 827468a..1b17954 100644
--- a/drivers/bus/mvebu-mbus.c
+++ b
From: Thomas Petazzoni
With the introduction of the ID based MBus API, it's better
to switch to use it instead of the current name based scheme.
This will allow to deprecate the name based API, once every
user is removed.
Signed-off-by: Thomas Petazzoni
---
arch/arm/mach-dove/common.c | 68 ++
From: Thomas Petazzoni
With the introduction of the ID based MBus API, it's better
to switch to use it instead of the current name based scheme.
This will allow to deprecate the name based API, once every
user is removed.
Signed-off-by: Thomas Petazzoni
---
arch/arm/mach-orion5x/common.c
From: Thomas Petazzoni
With the introduction of the ID based MBus API, it's better
to switch to use it instead of the current name based scheme.
This will allow to deprecate the name based API, once every
user is removed.
Signed-off-by: Thomas Petazzoni
---
arch/arm/mach-mv78xx0/pcie.c | 23 +
From: Thomas Petazzoni
We add an API to create MBus address decoding windows from the target
ID and attribute. This function will be used later and deprecate the
current name based scheme.
Signed-off-by: Thomas Petazzoni
---
drivers/bus/mvebu-mbus.c | 33 +
incl
an
Signed-off-by: Ezequiel Garcia
---
drivers/memory/mvebu-devbus.c | 64 ++-
1 file changed, 2 insertions(+), 62 deletions(-)
diff --git a/drivers/memory/mvebu-devbus.c b/drivers/memory/mvebu-devbus.c
index 978e8e3..94c9248 100644
--- a/drivers/memory/mveb
From: Thomas Petazzoni
With the introduction of the ID based MBus API, it's better
to switch to use it instead of the current name based scheme.
This will allow to deprecate the name based API, once every
user is removed.
Signed-off-by: Thomas Petazzoni
---
arch/arm/mach-kirkwood/common.c | 1
y allocated decoding window are defined in the same way.
I'd like to see this binding accepted more or less soon, so if the current
proposal is not accepted it'll be great to hear some hints on how to move
forward.
This series applies on top of today's linux-next. I will rebase it on v
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
---
arch/arm/boot/dts/armada-370-mirabox.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
---
arch/arm/boot/dts/armada-xp-db.dts
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
---
arch/arm/boot/dts/armada-370-db.dts | 3 ++-
arch/arm/boot/dts
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
---
arch/arm/boot/dts/armada-370-xp.dtsi
akes all of them sit 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
---
arch/arm/b
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
---
arch/arm
Signed-off-by: Ezequiel Garcia
---
arch/arm/boot/dts/armada-370-db.dts | 2 +-
arch/arm/boot/dts/armada-370-mirabox.dts | 2 +-
arch/arm/boot/dts/armada-370-rd.dts | 2 +-
arch/arm/boot/dts/armada-370.dtsi| 2 +-
arch/arm/boot/dts/armada-xp
ned-off-by: Ezequiel Garcia
---
drivers/memory/mvebu-devbus.c | 64 ++-
1 file changed, 2 insertions(+), 62 deletions(-)
diff --git a/drivers/memory/mvebu-devbus.c b/drivers/memory/mvebu-devbus.c
index 978e8e3..94c9248 100644
--- a/drivers/memory/mvebu-devb
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
---
arch/arm/mach-mvebu/platsmp.c | 25 -
1 file changed, 24 insertions(+), 1 deletion(-)
diff --git a/arch
1 - 100 of 261 matches
Mail list logo
