On Sat, Jun 29, 2013 at 1:43 AM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Rob,
Are you ok with phys_addr_t since your concern was about rest
of the memory specific bits of the device-tree code use u64 ?
No. I still think it should be u64 for same reasons I said originally.
+1
+1
On Fri, Jun 28, 2013 at 04:50:32PM +0200, Markus Pargmann wrote:
Hi,
This series adds some device nodes for imx27 and board files for Phytec
phyCARD-S SOM and RDK. It is based on shawn's branch imx/dt.
Looks good to me.
Acked-by: Sascha Hauer s.ha...@pengutronix.de
Sascha
--
Pengutronix
Hi,
On Friday 28 June 2013 03:41 PM, Sylwester Nawrocki wrote:
On 06/28/2013 10:17 AM, Hui Wang wrote:
On 06/26/2013 11:02 PM, Sylwester Nawrocki wrote:
Add a PHY provider driver for the Samsung S5P/Exynos SoC MIPI CSI-2
receiver and MIPI DSI transmitter DPHYs.
Signed-off-by: Sylwester
Hi,
On Friday 28 June 2013 12:45 PM, Jingoo Han wrote:
Add a PHY provider driver for the Samsung Exynos SoC DP PHY.
Signed-off-by: Jingoo Han jg1@samsung.com
---
.../phy/samsung,exynos5250-dp-video-phy.txt|7 ++
drivers/phy/Kconfig|8 ++
On Friday 28 June 2013 09:13:38 Stephen Warren wrote:
On 06/27/2013 12:26 PM, Marc Dietrich wrote:
Hi,
(CC'ing linux-tegra)
I'm puzzling for some time now to find a binding for a mfd device. So
let's
start with something I think I have learned already, let's describe the
hardware.
See the previous version of this patchset for further context:
http://www.spinics.net/lists/arm-kernel/msg253342.html
This is a new proposal, in an attempt to fix some obscurities in
the previous MBus DT binding proposal.
In the current proposal we have now required a 'controller' property
to
This patch adds the most fundamental device-tree initialization.
We only introduce what's required to be able to probe the mvebu-mbus
driver from the DT. Follow-up patches will extend the device tree binding,
allowing to describe static address decoding windows.
Signed-off-by: Thomas Petazzoni
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
We introduce a common initialization function mvebu_mbus_common_init()
that will be used by both legacy and device-tree initialization code.
This patch is an intermediate step, which will allow to introduce the
DT binding for this driver in a less intrusive way.
Signed-off-by: Thomas Petazzoni
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 | 25 -
1 file changed, 24
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
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 +-
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
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.
Cc: Greg Kroah-Hartman
The Armada 370/XP SoC family has a completely configurable address
space handled by the MBus controller.
This patch introduces the device tree layout of MBus, making the
'soc' node as mbus-compatible.
Since every peripheral/controller is a child of this 'soc' node,
this makes all of them sit
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
---
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-db.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
---
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
---
Hi,
On 06/29/2013 10:57 AM, Kishon Vijay Abraham I wrote:
On Friday 28 June 2013 03:41 PM, Sylwester Nawrocki wrote:
On 06/28/2013 10:17 AM, Hui Wang wrote:
On 06/26/2013 11:02 PM, Sylwester Nawrocki wrote:
Add a PHY provider driver for the Samsung S5P/Exynos SoC MIPI CSI-2
receiver and MIPI
On Sat, Jun 29, 2013 at 04:04:09PM -0300, Ezequiel Garcia wrote:
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
On Mon, Jun 24, 2013 at 1:54 PM, Michal Simek mon...@monstr.eu wrote:
I commented your comment on v1, and said I think you can support
both bindings.
in 2/6 you have applied that dual support for this driver
and that's why please add this binding description to your repo
because it reflects
On 28 June 2013 17:05, Mark Brown broo...@kernel.org wrote:
On Tue, Jun 25, 2013 at 11:56:12AM +0530, Sachin Kamat wrote:
There is no change in the bindings, but just a correction in the
documentation to reflect the
implementation. Earlier when Samsung platforms did not have pinctrl
driver,
22 matches
Mail list logo
