On Thu, Mar 21, 2013 at 04:33:05PM -0400, Rhyland Klein wrote:
Setup the compatible property so that when this device is registered
through device tree, it can match the expected compatiblity string
used in the tps65090 driver.
Signed-off-by: Rhyland Klein rkl...@nvidia.com
---
On Thu, Mar 28, 2013 at 05:35:15PM +0100, Philipp Zabel wrote:
The system reset controller (SRC) on i.MX51, i.MX53, and i.MX6q controls
reset lines to the GPU, VPU, IPU, and OpenVG IP modules.
The following patches add a simple API for devices to request being reset
by separate reset
There is a warning message that can't be printed because we test the
wrong variable.
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
diff --git a/drivers/mtd/nand/denali_dt.c b/drivers/mtd/nand/denali_dt.c
index 546f8cb..02988b0 100644
--- a/drivers/mtd/nand/denali_dt.c
+++
On Mon, Mar 25, 2013 at 12:57:56PM +0530, Mugunthan V N wrote:
am33xx_pinmux: pinmux@44e10800 {
pinctrl-names = default;
- pinctrl-0 = user_leds_s0;
+ pinctrl-0 = user_leds_s0 cpsw_s0;
Why do you add cpsw_s0 to the pinmux node? This should go into
-Original Message-
From: devicetree-discuss [mailto:devicetree-discuss-
bounces+hvaibhav=ti@lists.ozlabs.org] On Behalf Of Michal Bachraty
Sent: Thursday, March 28, 2013 11:02 PM
To: dri-de...@lists.freedesktop.org; devicetree-
disc...@lists.ozlabs.org
Cc: robdcl...@gmail.com;
On Thu, Mar 21, 2013 at 4:39 AM, Vinod Koul vinod.k...@intel.com wrote:
On Tue, Mar 05, 2013 at 02:55:31PM +0530, Padmavathi Venna wrote:
This patch register the dma controller with generic dma helpers only
in DT case. This also adds some extra error handling in the driver.
Signed-off-by:
On Wed, Mar 13, 2013 at 09:29:12PM +0800, Wei Yongjun wrote:
From: Wei Yongjun yongjun_...@trendmicro.com.cn
The variable bits_per_word is initialized but never used
otherwise, so remove the unused variable.
Applied, thanks.
signature.asc
Description: Digital signature
On Mon, Apr 1, 2013 at 7:31 AM, Hiremath, Vaibhav hvaib...@ti.com wrote:
-Original Message-
From: devicetree-discuss [mailto:devicetree-discuss-
bounces+hvaibhav=ti@lists.ozlabs.org] On Behalf Of Michal Bachraty
Sent: Thursday, March 28, 2013 11:02 PM
To:
This patch series adds support for DRM FIMD DT for Exynos4 DT Machines,
specifically for Exynos4412 SoC.
changes since v9:
- dropped the patch ARM: dts: Add lcd pinctrl node entries for
EXYNOS4412 SoC
as the gpios in the newly added nodes lcd_en and lcd_sync in this
patch
This patch adds a common FIMD device node for all Exynos4 SoCs.
Signed-off-by: Vikas Sajjan vikas.saj...@linaro.org
---
arch/arm/boot/dts/exynos4.dtsi | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4.dtsi b/arch/arm/boot/dts/exynos4.dtsi
index
This patch adds FIMD related nodes for the Origen Quad board.
Signed-off-by: Vikas Sajjan vikas.saj...@linaro.org
---
arch/arm/boot/dts/exynos4412-origen.dts | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4412-origen.dts
Add DT binding documentation for the FIMD IP block found in Samsung SoCs.
Signed-off-by: Vikas Sajjan vikas.saj...@linaro.org
---
.../devicetree/bindings/video/samsung-fimd.txt | 65
1 file changed, 65 insertions(+)
create mode 100644
Hi Javier
On Sat, 2013-03-30 at 14:18 +0100, Javier Martinez Canillas wrote:
A call to gpio_request() to enable the GPIO bank is needed before
using a GPIO as an IRQ source, otherwise accesses to the GPIO bank
registers fails making the kernel to hang.
Yes, that is exactly my problem here.
Vinod,
On 03/20/2013 11:36 AM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [130319 09:08]:
Vinod, Tony, Benoit,
On 02/26/2013 12:27 PM, Jon Hunter wrote:
If the device-tree blob is present during boot, then register the SDMA
controller with the device-tree DMA driver so that we can
of_get_mac_address() and of_get_phy_mode() are only provided if OF_NET
is configured. While most callers check for the define, not all do, and those
who do require #ifdef around the code. For those who don't, the missing check
can result in errors such as
arch/powerpc/sysdev/tsi108_dev.c:107:3:
On 04/01/2013 04:22 PM, Vikas Sajjan wrote:
This patch adds FIMD related nodes for the Origen Quad board.
Signed-off-by: Vikas Sajjanvikas.saj...@linaro.org
---
arch/arm/boot/dts/exynos4412-origen.dts | 21 +
1 file changed, 21 insertions(+)
diff --git
On 04/01/2013 01:19 PM, Guenter Roeck wrote:
of_get_mac_address() and of_get_phy_mode() are only provided if OF_NET
is configured. While most callers check for the define, not all do, and those
who do require #ifdef around the code. For those who don't, the missing check
can result in errors
On Mon, Apr 01, 2013 at 08:13:31AM -0500, Rob Herring wrote:
On Thu, Mar 21, 2013 at 4:39 AM, Vinod Koul vinod.k...@intel.com wrote:
On Tue, Mar 05, 2013 at 02:55:31PM +0530, Padmavathi Venna wrote:
This patch register the dma controller with generic dma helpers only
in DT case. This also
On Mon, Apr 01, 2013 at 12:48:26PM -0500, Jon Hunter wrote:
Vinod,
On 03/20/2013 11:36 AM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [130319 09:08]:
Vinod, Tony, Benoit,
On 02/26/2013 12:27 PM, Jon Hunter wrote:
If the device-tree blob is present during boot, then register
On Mon, Apr 01, 2013 at 01:44:24PM -0500, Rob Herring wrote:
On 04/01/2013 01:19 PM, Guenter Roeck wrote:
of_get_mac_address() and of_get_phy_mode() are only provided if OF_NET
is configured. While most callers check for the define, not all do, and
those
who do require #ifdef around the
On 04/01/2013 02:01 PM, Guenter Roeck wrote:
On Mon, Apr 01, 2013 at 01:44:24PM -0500, Rob Herring wrote:
On 04/01/2013 01:19 PM, Guenter Roeck wrote:
of_get_mac_address() and of_get_phy_mode() are only provided if OF_NET
is configured. While most callers check for the define, not all do, and
Just couple minor comments...
On 03/28/2013 06:43 AM, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without using phandle. To obtain a reference to the PHY
On Mon, Apr 1, 2013 at 6:41 PM, Christoph Fritz
chf.fr...@googlemail.com wrote:
Hi Javier
On Sat, 2013-03-30 at 14:18 +0100, Javier Martinez Canillas wrote:
A call to gpio_request() to enable the GPIO bank is needed before
using a GPIO as an IRQ source, otherwise accesses to the GPIO bank
Hi,
I am working on a thermal driver which needs to be able to read a
temperature threshold from a device tree property. The hardware supports
thresholds in the range -204.8 to +204.7 C in 0.1 C steps. I have found,
as I am sure others have as well, that dtc treats a '-' before an integer
in a
On 03/09/2013 02:15 PM, Tomasz Figa wrote:
This patch moves several for_each macros out of the #ifdef CONFIG_OF
block and adds inline stubs for functions used by these macros, compiled
conditionally when CONFIG_OF is not enabled.
This eliminates the need to explicitly check for CONFIG_OF in
On 01/04/13 08:56, Alexander Clouter wrote:
Currently there are two users of rtc-m48t86 (mach-ep93xx/ts72xx.c and
mach-orion5x/ts78xx-setup.c) and both just use {read,write}b against
a memory mapped region. As I am devicetree'ing the TS-7800, this
driver needs converting and thats what this
This series defines a common way for devicetree initialized
power_supplies to define their relationships between chargers and
supplicants.
This series adds a supplied_from array to complement the supplied_to
array and to allow supplies to define the list of supplies which
supply them.
Then once
This property is meant to be used in device nodes which represent
power_supply devices that wish to provide a list of supplies which
provide them power, such as a battery listing its chargers.
Signed-off-by: Rhyland Klein rkl...@nvidia.com
---
v2:
- no changes
v1:
- changed from RFC v2 - patch
This patch adds support for supplies to register a list of char *'s
which represent the list of supplies which supply them. This is the
opposite as the supplied_to list.
This change maintains support for supplied_to until all drivers which
make use of it already are converted.
Signed-off-by:
Adding support for supplied_from char * array. This is meant to store the
list of suppliers for a given supply, i.e. chargers for a battery. This
list can be populated through devicetree readily as well as passed
directly from the driver.
Signed-off-by: Rhyland Klein rkl...@nvidia.com
---
v2:
-
On 04/01/2013 03:08 PM, David Collins wrote:
Hi,
I am working on a thermal driver which needs to be able to read a
temperature threshold from a device tree property. The hardware supports
thresholds in the range -204.8 to +204.7 C in 0.1 C steps. I have found,
as I am sure others have as
On Tue, Apr 02, 2013 at 08:44:10AM +1100, Ryan Mallon wrote:
On 01/04/13 08:56, Alexander Clouter wrote:
Currently there are two users of rtc-m48t86 (mach-ep93xx/ts72xx.c and
mach-orion5x/ts78xx-setup.c) and both just use {read,write}b against
a memory mapped region. As I am devicetree'ing the
On 01/04/13 08:56, Alexander Clouter wrote:
This patch allows rtc-m48t86 to be used via devicetree.
Signed-off-by: Alexander Clouter a...@digriz.org.uk
---
.../devicetree/bindings/rtc/rtc-m48t86.txt | 17 ++
drivers/rtc/rtc-m48t86.c | 254
On 02/04/13 08:44, Ryan Mallon wrote:
On 01/04/13 08:56, Alexander Clouter wrote:
Currently there are two users of rtc-m48t86 (mach-ep93xx/ts72xx.c and
mach-orion5x/ts78xx-setup.c) and both just use {read,write}b against
a memory mapped region. As I am devicetree'ing the TS-7800, this
driver
On 03/28/2013 06:43 AM, Kishon Vijay Abraham I wrote:
diff --git a/Documentation/devicetree/bindings/phy/phy-bindings.txt
b/Documentation/devicetree/bindings/phy/phy-bindings.txt
new file mode 100644
index 000..35696b2
--- /dev/null
+++
On Tue, Apr 02, 2013 at 09:12:02AM +1100, Ryan Mallon wrote:
On 02/04/13 08:44, Ryan Mallon wrote:
On 01/04/13 08:56, Alexander Clouter wrote:
Currently there are two users of rtc-m48t86 (mach-ep93xx/ts72xx.c and
mach-orion5x/ts78xx-setup.c) and both just use {read,write}b against
a
On 04/01/2013 04:27 PM, Sylwester Nawrocki wrote:
On 03/28/2013 06:43 AM, Kishon Vijay Abraham I wrote:
diff --git a/Documentation/devicetree/bindings/phy/phy-bindings.txt
+example2:
+phys: phy {
+compatible = xxx;
+reg =...;
+.
+.
+phys =phys 1;
+.
+.
+};
The header for the rtc-m48t86 platform-data should be in
include/linux/platform_data.
Signed-off-by: Alexander Clouter a...@digriz.org.uk
---
arch/arm/mach-ep93xx/ts72xx.c |2 +-
arch/arm/mach-orion5x/ts78xx-setup.c |2 +-
Currently there are two users of rtc-m48t86 (mach-ep93xx/ts72xx.c and
mach-orion5x/ts78xx-setup.c) and both just use {read,write}b against
a memory mapped region. As I am devicetree'ing the TS-7800, this
driver needs converting and thats what this patchset does.
The patch does the following:
*
If platform_data is not defined (as before), then named memory io
ranges need to be defined (rtc_index and rtc_data). The driver
then maps those regions and uses them as the RTC index and data
addresses.
Does compile with the following warnings, I cannot see the codepath
affected myself:
The m48t86 has 114 bytes of user space available, so we can use this
space to detect for the presence of the RTC.
Signed-off-by: Alexander Clouter a...@digriz.org.uk
---
drivers/rtc/rtc-m48t86.c | 43 +++
1 file changed, 43 insertions(+)
diff --git
Remove platform_data hooks into rtc-m48t86 and use named resource regions.
Signed-off-by: Alexander Clouter a...@digriz.org.uk
---
arch/arm/mach-orion5x/ts78xx-setup.c | 78 --
1 file changed, 17 insertions(+), 61 deletions(-)
diff --git
Remove platform_data hooks into rtc-m48t86 and use named resource regions.
Signed-off-by: Alexander Clouter a...@digriz.org.uk
---
arch/arm/mach-ep93xx/ts72xx.c | 38 +++---
1 file changed, 7 insertions(+), 31 deletions(-)
diff --git
Add devicetree bindings (and documentation) for rtc-m48t86.
Signed-off-by: Alexander Clouter a...@digriz.org.uk
---
Documentation/devicetree/bindings/rtc/rtc-m48t86.txt | 17 +
drivers/rtc/rtc-m48t86.c | 12 ++--
2 files changed, 27
On 02/04/13 10:22, Alexander Clouter wrote:
If platform_data is not defined (as before), then named memory io
ranges need to be defined (rtc_index and rtc_data). The driver
then maps those regions and uses them as the RTC index and data
addresses.
Does compile with the following warnings,
On Tue, Apr 02, 2013 at 10:36:43AM +1100, Ryan Mallon wrote:
On 02/04/13 10:22, Alexander Clouter wrote:
If platform_data is not defined (as before), then named memory io
ranges need to be defined (rtc_index and rtc_data). The driver
then maps those regions and uses them as the RTC index and
On 04/01/2013 03:00 PM, Stephen Warren wrote:
On 04/01/2013 03:08 PM, David Collins wrote:
Hi,
I am working on a thermal driver which needs to be able to read a
temperature threshold from a device tree property. The hardware supports
thresholds in the range -204.8 to +204.7 C in 0.1 C
On 03/28/2013 12:12 AM, Lubomir Rintel wrote:
This adds a device tree binding for random number generator present on
Broadcom
BCM2835 SoC, used in Raspberry Pi and Roku 2 devices.
FYI, I intend to apply this patch to the bcm2835 tree whenever the RNG
driver itself is applied to the hw_random
Hi Vinod,
I apologies for the delayed reply. Last week I was out of station and
no access to mails. I will send another patch addressing your
comments.
Thanks
Padma
On Mon, Apr 1, 2013 at 11:51 PM, Vinod Koul vinod.k...@intel.com wrote:
On Mon, Apr 01, 2013 at 08:13:31AM -0500, Rob Herring
On 02/04/13 10:22, Alexander Clouter wrote:
If platform_data is not defined (as before), then named memory io
ranges need to be defined (rtc_index and rtc_data). The driver
then maps those regions and uses them as the RTC index and data
addresses.
Does compile with the following warnings,
On 02/04/13 10:42, Alexander Clouter wrote:
On Tue, Apr 02, 2013 at 10:36:43AM +1100, Ryan Mallon wrote:
On 02/04/13 10:22, Alexander Clouter wrote:
If platform_data is not defined (as before), then named memory io
ranges need to be defined (rtc_index and rtc_data). The driver
then maps
51 matches
Mail list logo
