On Friday 11 October 2013 12:23 PM, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Friday 11 October 2013 12:00 PM, Nishanth Menon wrote:
>> On Fri, Oct 11, 2013 at 1:13 AM, Kishon Vijay Abraham I
>> wrote:
>>>
regulator-boot-on indicates that PMIC enables it by default as part of
OTP or s
Hi,
On Friday 11 October 2013 12:00 PM, Nishanth Menon wrote:
> On Fri, Oct 11, 2013 at 1:13 AM, Kishon Vijay Abraham I wrote:
>>
>>> regulator-boot-on indicates that PMIC enables it by default as part of
>>> OTP or some internal behavior -> Looking at the measurements done on
>>> uEVM and OTP in
On Tuesday, October 08, 2013 8:45 PM, Yuvaraj Kumar wrote:
> On Fri, Oct 4, 2013 at 6:03 AM, Jingoo Han wrote:
> > On Thursday, October 03, 2013 8:32 PM, Bartlomiej Zolnierkiewicz wrote:
> >> On Tuesday, October 01, 2013 12:03:01 PM Yuvaraj Kumar C D wrote:
> >> > Exynos5250 contains one Synopsys
On Fri, Oct 11, 2013 at 1:13 AM, Kishon Vijay Abraham I wrote:
>
>> regulator-boot-on indicates that PMIC enables it by default as part of
>> OTP or some internal behavior -> Looking at the measurements done on
>> uEVM and OTP information -> regulator-boot-on should be kept here.
>
> No. Actually
On Thursday 10 October 2013 06:41 PM, Laxman Dewangan wrote:
> On Thursday 10 October 2013 06:07 PM, Kishon Vijay Abraham I wrote:
>> The Palmas device contains only a USB VBUS-ID detector, so added a
>> compatible type *ti,palmas-usb-vid*. Didn't remove the existing compatible
>> types for backwar
On Thursday 10 October 2013 07:49 PM, Nishanth Menon wrote:
> On 16:19-20131010, Kishon Vijay Abraham I wrote:
>> smps10 should be enabled only in the case of host mode. So stop
>> doing always_on, boot_on from smps10_out1. The driver will enable it in host
>> mode.
>&g
On 10/10/13 09:30, Michal Simek wrote:
> s/op/pdev/ in xilinxfb_of_probe().
> No functional chagnes.
>
> Signed-off-by: Michal Simek
> ---
> Changes in v3: None
> Changes in v2: None
>
> drivers/video/xilinxfb.c | 18 +-
> 1 file changed, 9 insertions(+), 9 deletions(-)
Thanks,
On 10/10/2013 03:07 PM, Matt Porter wrote:
On 10/10/2013 01:57 PM, Paul Zimmerman wrote:
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Thursday, October 10, 2013 10:46 AM
On Thu, Oct 10, 2013 at 12:54:40PM -0400, Matt Porter wrote:
On 10/10/2013 11:29 AM, Felipe Balbi wrote:
On Mon, Oct 07,
Thanks for your review.
See my reply inline
> -Original Message-
> From: Mark Rutland [mailto:mark.rutl...@arm.com]
> Sent: 2013年10月10日 星期四 18:04
> To: Tang Yuantian-B29983
> Cc: ga...@kernel.crashing.org; linuxppc-...@lists.ozlabs.org;
> devicetree@vger.kernel.org; Li Yang-Leo-R58472
> Su
Signed-off-by: Jingchang Lu
---
arch/arm/boot/dts/vf610.dtsi | 49 +
include/dt-bindings/dma/vf610-edma.h | 103 +++
2 files changed, 152 insertions(+)
create mode 100644 include/dt-bindings/dma/vf610-edma.h
diff --git a/arch/arm/boot/dts
Signed-off-by: Jingchang Lu
---
arch/arm/mach-imx/clk-vf610.c | 5 +
include/dt-bindings/clock/vf610-clock.h | 6 +-
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mach-imx/clk-vf610.c b/arch/arm/mach-imx/clk-vf610.c
index b169a39..29f88a2 100644
--- a/a
[ CCed devicetree@vger.kernel.org as this involves DT compatibility strings ]
On Thu, Oct 10, 2013 at 11:08:03PM +0400, Valentine Barshak wrote:
> RCAR Gen2 SoC has a different phy which is not compatible with
> the older H1/M1 versions. This adds OF/platform device table
> and PHY initialization
>> +config PINCTRL_CAPRI
>> + bool "Broadcom Capri pinctrl driver"
>> + select PINMUX
>> + select PINCONF
>> + help
>> + Say Y here to support Broadcom Capri pinctrl driver, which is used
>> for
>> + the BCM281xx SoC family, including BCM11130, BCM11140, BCM
On Thu, Oct 10, 2013 at 03:24:46PM -0700, Andrew Morton wrote:
> On Wed, 9 Oct 2013 17:59:21 +0530 Laxman Dewangan
> wrote:
> > +config RTC_DRV_AS3722
> > + tristate "ams AS3722 RTC driver"
> > + depends on MFD_AS3722
> ... the rtc patch depends on an mfd patch, so everyone ends up sitting
On Thu, Oct 10, 2013 at 3:22 PM, Stephen Warren wrote:
> On 10/10/2013 02:58 PM, Alexandre Courbot wrote:
>> On Wed, Oct 9, 2013 at 4:47 PM, Olof Johansson wrote:
>>> On Fri, Oct 4, 2013 at 9:37 AM, Alexandre Courbot
>>> wrote:
> ...
>>> But do we really need to panic here? It's a PITA to debug
This patch adds the internal panel timings to the exynos5250-snow board
dts file.
Signed-off-by: Sean Paul
---
v2: No difference
v3: Added status = "okay"
arch/arm/boot/dts/exynos5250-snow.dts | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5250-
This patch adds a drm_bridge driver for the PTN3460 DisplayPort to LVDS
bridge chip.
Signed-off-by: Sean Paul
---
v2:
- Changed header definition to static inline
- Changed dt node name to lvds-bridge
v3: No changes
.../devicetree/bindings/drm/bridge/ptn3460.txt | 27 ++
This patch adds the dp-controller node to the exynos5250-snow board dts
file.
Signed-off-by: Sean Paul
---
v2: Added dp-controller address to node (rebased on linux-next)
v3: Added status = "okay"
arch/arm/boot/dts/exynos5250-snow.dts | 13 +
1 file changed, 13 insertions(+)
diff
This patch adds code to look for the ptn3460 in the device tree file on
exynos initialization. If ptn node is found, the driver will initialize
the ptn3460 driver and skip creating a DP connector (since the bridge
driver will register its own connector).
Signed-off-by: Sean Paul
---
v2:
This patch adds a node for the ptn3460 DP-LVDS chip in the
exynos5250-snow board dts file.
Signed-off-by: Sean Paul
---
v2: Changed node name to lvds-bridge
v3: No changes
arch/arm/boot/dts/exynos5250-snow.dts | 19 +++
1 file changed, 19 insertions(+)
diff --git a/arch/arm/bo
This set adds some missing devicetree nodes to the exynos5250-snow file as well
as adds a drm_bridge driver for the ptn3460 DP-LVDS chip. This chip is used in
the exynos5250-snow board.
Sean
Sean Paul (5):
ARM: dts: Add fimd display-timings for exynos5250-snow
ARM: dts: Add dp-controller node
On Thu, Oct 10, 2013 at 3:22 PM, Stephen Warren wrote:
> On 10/10/2013 02:58 PM, Alexandre Courbot wrote:
>> On Wed, Oct 9, 2013 at 4:47 PM, Olof Johansson wrote:
>>> On Fri, Oct 4, 2013 at 9:37 AM, Alexandre Courbot
>>> wrote:
> ...
>>> But do we really need to panic here? It's a PITA to debug
On Wed, 9 Oct 2013 17:59:21 +0530 Laxman Dewangan wrote:
> The ams AS3722 is a compact system PMU suitable for mobile phones,
> tablets etc.
>
> Add a driver to support accessing the RTC found on the ams AS3722
> PMIC using RTC framework.
I hate these patchsets, because ...
> index 9654aa3..d8
On Thu, Oct 10, 2013 at 11:19:14PM +0300, Aaro Koskinen wrote:
> On Thu, Oct 10, 2013 at 10:02:36PM +0200, Sebastian Reichel wrote:
> > P.S.: You can get a mainline kernel status matrix for the Nokia
> > N900 on this page: http://elinux.org/N900
>
> Thanks for summary,
You're welcome.
> an
On 10/10/2013 02:58 PM, Alexandre Courbot wrote:
> On Wed, Oct 9, 2013 at 4:47 PM, Olof Johansson wrote:
>> On Fri, Oct 4, 2013 at 9:37 AM, Alexandre Courbot
>> wrote:
...
>> But do we really need to panic here? It's a PITA to debug since it'll
>> be a very early panic. I'd rather have the syste
Looks like at least Igep, Zoom and EVM boards can use a
common file for the GPMC connected smsc911x.
Signed-off-by: Tony Lindgren
---
arch/arm/boot/dts/omap-gpmc-smsc911x.dtsi | 52 +
arch/arm/boot/dts/omap3-igep0020.dts | 45 +
2 file
We now have pretty decent device tree based support for
zoom platforms. It's not complete, but basics work for
me so adding more features should be quite trivial.
Looks like also 3630 sdp is zoom based, and looking
at it's board file should also be trivial to support
with the device tree based boo
Looks like the main difference between the TMDSEVM3530 and
TMDSEVM3730 is just the omap processor:
http://www.ti.com/tool/tmdsevm3530
http://www.ti.com/tool/tmdsevm3730
So let's add a common file for the EVMs, and fix the description
for the omap3-evm.dst as that's clearly for the TMDSEVM3530
sin
Just initialize things using the bootloader timings like
we've been doing for the legacy booting too. It should be
possible to patch in the GPMC timings for the based on the
TL16CP743C/TL16C754C manual at:
http://www.ti.com/lit/ds/slls644g/slls644g.pdf
Signed-off-by: Tony Lindgren
---
arch/arm/
I've tested serial, MMC, smsc911x and wl12xx on zoom3. As my
omap is an early ES revision, I have not been able to test
off-idle on this one. But anyways, I'd say we have enough
device tree support for the zoom to be able to drop the
board-zoom files. Patches are welcome to add further features
to
I've tested the serial, MMC, smsc911x, wl12xx, and off-idle support
with the pinctrl patches, so it probably works better than the
board-*.c files ever did. Also the board-omap3evm.c file is broken
for the DSS, and has been for a while. Patches are welcome to fix
it in this .dts file, let's just dr
As the wl12xx bindings are still pending, this way we can
get things working for omap3 evm and zoom platforms.
Signed-off-by: Tony Lindgren
---
arch/arm/mach-omap2/pdata-quirks.c | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/mach-omap2/pdata-quirks.c
b/arch/arm/ma
We now have pretty decent support with the device tree
based booting. Patches to add more features are welcome.
Signed-off-by: Tony Lindgren
---
arch/arm/mach-omap2/Kconfig |6
arch/arm/mach-omap2/Makefile |1
arch/arm/mach-omap2/board-omap3evm.c | 756 ---
Hi all,
Now that we have the remaining omap3 PM related wake-up
events mostly resolved, it's time to start making omap3
to be device tree only.
These are the boards that I'm using for testing in my
rack setup, so I've verified that the basic features work
well enough for me so we can make them de
AM33XX device family also supports hwspinlocks. The IP
is identical to that of OMAP4/OMAP5, except for the
number of locks.
Signed-off-by: Suman Anna
---
drivers/hwspinlock/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwspinlock/Kconfig b/drivers/hwspinlock
The hwspinlock_device structure is used for registering a bank of
locks with the driver core. The structure already contains the
necessary members to identify the bank of locks. The core does not
maintain the hwspinlock_devices itself, but maintains only a radix
tree for all the registered locks. A
Hi,
This is an updated series addressing the review comments from the
v2 series. The hwmod patches have been dropped from the repost
as per Paul's request, they have already been queued.
The series is tested on top of v3.12-rc4 + Benoit's 3.13 DTS branch and
Tero's clock series, along with the qu
HwSpinlock IP is present only on OMAP4 and other newer SoCs,
which are all device-tree boot only. This patch adds the
base support for parsing the DT nodes, and removes the code
dealing with the traditional platform device instantiation.
Signed-off-by: Suman Anna
---
.../devicetree/bindings/hwlo
Add the hwspinlock device tree node for AM33xx family
of SoCs.
Signed-off-by: Suman Anna
---
arch/arm/boot/dts/am33xx.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 8692490..49dfb86 100644
--- a/arch/arm/boot/dts
This patch adds the necessary documentation and OF helpers to
represent a hwlock device and use/request locks in a device-tree
build.
All the platform-specific hwlock driver implementations need the
number of locks and associated base id for registering the locks
present within the device with the
The number of hwspinlocks are determined based on the value read
from the IP block's SYSSTATUS register. However, the module may
not be enabled and clocked, and the read may result in a bus error.
This particular issue is seen rather easily on AM33XX, since the
module wakeup is software controlled
Add the hwspinlock device tree node for OMAP5 SoCs.
Signed-off-by: Suman Anna
---
arch/arm/boot/dts/omap5.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index 86295d2..2a98a59 100644
--- a/arch/arm/boot/dts/omap5.dtsi
++
Add the hwspinlock device tree node for OMAP4 family
of SoCs.
Signed-off-by: Suman Anna
---
arch/arm/boot/dts/omap4.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 45708e1..74db751 100644
--- a/arch/arm/boot/dts/oma
Alexandre Courbot writes:
> On Wed, Oct 9, 2013 at 4:47 PM, Olof Johansson wrote:
>> On Fri, Oct 4, 2013 at 9:37 AM, Alexandre Courbot
>> wrote:
[...]
>>> +static inline void register_trusted_foundations(
>>> + struct trusted_foundations_platform_data
>>> *p
On Wed, Oct 9, 2013 at 4:47 PM, Olof Johansson wrote:
> On Fri, Oct 4, 2013 at 9:37 AM, Alexandre Courbot wrote:
>> Trusted Foundations is a TrustZone-based secure monitor for ARM that
>> can be invoked using the same SMC-based API on all supported
>> platforms. This patch adds initial basic supp
On Mon, 2013-10-07 at 10:58 +0900, Cho KyongHo wrote:
> Patch written by Antonios Motakis :
>
> IOMMU groups are expected by certain users of the IOMMU API,
> e.g. VFIO. Since each device is behind its own System MMU, we
> can allocate a new IOMMU group for each device.
>
> Reviewd-by: Cho KyongH
On 10/09/2013 08:01 AM, Linus Walleij wrote:
> On Wed, Oct 9, 2013 at 3:28 PM, Christian Ruppert
> wrote:
>> On Wed, Oct 09, 2013 at 01:58:35PM +0200, Linus Walleij wrote:
>>> On Tue, Oct 8, 2013 at 2:25 PM, Christian Ruppert
>>> wrote:
...
>> Obviously, a driver (no matter for which OS) must be
On 10/09/2013 05:58 AM, Linus Walleij wrote:
> On Tue, Oct 8, 2013 at 2:25 PM, Christian Ruppert
> wrote:
>> This patch adds the infrastructure required to register non-linear gpio
>> ranges through gpiolib and the standard GPIO device tree bindings.
...
>> +Example:
>> +
>> + gpio_pio_i: gp
Hi Mark,
>>
>>> On Fri, Sep 27, 2013 at 05:06:38PM +0100, Kumar Gala wrote:
On Sep 17, 2013, at 2:30 PM, Suman Anna wrote:
> HwSpinlock IP is present only on OMAP4 and other newer SoCs,
> which are all device-tree boot only. This patch adds the
> base support for parsing
On Thu, Oct 10, 2013 at 10:02:36PM +0200, Sebastian Reichel wrote:
> P.S.: You can get a mainline kernel status matrix for the Nokia
> N900 on this page: http://elinux.org/N900
Thanks for summary, and the above page looks very useful. I wonder
would it make sense to add also N9/N950 there (s
On Thu, Oct 10, 2013 at 09:28:01PM +0300, Aaro Koskinen wrote:
> On Thu, Oct 10, 2013 at 07:21:30PM +0200, Sebastian Reichel wrote:
> > Any issues with this or any other suggestions how to proceed?
>
> Maybe you could provide some brief instructions/description of how this
> was tested?
Sure. I u
Hi,
On Fri, Oct 11, 2013 at 12:44:52AM +0530, Lokesh Vutla wrote:
> This patch series add nodes for l2-cache-controller, EDMA, mailbox,
> mmc, sham, and updates the properties for cpsw, i2c0, matrix-keypad.
>
> These patches are applied on top of Benoit's for_3.13/dts branch
> git://git.kernel.o
This patch series add nodes for l2-cache-controller, EDMA, mailbox, mmc, sham,
and updates the properties for cpsw, i2c0, matrix-keypad.
These patches are applied on top of Benoit's for_3.13/dts branch
git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git
for_3.13/dts
Testing
From: Mugunthan V N
-> Adding pinmux for cpsw, i2c0.
-> Enabling the modules that are present in AM4372 EPOS EVM
These modules are tested on AM4372 EPOS EVM.
Signed-off-by: Lokesh Vutla
Signed-off-by: Sourav Poddar
Signed-off-by: Mugunthan V N
---
arch/arm/boot/dts/am43x-epos-evm.dts | 168
Populate nodes for l2-cache-controller, EDMA, mailbox,
mmc, sham.
And also updating dt properties for epwmss, aes, des.
Few nodes are taken from a different tree that are added by
Suman Anna (Mailbox)
Balaji T K (MMC)
Mugunthan V N (Pinmux, Ethernet)
Signed-off-by: Lokesh Vutla
---
arch/arm
On 10/10/2013 01:57 PM, Paul Zimmerman wrote:
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Thursday, October 10, 2013 10:46 AM
On Thu, Oct 10, 2013 at 12:54:40PM -0400, Matt Porter wrote:
On 10/10/2013 11:29 AM, Felipe Balbi wrote:
On Mon, Oct 07, 2013 at 06:12:29AM -0400, Matt Porter wrote:
On 10/10/2013 11:47 AM, Tony Lindgren wrote:
> * Nishanth Menon [131010 09:53]:
>> Do not reset GPIO1 at boot-up because GPIO 7 in GPIO1 block is used on
>> OMAP4460 PandaBoard-ES to select voltage register in TPS62361 which
>> supplies VDD_MPU.
>>
>> Without this, OMAP4460 PandaBoard-ES boards fa
Hi,
On Thu, Oct 10, 2013 at 06:14:19PM +, Paul Zimmerman wrote:
> > From: Felipe Balbi [mailto:ba...@ti.com]
> > Sent: Thursday, October 10, 2013 11:07 AM
> >
> > On Thu, Oct 10, 2013 at 05:57:54PM +, Paul Zimmerman wrote:
> > > > From: Felipe Balbi [mailto:ba...@ti.com]
> > > > Sent: Thu
Hi,
On Thu, Oct 10, 2013 at 07:21:30PM +0200, Sebastian Reichel wrote:
> Any issues with this or any other suggestions how to proceed?
Maybe you could provide some brief instructions/description of how this
was tested?
Thanks,
A.
--
To unsubscribe from this list: send the line "unsubscribe devi
> From: Felipe Balbi [mailto:ba...@ti.com]
> Sent: Thursday, October 10, 2013 11:07 AM
>
> On Thu, Oct 10, 2013 at 05:57:54PM +, Paul Zimmerman wrote:
> > > From: Felipe Balbi [mailto:ba...@ti.com]
> > > Sent: Thursday, October 10, 2013 10:46 AM
> > >
> > > On Thu, Oct 10, 2013 at 12:54:40PM -
Hi,
On Thu, Oct 10, 2013 at 05:57:54PM +, Paul Zimmerman wrote:
> > From: Felipe Balbi [mailto:ba...@ti.com]
> > Sent: Thursday, October 10, 2013 10:46 AM
> >
> > On Thu, Oct 10, 2013 at 12:54:40PM -0400, Matt Porter wrote:
> > > On 10/10/2013 11:29 AM, Felipe Balbi wrote:
> > > >On Mon, Oct
> From: Felipe Balbi [mailto:ba...@ti.com]
> Sent: Thursday, October 10, 2013 10:46 AM
>
> On Thu, Oct 10, 2013 at 12:54:40PM -0400, Matt Porter wrote:
> > On 10/10/2013 11:29 AM, Felipe Balbi wrote:
> > >On Mon, Oct 07, 2013 at 06:12:29AM -0400, Matt Porter wrote:
> > >>Extend dwc2 binding with a
>This should *all* be using generic pin config.
>
>For the devicetree side of this, read:
>Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
>
>Your driver should also be selecting GENERIC_PINCONF in
>drivers/pinctrl/Kconfig so you use the generic pinconf
>library.
>
>Read
>include/lin
Hi,
On Thu, Oct 10, 2013 at 12:54:40PM -0400, Matt Porter wrote:
> On 10/10/2013 11:29 AM, Felipe Balbi wrote:
> >On Mon, Oct 07, 2013 at 06:12:29AM -0400, Matt Porter wrote:
> >>Extend dwc2 binding with an optional utmi phy width property.
> >>Enable the s3c-hsotg.c driver to use standard dwc2 bi
On Thu, Oct 10, 2013 at 05:51:00PM +0100, Mark Rutland wrote:
> On Thu, Oct 10, 2013 at 12:10:53PM +0100, Chanwoo Choi wrote:
> > Turn on ramp control of buck2/3/4.
> Ok, but why does this need to be in the dt?
Ramp control is a hardware system integration decision which people
working with regu
* Sebastian Reichel [131010 10:30]:
> Hi,
>
> On Tue, Oct 08, 2013 at 10:28:15AM -0700, Tony Lindgren wrote:
> > * Sebastian Reichel [131006 13:36]:
> > > Here is the third round of the OMAP SSI driver patches.
> >
> > Thanks for updating these, they look good to me now:
> >
> > Acked-by: Tony
On 10/10/2013 07:59 PM, Mark Rutland wrote:
>> No, they're not actually of much practical use to us at the minute but
>> it was generally felt better to include the information and not use it
>> so that if someone does come up with a use for them then the trees for
>> deployed systems already have
Hi,
On Tue, Oct 08, 2013 at 10:28:15AM -0700, Tony Lindgren wrote:
> * Sebastian Reichel [131006 13:36]:
> > Here is the third round of the OMAP SSI driver patches.
>
> Thanks for updating these, they look good to me now:
>
> Acked-by: Tony Lindgren
Ok. I guess it's time to check how this get
Signed-off-by: Soren Brinkmann
---
This is kind of optional since it does not have any effect due to the changed
default in 1/2.
v2:
- no change
arch/arm/boot/dts/zynq-7000.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/zynq-7000.dtsi b/arch/arm/boot/dts/zynq-7000.
In some use cases Zynq's FPGA clocks are used as static clock
generators for IP in the FPGA part of the SOC for which no Linux driver
exists and would control those clocks. To avoid automatic
gating of these clocks in such cases a new property - fclk-enable - is
added to the clock controller's DT d
On Tue, Oct 08, 2013 at 01:46:41AM +0100, Mark Brown wrote:
> On Mon, Oct 07, 2013 at 10:47:18PM +0100, Mark Rutland wrote:
> > On Thu, Sep 26, 2013 at 08:18:28PM +0100, Jyri Sarha wrote:
>
> > > - interrupts : Interrupt number for McASP
>
> > The device also seems to be able to generate multipl
On 10/08/2013 06:12 AM, Thierry Reding wrote:
> On Sat, Sep 21, 2013 at 12:19:33PM -0700, Mike Dunn wrote:
>> This patch adds device tree support to the PXA's PWM driver. Nothing
>> needs to be extracted from the device tree node by the PWM device.
>> Client devices need only specify the period; t
On 10/10/2013 11:29 AM, Felipe Balbi wrote:
On Mon, Oct 07, 2013 at 06:12:29AM -0400, Matt Porter wrote:
Extend dwc2 binding with an optional utmi phy width property.
Enable the s3c-hsotg.c driver to use standard dwc2 binding
and enable configuration of the UTMI phy width based on the
property.
On Thu, Oct 10, 2013 at 12:10:53PM +0100, Chanwoo Choi wrote:
> On 10/10/2013 07:28 PM, Mark Rutland wrote:
> > On Thu, Oct 10, 2013 at 02:41:35AM +0100, Chanwoo Choi wrote:
> >> This patch parse 'buck[2-4]_ramp_enable and buck_ramp_delay' platform data
> >> from dts file.
> >
> > Why?
> >
> > Wh
* Nishanth Menon [131010 09:53]:
> Do not reset GPIO1 at boot-up because GPIO 7 in GPIO1 block is used on
> OMAP4460 PandaBoard-ES to select voltage register in TPS62361 which
> supplies VDD_MPU.
>
> Without this, OMAP4460 PandaBoard-ES boards fail to boot-up because
> MPU voltage switches over t
Do not reset GPIO1 at boot-up because GPIO 7 in GPIO1 block is used on
OMAP4460 PandaBoard-ES to select voltage register in TPS62361 which
supplies VDD_MPU.
Without this, OMAP4460 PandaBoard-ES boards fail to boot-up because
MPU voltage switches over to VSET0 voltage value (boot voltage) which
is
On Thu, Oct 10, 2013 at 09:39:04AM +, Lu Jingchang-B35083 wrote:
> Hi, Vinod,
>
> Could you please help review this patch? Could it be merged into your next
> tree?
> Thanks!
Where is the patch 1 & 2 of the series, I dont sem to find it.
Also I need ACK from one of the DT maintainers on t
This augments the core machine code for the Integrator platforms
to get their references to the core module device nodes by
using compatible strings instead of predefined node names
and rename the CP syscon node to be simply "syscon".
Reported-by: Mark Rutland
Signed-off-by: Linus Walleij
---
D
* Linus Walleij [131010 08:40]:
> On Thu, Oct 10, 2013 at 4:35 PM, Roger Quadros wrote:
> > On 10/10/2013 05:04 PM, Linus Walleij wrote:
>
> >> As an innocent bystander who has no clue what the _reconfigure_io_chain()
> >> is about can you tell me what this is all about?
> >
> > The OMAP SoC has
* Tony Lindgren [131010 09:09]:
> * Roger Quadros [131010 06:32]:
> >
> > I tried testing this with the USB EHCI driver, but I'm not getting wake up
> > interrupts
> > while the system is still running and only the EHCI controller is runtime
> > suspended.
> >
> > It seems we need to somehow
* Linus Walleij [131010 09:19]:
> On Thu, Oct 10, 2013 at 6:00 PM, Tony Lindgren wrote:
> > * Roger Quadros [131010 06:32]:
> >>
> >> I tried testing this with the USB EHCI driver, but I'm not getting wake up
> >> interrupts
> >> while the system is still running and only the EHCI controller is
On Thu, Oct 10, 2013 at 6:00 PM, Tony Lindgren wrote:
> * Roger Quadros [131010 06:32]:
>>
>> I tried testing this with the USB EHCI driver, but I'm not getting wake up
>> interrupts
>> while the system is still running and only the EHCI controller is runtime
>> suspended.
>>
>> It seems we nee
On Thu, Oct 10, 2013 at 07:21:40AM +0200, Michal Simek wrote:
> On 10/09/2013 05:25 PM, Sören Brinkmann wrote:
> > On Tue, Oct 08, 2013 at 04:38:17PM +0100, Mark Rutland wrote:
> >> On Tue, Oct 08, 2013 at 03:36:11PM +0100, Soren Brinkmann wrote:
> >>> In some use cases Zynq's FPGA clocks are used
On Thu, Oct 10, 2013 at 04:24:38PM +0100, Jens Renner wrote:
> Add device tree binding documentation for the driver in spi/spi-xilinx.c.
>
> Signed-off-by: Jens Renner
> ---
> diff --git a/Documentation/devicetree/bindings/spi/spi-xilinx.txt
> b/Documentation/devicetree/bindings/spi/spi-xilinx.t
On Thu, Oct 10, 2013 at 10:23 AM, Joel Fernandes wrote:
> I see a function of that name already exists. I guess you can leave your patch
> as is then and not have to do this.
Can I consider that as an Acked-by :) ?
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line "unsubscr
* Roger Quadros [131010 06:32]:
>
> I tried testing this with the USB EHCI driver, but I'm not getting wake up
> interrupts
> while the system is still running and only the EHCI controller is runtime
> suspended.
>
> It seems we need to somehow call _reconfigure_io_chain() to update the daisy
On 10/10/2013 10:45 AM, Nishanth Menon wrote:
> On Thu, Oct 10, 2013 at 10:23 AM, Joel Fernandes wrote:
>> I see a function of that name already exists. I guess you can leave your
>> patch
>> as is then and not have to do this.
>
>
> Can I consider that as an Acked-by :) ?
Yes, sure, for this
Hi,
On Wed, Oct 02, 2013 at 10:52:06AM +0200, Andreas Larsson wrote:
> >hmm, there are two ways to look at this.
> >
> >a) we have KERN_CONT to continue printing messages
> >b) you might prefer using debugfs and seq_puts() for dumping large(-ish)
> >amounts of debugging data ;-)
>
> I just found
On Thu, Oct 10, 2013 at 11:25 AM, Laxman Dewangan wrote:
> On Tuesday 08 October 2013 05:46 PM, Linus Walleij wrote:
>> On Wed, Oct 2, 2013 at 5:50 PM, Laxman Dewangan
>> wrote:
>>> Changes from V4:
>>> - Drop separate DT binding document as it is moved to mfd/as3722.txt.
>>
>> As mentioned I am
On Mon, Oct 07, 2013 at 04:28:13PM +0300, Roger Quadros wrote:
> The generic PHY framewrok expects different properties than the
> old USB PHY framework. Supply those properties.
>
> Fixes USB OTG port on GAT04 and N900 after the Generic PHY framework was
> merged in greg/usb-next. [1]
>
> [1] -
On Mon, Oct 07, 2013 at 01:46:50PM +0300, Roger Quadros wrote:
> The generic PHY framewrok expects different properties than the
> old USB PHY framework. Supply those properties.
>
> Fixes USB OTG port on beagle after the Generic PHY framework was
> merged in greg/usb-next. [1]
>
> [1] - https://
Hi,
On Mon, Oct 07, 2013 at 06:12:30AM -0400, Matt Porter wrote:
> Broadcom BCM281xx parts have a PHY control block that
> operates in conjunction with the DWC2 USB OTG. This driver
> exposes an API that allows control of power/reset for a
> connected USB PHY.
>
> Signed-off-by: Matt Porter
> Re
On Thu, Oct 10, 2013 at 4:35 PM, Roger Quadros wrote:
> On 10/10/2013 05:04 PM, Linus Walleij wrote:
>> As an innocent bystander who has no clue what the _reconfigure_io_chain()
>> is about can you tell me what this is all about?
>
> The OMAP SoC has a mechanism to monitor and wakeup from a low p
On Mon, Oct 07, 2013 at 06:12:29AM -0400, Matt Porter wrote:
> Extend dwc2 binding with an optional utmi phy width property.
> Enable the s3c-hsotg.c driver to use standard dwc2 binding
> and enable configuration of the UTMI phy width based on the
> property.
>
> Signed-off-by: Matt Porter
> Revi
Add device tree binding documentation for the driver in spi/spi-xilinx.c.
Signed-off-by: Jens Renner
---
diff --git a/Documentation/devicetree/bindings/spi/spi-xilinx.txt
b/Documentation/devicetree/bindings/spi/spi-xilinx.txt
new file mode 100644
index 000..768a1ea
--- /dev/null
+++ b/Docume
On 10/10/2013 10:20 AM, Joel Fernandes wrote:
> On 10/10/2013 08:32 AM, Nishanth Menon wrote:
>> On 00:32-20131010, Joel Fernandes wrote:
>>> On 10/09/2013 06:24 PM, Nishanth Menon wrote:
>>>> Call OMAP2+ generic lateinit hook from AM specific late init hook.
>
On 10/10/2013 08:32 AM, Nishanth Menon wrote:
> On 00:32-20131010, Joel Fernandes wrote:
>> On 10/09/2013 06:24 PM, Nishanth Menon wrote:
>>> Call OMAP2+ generic lateinit hook from AM specific late init hook.
>>> This allows the generic late initializations such as cpu
On Tue, Oct 8, 2013 at 12:00 PM, Mark Rutland wrote:
>> +static int __init integrator_cpufreq_probe(struct platform_device *pdev)
>> {
>> + struct device_node *np = pdev->dev.of_node;
>> +
>> + cm_base = of_iomap(np, 0);
>> + if (!cm_base)
>> + return -ENODEV;
>> re
On 10/10/2013 03:41 AM, Paul Mackerras wrote:
> On Wed, Oct 09, 2013 at 08:07:35AM -0700, H. Peter Anvin wrote:
>
>> consider the PowerPC random number generator[1]) and
>
> [snip]
>
>> [1] which has a known first-order bias which they "correct" for by
>> XORing two datums together in a very sim
This moves the core module (CM) control base into the device
tree. It is a simple memory range of 0x200 bytes. Move the
cm header down into the machine directory and unexport the
cm_control() symbol as no modules are using it.
Signed-off-by: Linus Walleij
---
ChangeLog v2->v3:
- Actually git add
1 - 100 of 161 matches
Mail list logo
