Hi Afzal,
On Thu, Jan 24, 2013 at 08:47:02AM +, Mohammed, Afzal wrote:
Hi Steffen,
On Thu, Jan 24, 2013 at 13:49:58, Steffen Trumtrar wrote:
Thanks. I'll use that opportunity for a v17 that is rebased onto 3.8-rc4.
As you are going to have a v17, if you can fold the diff[1]
(that
On 01/24/2013 10:14 PM, Florian Vaussard wrote:
You are right. But then the pwm core must provide a way to know if the pwm
access function are callable
from atomic context or not (the gpio framework provides gpio_cansleep()).
This implies a good amount of changes to the pwm framework, and
On Friday 25 January 2013 01:18 PM, Felipe Balbi wrote:
On Thu, Jan 24, 2013 at 09:32:46PM -0800, Stephen Warren wrote:
On 01/24/2013 06:19 PM, Kishon Vijay Abraham I wrote:
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to
On Friday 25 January 2013 01:13 PM, Felipe Balbi wrote:
Hi,
On Fri, Jan 25, 2013 at 08:42:24AM +0530, Kishon Vijay Abraham I wrote:
palmas-usb is made as a comparator driver to omap usb2 phy, so that
omap usb can make use of palmas for srp and also to set vbus.
Signed-off-by: Kishon Vijay
hi,
On Fri, Jan 25, 2013 at 02:12:41PM +0530, kishon wrote:
On Friday 25 January 2013 01:18 PM, Felipe Balbi wrote:
On Thu, Jan 24, 2013 at 09:32:46PM -0800, Stephen Warren wrote:
On 01/24/2013 06:19 PM, Kishon Vijay Abraham I wrote:
Added a new driver for the usb part of control module. This
On Friday 25 January 2013 02:15 PM, Felipe Balbi wrote:
hi,
On Fri, Jan 25, 2013 at 02:12:41PM +0530, kishon wrote:
On Friday 25 January 2013 01:18 PM, Felipe Balbi wrote:
On Thu, Jan 24, 2013 at 09:32:46PM -0800, Stephen Warren wrote:
On 01/24/2013 06:19 PM, Kishon Vijay Abraham I wrote:
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
Cc: Andrew Morton a...@linux-foundation.org
---
drivers/video/backlight/Kconfig |7 +
drivers/video/backlight/Makefile |1 +
drivers/video/backlight/hx8357.c | 482 ++
3 files changed, 490
On Fri, Jan 25, 2013 at 02:14:07PM +0530, kishon wrote:
On Friday 25 January 2013 01:13 PM, Felipe Balbi wrote:
Hi,
On Fri, Jan 25, 2013 at 08:42:24AM +0530, Kishon Vijay Abraham I wrote:
palmas-usb is made as a comparator driver to omap usb2 phy, so that
omap usb can make use of palmas for
Add helper to get fb_videomode from devicetree.
Signed-off-by: Steffen Trumtrar s.trumt...@pengutronix.de
Reviewed-by: Thierry Reding thierry.red...@avionic-design.de
Acked-by: Thierry Reding thierry.red...@avionic-design.de
Tested-by: Thierry Reding thierry.red...@avionic-design.de
Tested-by:
Add a function to convert from the generic videomode to a fb_videomode.
Signed-off-by: Steffen Trumtrar s.trumt...@pengutronix.de
Reviewed-by: Thierry Reding thierry.red...@avionic-design.de
Acked-by: Thierry Reding thierry.red...@avionic-design.de
Tested-by: Thierry Reding
Add helper to get drm_display_mode from devicetree.
Signed-off-by: Steffen Trumtrar s.trumt...@pengutronix.de
Reviewed-by: Thierry Reding thierry.red...@avionic-design.de
Acked-by: Thierry Reding thierry.red...@avionic-design.de
Tested-by: Thierry Reding thierry.red...@avionic-design.de
Add display_timing structure and the according helper functions. This allows
the description of a display via its supported timing parameters.
Also, add helper functions to convert from display timings to a generic
videomode
structure.
The struct display_timing specifies all needed parameters
This adds support for reading display timings from DT into a struct
display_timings. The of_display_timing implementation supports multiple
subnodes. All children are read into an array, that can be queried.
If no native mode is specified, the first subnode will be used.
For cases where the
Hi!
This is basically just a resend of v16 that was rebased onto v3.8-rc4 and has
two new tested-bys from Rob and Leela.
The patches were tested with:
- v15 on Tegra by Thierry
- sh-mobile-lcdcfb by Laurent
- MX53QSB by Marek
- Exynos: smdk5250 by Leela
-
Add conversion from videomode to drm_display_mode
Signed-off-by: Steffen Trumtrar s.trumt...@pengutronix.de
Reviewed-by: Thierry Reding thierry.red...@avionic-design.de
Acked-by: Thierry Reding thierry.red...@avionic-design.de
Tested-by: Thierry Reding thierry.red...@avionic-design.de
Tested-by:
The struct display_timing is specific to the via subsystem. The naming leads to
collisions with the new struct display_timing, which is supposed to be a shared
struct between different subsystems.
To clean this up, prepend the existing struct with the subsystem it is specific
to.
Signed-off-by:
This patch adds device tree based discovery support to G2D driver
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
drivers/media/platform/s5p-g2d/g2d.c | 17 -
1 files changed, 16 insertions(+), 1 deletions(-)
diff --git a/drivers/media/platform/s5p-g2d/g2d.c
From: Ajay Kumar ajaykumar...@samsung.com
This patch adds device tree match table for Exynos G2D controller.
Signed-off-by: Ajay Kumar ajaykumar...@samsung.com
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
drivers/gpu/drm/exynos/exynos_drm_g2d.c | 10 ++
1 files changed, 10
This patch enables hdmi support for Samsung Exynos4412 soc based Origen Board.
This set is base on for next branch at
git.kernel.org/?p=linux/kernel/git/kgene/linux-samsung.git
Rahul Sharma (4):
ARM: dts: add support for hdmi to exynos4
ARM: dts: add support for mixer to exynos4
ARM: dts:
Signed-off-by: Rahul Sharma rahul.sha...@samsung.com
Conflicts:
arch/arm/mach-exynos/mach-exynos4-dt.c
---
arch/arm/boot/dts/exynos4.dtsi | 7 +++
arch/arm/mach-exynos/mach-exynos4-dt.c | 2 ++
2 files changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4.dtsi
Signed-off-by: Rahul Sharma rahul.sha...@samsung.com
Conflicts:
arch/arm/boot/dts/exynos4.dtsi
---
arch/arm/boot/dts/exynos4.dtsi | 8
arch/arm/mach-exynos/mach-exynos4-dt.c | 2 ++
2 files changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4.dtsi
Signed-off-by: Rahul Sharma rahul.sha...@samsung.com
---
arch/arm/boot/dts/exynos4.dtsi | 1 -
arch/arm/boot/dts/exynos4412-origen.dts | 13 +
2 files changed, 13 insertions(+), 1 deletion(-)
mode change 100644 = 100755 arch/arm/boot/dts/exynos4412.dtsi
diff --git
Signed-off-by: Rahul Sharma rahul.sha...@samsung.com
---
arch/arm/boot/dts/exynos4.dtsi | 8
arch/arm/boot/dts/exynos4412.dtsi | 11 +++
arch/arm/mach-exynos/mach-exynos4-dt.c | 2 ++
3 files changed, 21 insertions(+)
mode change 100644 = 100755
Hi Guennadi,
On Thursday 24 January 2013 17:07:32 Guennadi Liakhovetski wrote:
If an ethernet PHY can be reset by a GPIO, it can be specified in DT. Add
a binding and code to parse it, request the GPIO and take the PHY out of
reset.
Signed-off-by: Guennadi Liakhovetski g.liakhovet...@gmx.de
Start using the control module driver for powering on the PHY and for
writing to the mailbox instead of writing to the control module
registers on their own.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/usb/omap-usb.txt |4 ++
A seperate driver has been added to handle the usb part of control
module. A device for the above driver is created here, using the register
address information to be used by the driver for powering on the PHY and
for writing to the mailbox.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Also added an API to power on usb3 phy (omap5).
Writing to control module registers for doing the
Added has_mailbox to the musb platform data to specify that omap uses
an external mailbox (in control module) to communicate with the musb
core during device connect and disconnect.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/mach-omap2/usb-musb.c |3 +++
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Writing to control module registers for doing the above task which was
previously done in omap
Add usb otg data node in omap4/omap3 device tree file. Also update
the node with board specific setting in omapx-board.dts file.
The dt data specifies among others the interface type (ULPI or UTMI), mode
which is mostly OTG, power that specifies the amount of power this can supply
when in host
Add omap control usb data in omap4 device tree file. This will have the
register address of registers to power on the PHY and to write to
mailbox. The information about this data node is available @
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I
This patch series adds dt data to get MUSB working in omap4 and omap3.
Long time back a patch series with the same title was sent but only
a part of it got merged. The rest of it wasn't merged because of
adding omap control usb data to glue and usb phy.
Now there exists a separate driver for
Add omap-usb2 data node in omap4 device tree file. Since omap-usb2 is
connected to ocp2scp, omap-usb2 dt data is added as a child node
of ocp2scp. The information about this data node is availabe @
Documentation/devicetree/bindings/usb/usb-phy.txt
Acked-by: Felipe Balbi ba...@ti.com
Hi,
On Fri, Jan 25, 2013 at 03:54:00PM +0530, Kishon Vijay Abraham I wrote:
Start using the control module driver for powering on the PHY and for
writing to the mailbox instead of writing to the control module
registers on their own.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
On 1/25/2013 11:43 AM, Mrugesh Katepallewar wrote:
Add RTC DT entries in da850 dts file.
Signed-off-by: Mrugesh Katepallewar mrugesh...@ti.com
---
Applies on top of v3.8-rc4 of linus tree.
Tested on da850-evm device.
Test Procedure:
date [.]MM.DD-hh:mm[:ss]
hwclock -w
reset
Hi Nicolas,
2013/1/22 Nicolas Pitre nicolas.pi...@linaro.org:
On Tue, 22 Jan 2013, Michal Simek wrote:
Hi,
I have a question regarding to the case where DTS specify one memory bank
for example 0x0 0x4000 with CONFIG_ARM_PATCH_PHYS_VIRT=y
where the kernel can be loaded at a 16MB
Hi Laurent
On Fri, 25 Jan 2013, Laurent Pinchart wrote:
Hi Guennadi,
On Thursday 24 January 2013 17:07:32 Guennadi Liakhovetski wrote:
If an ethernet PHY can be reset by a GPIO, it can be specified in DT. Add
a binding and code to parse it, request the GPIO and take the PHY out of
On 1/24/2013 5:05 PM, Vishwanathrao Badarkhe, Manish wrote:
Add I2C0 device tree node information to da850-evm.
Also, add I2C0 pin muxing information in da850-evm.
Signed-off-by: Vishwanathrao Badarkhe, Manish manish...@ti.com
---
Depends on patch
Apologies for the delay in sending this version.
Added a driver for usb3 phy that handles the interaction between usb phy
device and dwc3 controller.
Changes from v3:
* Changed the property name from ctrl_module to ctrl-module
Changes from v2:
* used control module driver APIs to write to
usb_otg_ss_refclk960m is needed for usb2 phy present in omap5. For
omap4, the clk_get of this clock will fail since it does not have this
clock.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/phy/omap-usb2.c | 28 +++-
1 file changed, 27
Added a driver for usb3 phy that handles the interaction between usb phy
device and dwc3 controller.
This also includes device tree support for usb3 phy driver and
the documentation with device tree binding information is updated.
Currently writing to control module register is taken care in
On Fri, Jan 25, 2013 at 10:23:57AM +, Kishon Vijay Abraham I wrote:
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Writing to control
Added dt support for dwc3 core and update the documentation with
device tree binding information. Getting a PHY is now done using
devm_usb_get_phy_by_phandle() for dt boot.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/usb/dwc3.txt | 22
On Fri, Jan 25, 2013 at 11:01:41AM +, Mark Rutland wrote:
On Fri, Jan 25, 2013 at 10:23:57AM +, Kishon Vijay Abraham I wrote:
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB
Add ocp2scp data node in omap5 device tree file. The information for
the node added here can be found @
Documentation/devicetree/bindings/bus/omap-ocp2scp.txt
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap5.dtsi |8
1 file changed, 8 insertions(+)
Add omap control usb data in omap5 device tree file. This will have the
register address of registers to power on the USB2 PHY and USB3 PHY. The
information for the node added here is available in
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I
Add omap-usb3 and omap-usb2 data node in omap5 device tree file.
The information for the node added here is available @
Documentation/devicetree/bindings/usb/usb-phy.txt
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 14 ++
1 file changed, 14
This patch series adds dt data to get dwc3 working in omap5.
Changes from v1:
* rename ctrl_module to ctrl-module and usb_phy to usb-phy
This patch series is developed on
git://github.com/rrnayak/linux.git omap5-3.8-rc4-base-palmas
This is the last series of the series of patches.
I've kept
Add dwc3 omap glue data to the omap5 dt data file. The information about
the dt node added here is available @
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 11 +++
1 file changed, 11
Add dwc3 core dt data as a subnode to dwc3 omap glue data in omap5 dt
data file. The information for the entered data node is available @
Documentation/devicetree/bindings/usb/dwc3.txt
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap5.dtsi |7 +++
1 file
Update palmas-usb data node in palmas device tree file
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/palmas.dtsi |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/palmas.dtsi b/arch/arm/boot/dts/palmas.dtsi
index
From: Lad, Prabhakar prabhakar@ti.com
This patch adds 'interrupt-parent' property in soc node, so that
the child inherits this property, this avoids adding 'interrupt-parent'
to each node.
Signed-off-by: Lad, Prabhakar prabhakar@ti.com
Cc: linux-arm-ker...@lists.infradead.org
Cc:
On 1/25/2013 4:34 PM, Katepallewar, Mrugesh wrote:
On Fri, Jan 25, 2013 at 16:04:22, Nori, Sekhar wrote:
On 1/25/2013 11:43 AM, Mrugesh Katepallewar wrote:
Add RTC DT entries in da850 dts file.
Signed-off-by: Mrugesh Katepallewar mrugesh...@ti.com
---
Applies on top of v3.8-rc4 of linus
On Friday 25 January 2013 03:57 PM, Felipe Balbi wrote:
Hi,
On Fri, Jan 25, 2013 at 03:54:00PM +0530, Kishon Vijay Abraham I wrote:
Start using the control module driver for powering on the PHY and for
writing to the mailbox instead of writing to the control module
registers on their own.
Hi Mike,
On Thu, Jan 24, 2013 at 22:30:44, Mike Turquette wrote:
Quoting Mohammed, Afzal (2013-01-24 03:36:02)
So there are 3 - LIDD is actually not for present use case, CORE could
be clubbed with the divider to have a composite clock. And CORE is
in functional clock path and logically
On 01/25/2013 09:29 AM, Peter Ujfalusi wrote:
On 01/24/2013 10:14 PM, Florian Vaussard wrote:
You are right. But then the pwm core must provide a way to know if the pwm
access function are callable
from atomic context or not (the gpio framework provides gpio_cansleep()).
This implies a good
Hi,
On Fri, Jan 25, 2013 at 04:41:46PM +0530, Kishon Vijay Abraham I wrote:
This patch series adds dt data to get dwc3 working in omap5.
Changes from v1:
* rename ctrl_module to ctrl-module and usb_phy to usb-phy
This patch series is developed on
git://github.com/rrnayak/linux.git
We have two drivers at the moment: pwm-twl and pwm-twl-led. However new out of
SoC PWM drivers might come (for example for palmas). So it worth take a look
at some generic implementation.
OK. So I have the series. I need to add few more things but pwm-leds on
BeagleBoard works fine when I put
Pass an optional device_node pointer in the platform data,
which in turn will be put into a mtd_part_parser_data.
This way, code that sets up the platform devices can pass
along the node from DT so that the partitions can be parsed.
For non-DT boards, this change has no effect.
Acked-by: Artem
Hello.
On 25-01-2013 7:00, Kishon Vijay Abraham I wrote:
No functional change. Stray statements where removed from dwc3 core.
s/where/are/
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/dwc3/core.c |3 ---
1 file changed, 3 deletions(-)
WBR, Sergei
gpmc_onenand_init() will be called from another driver's probe() function,
so drop the __init annotation, in order to prevent section mismatches.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/mach-omap2/gpmc-onenand.c |2 +-
1 files changed, 1 insertions(+),
On 01/25/2013 01:21 PM, Florian Vaussard wrote:
We have two drivers at the moment: pwm-twl and pwm-twl-led. However new out
of
SoC PWM drivers might come (for example for palmas). So it worth take a look
at some generic implementation.
OK. So I have the series. I need to add few more
[...]
+OMAP CONTROL USB
+
+Required properties:
+ - compatible: Should be ti,omap-control-usb
+ - reg : Address and length of the register set for the device. It
contains
+ the address of control_dev_conf and otghs_control or
phy_power_usb
Could you not use '-'
On 01/24/2013 10:12 PM, Simon Horman wrote:
On Thu, Jan 24, 2013 at 05:09:45PM +0100, Guennadi Liakhovetski wrote:
Signed-off-by: Guennadi Liakhovetski g.liakhovet...@gmx.de
I'm curious to know who would ack and or pick-up this patch.
I have applied it. You would know if get_maintainers.pl
Hi Kishon,
On Thu, Jan 24, 2013 at 17:21:45, Mohammed, Afzal wrote:
On Wed, Jan 23, 2013 at 19:56:37, ABRAHAM, KISHON VIJAY wrote:
On Wednesday 23 January 2013 07:28 PM, Mohammed, Afzal wrote:
USB first instance of am335x works in mainline as of now.
Can you check if this series indeed
Hi,
On Fri, Jan 25, 2013 at 12:29:43PM +, Mark Rutland wrote:
+ depending upon omap4 or omap5.
+ - reg-names: The names of the register addresses corresponding to the
registers
+ filled in reg.
+ - ti,type: This is used to differentiate whether the control module
Hi,
I have a couple more comments after looking though this a bit more thoroughly.
On Fri, Jan 25, 2013 at 12:23:11PM +, Ezequiel Garcia wrote:
This patch adds device tree bindings for OMAP OneNAND devices.
Tested on an OMAP3 3430 IGEPv2 board.
Signed-off-by: Ezequiel Garcia
Hi,
On Fri, Jan 25, 2013 at 04:14:02PM +, Mark Rutland wrote:
On Fri, Jan 25, 2013 at 02:59:28PM +, Felipe Balbi wrote:
Hi,
On Fri, Jan 25, 2013 at 12:29:43PM +, Mark Rutland wrote:
+ depending upon omap4 or omap5.
+ - reg-names: The names of the register
On Fri, Jan 25, 2013 at 04:23:46PM +, Felipe Balbi wrote:
Hi,
On Fri, Jan 25, 2013 at 04:14:02PM +, Mark Rutland wrote:
On Fri, Jan 25, 2013 at 02:59:28PM +, Felipe Balbi wrote:
Hi,
On Fri, Jan 25, 2013 at 12:29:43PM +, Mark Rutland wrote:
+ depending upon
MPIC allows the use of private interrupt for each CPUs. The 28th first
interrupts are per-cpu. This patch adds support to use them.
Signed-off-by: Gregory CLEMENT gregory.clem...@free-electrons.com
---
arch/arm/mach-mvebu/irq-armada-370-xp.c | 15 +++
1 file changed, 11
Hello,
The Armada XP SoCs comes with private timers. This allows us to use
local timers through CONFIG_LOCAL_TIMERS and as stated in the kconfig
help, it prevents a thundering herd at every timer tick.
Armada 370 also have these private timers, and even if it comes only
with a single CPU, the
On the SOCs Armada 370 and Armada XP, each CPU comes with two private
timers. This patch use the timer 0 of each CPU as local timer for the
clockevent if CONFIG_LOCAL_TIMER is selected. In the other case, use
only the private Timer 0 of CPU 0.
Signed-off-by: Gregory CLEMENT
Now that we have support for local timers, enable it by default
Signed-off-by: Gregory CLEMENT gregory.clem...@free-electrons.com
---
arch/arm/configs/mvebu_defconfig |1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/configs/mvebu_defconfig b/arch/arm/configs/mvebu_defconfig
index
Now that the time-armada-370-xp support local timers, updated the
device tree to take it into account.
Signed-off-by: Gregory CLEMENT gregory.clem...@free-electrons.com
---
arch/arm/boot/dts/armada-370-xp.dtsi |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git
Timer driver for Armada 370 and Armada XP have gained local timers
support. So it needs new resources information regarding the IRQs
and the registers.
Also move the documentation in the new and more accurate directory
Signed-off-by: Gregory CLEMENT gregory.clem...@free-electrons.com
---
On 25 January 2013 02:39, Rahul Sharma rahul.sha...@samsung.com wrote:
Signed-off-by: Rahul Sharma rahul.sha...@samsung.com
Conflicts:
arch/arm/mach-exynos/mach-exynos4-dt.c
---
arch/arm/boot/dts/exynos4.dtsi | 7 +++
arch/arm/mach-exynos/mach-exynos4-dt.c | 2 ++
2
Vivek Gautam wrote:
Using chip specific compatible string as it should be.
So fixing this for ehci-s5p, ohci-exynos and dwc3-exynos
which till now used a generic 'exynos' in their compatible strings.
Changes from v1:
- Changing compatible string from samsung,exynos5250-dwc3 to
Hi Mark,
First of all: thanks for reviewing.
On Fri, Jan 25, 2013 at 12:56 PM, Mark Rutland mark.rutl...@arm.com wrote:
Hi,
I have a couple more comments after looking though this a bit more thoroughly.
On Fri, Jan 25, 2013 at 12:23:11PM +, Ezequiel Garcia wrote:
This patch adds device
On Fri, Jan 25, 2013 at 11:34:55AM +0100, Guennadi Liakhovetski wrote:
Is there no need to reset the phy at runtime ?
No idea, I'm not developing the driver, I'm just porting one specific
feature from one API to another with no functional changes (apart from
postponing setting the GPIO).
From: Thomas Gleixner t...@linutronix.de
There is no real reason to use a rwlock for devtree_lock. It even
could be a mutex, but unfortunately it's locked from cpu hotplug
paths which can't schedule :(
So it needs to become a raw lock on rt as well. The devtree_lock would
be the only user of a
On Sunday 13 of January 2013 02:10:52 Tomasz Figa wrote:
This series is adds Device Tree support for Samsung S3C64xx SoC series.
It fixes several problems preventing from booting an S3C64xx-based
system using Device Tree, adds all the infrastructure for Device
Tree-based board support,
Tomasz Figa wrote:
[...]
Well, the number of CPU types does not grow rapidly. It will be much
less than one per SoC -- so keeping the list up to date shouldn't be
that much effort.
For ARM1176JZF-S, it could make sense for the comatible list to be
arm,arm1176jzf-s, arm,arm1176
Tomasz Figa wrote:
On Sunday 13 of January 2013 02:10:52 Tomasz Figa wrote:
This series is adds Device Tree support for Samsung S3C64xx SoC series.
It fixes several problems preventing from booting an S3C64xx-based
system using Device Tree, adds all the infrastructure for Device
Quoting Mohammed, Afzal (2013-01-25 04:05:44)
Hi Mike,
On Thu, Jan 24, 2013 at 22:30:44, Mike Turquette wrote:
Quoting Mohammed, Afzal (2013-01-24 03:36:02)
So there are 3 - LIDD is actually not for present use case, CORE could
be clubbed with the divider to have a composite clock.
Hi Guennadi,
On Friday 25 January 2013 11:34:55 Guennadi Liakhovetski wrote:
On Fri, 25 Jan 2013, Laurent Pinchart wrote:
On Thursday 24 January 2013 17:07:32 Guennadi Liakhovetski wrote:
If an ethernet PHY can be reset by a GPIO, it can be specified in DT.
Add a binding and code to
On Thu, Jan 24, 2013 at 12:39:48PM +0100, Wolfram Sang wrote:
On Thu, Jan 24, 2013 at 07:18:47PM +0800, Mark Brown wrote:
A read is typically implemented as a write of the register address
followed by a read of the value, usually with the ability to free the
bus in between. If two devices
On Fri, Jan 25, 2013 at 06:29:49AM +, Vishwanathrao Badarkhe, Manish wrote:
On Thu, Jan 24, 2013 at 17:30:51, Mark Brown wrote:
I too doubt that whether it should be in architecture specific folder,
My code is in reference to below patch:
arm/dts: regulator: Add tps65910 device tree
87 matches
Mail list logo
