Add OMAP MMC related device tree data for OMAP5.
Signed-off-by: Balaji T K balaj...@ti.com
---
arch/arm/boot/dts/omap5-evm.dts | 31 +++
arch/arm/boot/dts/omap5.dtsi| 31 +++
2 files changed, 62 insertions(+), 0 deletions(-)
diff
* AnilKumar, Chimata anilku...@ti.com [120731 06:37]:
Hi Peter,
On Fri, Jul 27, 2012 at 14:40:52, Ujfalusi, Peter wrote:
Hi,
On 07/24/2012 06:45 PM, AnilKumar Ch wrote:
Adds basic pinctrl support for AM33XX family of devices. This patch
is based on the pinctrl-simple driver
Am Dienstag, 7. August 2012, 09:28:40 schrieb Praveen Paneri:
This driver uses usb_phy interface to interact with s3c-hsotg. Supports
phy_init and phy_shutdown functions to enable/disable phy. Tested with
smdk6410 and smdkv310. More SoCs can be brought under later.
Signed-off-by: Praveen
On Tuesday 07 August 2012, Balaji T K wrote:
Add OMAP MMC related device tree data for OMAP5.
Signed-off-by: Balaji T K balaj...@ti.com
---
Acked-by: Arnd Bergmann a...@arndb.de
___
devicetree-discuss mailing list
Sylwester Nawrocki wrote:
On 08/06/2012 08:27 AM, Shaik Ameer Basha wrote:
After all this discussion, I can see two possibilities here.
1] If Kukjin Kim is sure about G-Scaler remains unchanged, across all
the exynos5 series SoCs,
It is fine to go with the compatible string
Hi Vaibhav,
Thanks for the review.
On Mon, Aug 06, 2012 at 12:18:32, Hiremath, Vaibhav wrote:
On Sat, Aug 04, 2012 at 00:39:25, Marc Kleine-Budde wrote:
On 08/03/2012 08:32 AM, Hiremath, Vaibhav wrote:
On Thu, Aug 02, 2012 at 18:43:11, AnilKumar, Chimata wrote:
Add Runtime PM support to
* Rajendra Nayak rna...@ti.com [120730 06:17]:
vcxio, v2v1 and v1v8 are expected to be always on, update the dtsi
for twl6030 to reflect this.
commit '86f5fc' regulator: core: Mark all DT based boards as having
full constraints) caused these to be disabled at late boot causing
OMAP4 boards
On Tue, Aug 07, 2012 at 08:43:44AM +0300, Felipe Balbi wrote:
On Mon, Aug 06, 2012 at 04:42:14PM +0100, Mark Brown wrote:
It's good practice to have an explict compatible string even if the
default happens to work in order to avoid any name clashes.
of_i2c.c makes no use whatsoever of the
* Peter Ujfalusi peter.ujfal...@ti.com [120727 02:47]:
Hello,
I need to find a solution to control 2 bits in CONTROL_DEVCONF0 on OMAP2/3 for
McBSP1 CLKR/FSR signal routing.
In boards using McBSP1 we might need to change bit 3 and 4 based on the audio
setup (how the board has been wired).
Vaibhav,
Thanks for the review.
On Fri, Aug 03, 2012 at 11:58:41, Hiremath, Vaibhav wrote:
On 7/25/2012 5:53 PM, AnilKumar Ch wrote:
Add Bosch D_CAN controller device tree data to AM33XX dtsi file
by adding d_can device node with all the necessary parameters.
Signed-off-by:
Hello,
On 30.07.2012 09:22, Heiko Schocher wrote:
add OF support for the davinci nand controller.
Signed-off-by: Heiko Schocherh...@denx.de
Cc: davinci-linux-open-sou...@linux.davincidsp.com
Cc: linux-arm-ker...@lists.infradead.org
Cc: devicetree-discuss@lists.ozlabs.org
Cc:
Hello,
On 30.07.2012 09:21, Heiko Schocher wrote:
add of support for the davinci i2c driver.
Signed-off-by: Heiko Schocherh...@denx.de
Signed-off-by: Sekhar Norinsek...@ti.com
Cc: davinci-linux-open-sou...@linux.davincidsp.com
Cc: linux-arm-ker...@lists.infradead.org
Cc:
On 08/07/2012 09:51 AM, Timur Tabi wrote:
The mdio-mux driver scans all child mdio nodes, without regard to whether
the node is actually used. Some device trees include all possible
mdio-mux nodes and rely on the boot loader to disable those that are not
present, based on some run-time
David Daney wrote:
Although this will get the job done, I don't think it is the cleanest
approach.
Would it be better to create a new iterator
(for_each_available_child_of_node perhaps) that skips the unavailable
nodes? This seems like a general problem that is not restricted to mdio
On Aug 7, 2012, at 4:52 AM, Mark Brown wrote:
On Tue, Aug 07, 2012 at 08:43:44AM +0300, Felipe Balbi wrote:
On Mon, Aug 06, 2012 at 04:42:14PM +0100, Mark Brown wrote:
It's good practice to have an explict compatible string even if the
default happens to work in order to avoid any name
On 7/30/2012 12:52 PM, Heiko Schocher wrote:
add OF support for the davinci nand controller.
Signed-off-by: Heiko Schocher h...@denx.de
Acked-by: Sekhar Nori nsek...@ti.com
Thanks,
Sekhar
___
devicetree-discuss mailing list
On Mon, Aug 06, 2012 at 01:42:21PM -0600, Stephen Warren wrote:
On 07/26/2012 01:55 PM, Thierry Reding wrote:
This patch series adds support for device tree based probing of the PCIe
controller found on Tegra SoCs.
Thierry, I just tested all Tegra boards in v3.6-rc1, and noticed that
PCIe
Hi,
thanks for your review.
On 06.08.2012 12:45, AnilKumar, Chimata wrote:
On Sun, Aug 05, 2012 at 21:48:42, Daniel Mack wrote:
On 30.07.2012 09:36, Daniel Mack wrote:
This patch adds logic to parse lis3 properties from a device tree node
and store them in a freshly allocated
When a 'gpios' property defines multiple GPIO pins, is there any kind of
expectation on the endian order of those pins? For example, take this:
gpios = gpio0 0 0
gpio0 1 0;
If I write a value of 2 to this GPIO pair, should I expect a value of 1
to be written to pin 0
From: Mugunthan V N mugunthan...@ti.com
Date: Mon, 6 Aug 2012 20:35:56 +0530
This patch set adds support for device tree for Davinci MDIO driver and fixes
CPSW DT binding documentation to make it copy pastable to dts file.
This patch set is tested with the following git tree on AM335X Beagle
Add device tree files for VT8500, WM8505 and WM8650 SoC's and
reference boards.
Signed-off-by: Tony Prisk li...@prisktech.co.nz
---
arch/arm/boot/dts/vt8500.dtsi| 99 ++
arch/arm/boot/dts/vt8500_ref.dts | 31 ++
arch/arm/boot/dts/wm8505.dtsi| 125
Signed-off-by: Tony Prisk li...@prisktech.co.nz
---
drivers/tty/serial/vt8500_serial.c |7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/tty/serial/vt8500_serial.c
b/drivers/tty/serial/vt8500_serial.c
index 2be006f..a7f58c9 100644
--- a/drivers/tty/serial/vt8500_serial.c
+++
Add devicetree support for vt8500-ehci.
Convert vt8500-uhci to a generic non-pci platform-uhci with
device tree support.
Signed-off-by: Tony Prisk li...@prisktech.co.nz
---
drivers/usb/host/Kconfig |4 +-
drivers/usb/host/ehci-vt8500.c | 24 --
drivers/usb/host/uhci-hcd.c
Signed-off-by: Tony Prisk li...@prisktech.co.nz
---
drivers/rtc/rtc-vt8500.c |7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/rtc/rtc-vt8500.c b/drivers/rtc/rtc-vt8500.c
index 9e94fb1..7364564 100644
--- a/drivers/rtc/rtc-vt8500.c
+++ b/drivers/rtc/rtc-vt8500.c
@@ -23,6 +23,7
This patchset updates arch-vt8500 to devicetree and removes all the old-style
code. Support for WM8650 has also been added.
Example dts/dtsi files are given for the three currently supported models.
Major changes:
GPIO code has been converted to a platform_device and rewritten as WM8505
support
Bindings for gpio, interrupt controller, power management controller,
timer, realtime clock, serial uart, ehci and uhci controllers and
framebuffer controllers used on the arch-vt8500 platform.
Framebuffer binding also specifies a 'display' node which is required
for determining the lcd panel
Update vt8500-fb, wm8505-fb and wmt-ge-rops to support device
tree bindings.
Small change in wm8505-fb.c to support WM8650 framebuffer color
format.
Signed-off-by: Tony Prisk li...@prisktech.co.nz
---
drivers/video/Kconfig |6 +--
drivers/video/vt8500lcdfb.c | 77
Converted the existing arch-vt8500 gpio to a platform_device.
Added support for WM8505 and WM8650 GPIO controllers.
Signed-off-by: Tony Prisk li...@prisktech.co.nz
---
drivers/gpio/Kconfig |6 +
drivers/gpio/Makefile |1 +
drivers/gpio/gpio-vt8500.c | 318
Apologies for the formatting/style errors. Thought I had checkpatch'd these but
missed a few (especially the uhci patch).
All formatting errors returned by scripts/checkpatch.pl are now fixed locally.
Apologies again,
Tony P
___
devicetree-discuss
Hi Sebastian,
On Tue, Jul 31 2012, Sebastian Hesselbarth wrote:
This patch adds device tree support and binding documentiation for
sdhci-dove.
v2: extended documentation and removed second interrupt as it is marked
'reserved' in dove datasheet.
Signed-off-by: Sebastian Hesselbarth
From: Stephen Warren swar...@nvidia.com
dtc currently allows the contents of properties to be changed, and the
contents of nodes to be added to. There are situations where removing
properties or nodes may be useful. This change implements the following
syntax to do that:
/ {
Hi Mack,
No attachments please.
On Wed, Aug 08, 2012 at 00:19:01, Daniel Mack wrote:
Hi,
thanks for your review.
On 06.08.2012 12:45, AnilKumar, Chimata wrote:
On Sun, Aug 05, 2012 at 21:48:42, Daniel Mack wrote:
On 30.07.2012 09:36, Daniel Mack wrote:
This patch adds logic to parse
32 matches
Mail list logo
