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. For dt-boot, the PHY drivers should
also register *PHY provider* with the framework.
PHY drivers should create the PHY by
Used the generic PHY framework API to create the PHY. Now the power off and
power on are done in omap_usb_power_off and omap_usb_power_on respectively.
However using the old USB PHY library cannot be completely removed
because OTG is intertwined with PHY and moving to the new framework
will break
Added a generic PHY framework that 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.
This framework will be of use only to devices that uses external PHY (PHY
functionality is not embedded
Use the generic PHY framework API to get the PHY. The usb_phy_set_resume
and usb_phy_set_suspend is replaced with power_on and
power_off to align with the new PHY framework.
musb-xceiv can't be removed as of now because musb core uses xceiv.state and
xceiv.otg. Once there is a separate state
In order for controllers to get PHY in case of non dt boot, the phy
binding information (phy device name) should be added in the platform
data of the controller.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Reviewed-by: Sylwester Nawrocki s.nawro...@samsung.com
---
Updated the usb_otg_hs dt data to include the *phy* and *phy-names*
binding in order for the driver to use the new generic PHY framework.
Also updated the Documentation to include the binding information.
The PHY binding information can be found at
Used the generic PHY framework API to create the PHY. For powering on
and powering off the PHY, power_on and power_off ops are used. Once the
MUSB OMAP glue is adapted to the new framework, the suspend and resume
ops of usb phy library will be removed.
However using the old usb phy library cannot
Now that omap-usb2 is adapted to the new generic PHY framework,
*set_suspend* ops can be removed from omap-usb2 driver.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
Reviewed-by: Sylwester Nawrocki s.nawro...@samsung.com
---
Now that twl4030-usb is adapted to the new generic PHY framework,
*set_suspend* and *phy_init* ops can be removed from twl4030-usb driver.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
Reviewed-by: Sylwester Nawrocki s.nawro...@samsung.com
---
On 24 June 2013 20:55, Mark Brown broo...@kernel.org wrote:
On Mon, Jun 24, 2013 at 03:06:57PM +0530, Sachin Kamat wrote:
s5m8767 regulator is used on Exynos platforms which use pin controller
to configure GPIOs. Update the example accordingly.
This smells bad, why does a driver using GPIOs
On Mon, 2013-06-24 at 15:32 -0500, Benoit Parrot wrote:
Add LCDC device node in DT for am33xx
Add LCDC and Panel info in DT for am335x-evm
diff --git a/arch/arm/boot/dts/am335x-evm.dts
b/arch/arm/boot/dts/am335x-evm.dts
index 0423298..40d7a3f 100644
--- a/arch/arm/boot/dts/am335x-evm.dts
* Benoit Cousson b-cous...@ti.com [130624 07:42]:
Hi Tony,
On 06/24/2013 12:19 PM, Tony Lindgren wrote:
Hi,
For merging this series, I suggest the following sets:
* Joel A Fernandes joelag...@ti.com [130620 14:13]:
Joel A Fernandes (3):
edma: config: Enable config options
On 21 June 2013 14:14, Mike Turquette mturque...@linaro.org wrote:
Device Tree binding for the basic clock multiplexer, plus the setup
function to register the clock. Based on the existing fixed-clock
binding.
Includes minor beautification of clk-provider.h where some whitespace is
added
Add device tree bindings documentation for the TI WiLink modules.
Currently only the WLAN part of the WiLink6, WiLink7 and WiLink8
modules is supported.
Signed-off-by: Luciano Coelho coe...@ti.com
---
I created a new directory under net to contain wireless bindings documentation.
The actual
Thankyou for the comments.
On 24/06/13 23:08, Stephen Boyd wrote:
On 06/24/13 08:53, Srinivas KANDAGATLA wrote:
+#include linux/clkdev.h
Why do you need this include?
+#include asm/mach/irq.h
And this one?
Removed them.
+static u64 gt_counter_read(void)
+{
+u64 counter;
+
Thankyou for the comments,
On 24/06/13 23:00, Stephen Boyd wrote:
On 06/24/13 14:08, Srinivas KANDAGATLA wrote:
On 24/06/13 21:06, Stephen Boyd wrote:
On 06/24/13 08:53, Srinivas KANDAGATLA wrote:
I think the problem is your clockevent has no rating. Please give it a
rating (300?) so that
This series enables the use of the additional cores on Rockchip
Cortex-A9 SoCs.
To achieve this, add the scu, the needed sram and power-management-unit.
changes since v1:
- add reserved block feature for mmio-sram, to not use two logical
sram nodes
- the sram content is kept intact while the
The pool is created thru devm_gen_pool_create, so the call to
gen_pool_destroy is not necessary.
Instead the sram-clock must be turned off again if it exists.
Signed-off-by: Heiko Stuebner he...@sntech.de
---
drivers/misc/sram.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff
Some SoCs need parts of their sram for special purposes. So while being part
of the periphal, it should not be part of the genpool controlling the sram.
Threfore add an option mmio-sram-reserved to keep arbitary portions of the
sram from being part of the pool.
Suggested-by: Rob Herring
This adds the device-node and config select to enable the
scu in all Rockchip Cortex-A9 SoCs.
Signed-off-by: Heiko Stuebner he...@sntech.de
---
arch/arm/boot/dts/rk3066a.dtsi |5 +
arch/arm/mach-rockchip/Kconfig |1 +
2 files changed, 6 insertions(+)
diff --git
The Rockchip SoCs need a special part of their sram for bringup
of additional cores. Therefore also add a reserved section when adding the
mmio-sram node to keep the sram driver from using this space.
Signed-off-by: Heiko Stuebner he...@sntech.de
---
The pmu is needed to bring up the cores during smp operations.
Therefore add a node and documentation for it.
Signed-off-by: Heiko Stuebner he...@sntech.de
---
Documentation/devicetree/bindings/arm/rockchip/pmu.txt | 16
arch/arm/boot/dts/rk3066a.dtsi |
This adds the necessary smp-operations and startup code to use
additional cores on Rockchip SoCs.
We currently hog the power management unit in the smp code, as it is
necessary to control the power to the cpu core and nothing else is
currently using it, so a generic implementation can be done
Hi Heiko,
Am Dienstag, den 25.06.2013, 10:46 +0200 schrieb Heiko Stübner:
The pool is created thru devm_gen_pool_create, so the call to
gen_pool_destroy is not necessary.
Instead the sram-clock must be turned off again if it exists.
Signed-off-by: Heiko Stuebner he...@sntech.de
---
Hi Hans,
On Mon, Jun 24, 2013 at 1:21 PM, Hans Verkuil hverk...@xs4all.nl wrote:
Hi Prabhakar,
On Sat June 22 2013 17:03:03 Prabhakar Lad wrote:
From: Lad, Prabhakar prabhakar.cse...@gmail.com
[snip]
+#ifndef _DT_BINDINGS_VIDEO_INTERFACES_H
+#define _DT_BINDINGS_VIDEO_INTERFACES_H
+
From: Stuart Menefy stuart.men...@st.com
This is a simple driver for the global timer module found in the Cortex
A9-MP cores from revision r1p0 onwards. This should be able to perform
the functions of the system timer and the local timer in an SMP system.
The global timer has the following
On 24/06/13 15:12, Mark Brown wrote:
On Mon, Jun 24, 2013 at 01:57:56PM +0200, Linus Walleij wrote:
This seems fairly complete, but I cannot have such a basic dependency onto
the regmap tree this late in the merge window, i.e. I'm not ready to pull
all of regmap into the pinctrl tree. I'd
Hi Will,
On Mon, 10 Jun 2013 20:34:39 +0200
Will Deacon will.dea...@arm.com wrote:
...
@@ -1636,13 +1636,27 @@ static dma_addr_t arm_coherent_iommu_map_page(struct
device *dev, struct page *p
{
struct dma_iommu_mapping *mapping = dev-archdata.mapping;
dma_addr_t dma_addr;
-
Hi Heiko,
Am Dienstag, den 25.06.2013, 10:47 +0200 schrieb Heiko Stübner:
Some SoCs need parts of their sram for special purposes. So while being part
of the periphal, it should not be part of the genpool controlling the sram.
Threfore add an option mmio-sram-reserved to keep arbitary
On 25/06/13 00:38, Greg Kroah-Hartman wrote:
On Mon, Jun 24, 2013 at 08:21:43AM +0100, Srinivas KANDAGATLA wrote:
From: Srinivas Kandagatla srinivas.kandaga...@st.com
This patch adds support to ASC (asynchronous serial controller)
driver, which is basically a standard serial driver. This IP
On Mon, Jun 24, 2013 at 4:12 PM, Mark Brown broo...@kernel.org wrote:
On Mon, Jun 24, 2013 at 01:57:56PM +0200, Linus Walleij wrote:
This seems fairly complete, but I cannot have such a basic dependency onto
the regmap tree this late in the merge window, i.e. I'm not ready to pull
all of
Hi,
On Tue, Jun 25, 2013 at 11:35:30AM +0300, Luciano Coelho wrote:
Add device tree bindings documentation for the TI WiLink modules.
Currently only the WLAN part of the WiLink6, WiLink7 and WiLink8
modules is supported.
Signed-off-by: Luciano Coelho coe...@ti.com
---
I created a new
On 25/06/13 11:58, Linus Walleij wrote:
On Mon, Jun 24, 2013 at 4:12 PM, Mark Brown broo...@kernel.org wrote:
On Mon, Jun 24, 2013 at 01:57:56PM +0200, Linus Walleij wrote:
This seems fairly complete, but I cannot have such a basic dependency onto
the regmap tree this late in the merge
On Tue, Jun 18, 2013 at 06:16:57PM +0200, Guennadi Liakhovetski wrote:
This patch adds Device Tree support to the shdma driver. No special DT
properties are used, only standard DMA DT bindings are implemented. Since
shdma controllers reside on SoCs, their configuration is SoC-specific and
On Tue, Jun 25, 2013 at 11:12:15AM +0100, Hiroshi Doyu wrote:
Hi Will,
Hi Hiroshi,
On Mon, 10 Jun 2013 20:34:39 +0200
Will Deacon will.dea...@arm.com wrote:
...
@@ -1636,13 +1636,27 @@ static dma_addr_t
arm_coherent_iommu_map_page(struct device *dev, struct page *p
{
struct
On Mon, Jun 24, 2013 at 5:33 PM, Lorenzo Pieralisi
lorenzo.pieral...@arm.com wrote:
Hi all,
I am dealing with a lingering problem related to init and probing of platform
devices early (before initcalls) in the kernel boot process. The problem,
which is nothing new, is related to how platform
Will Deacon will.dea...@arm.com wrote @ Tue, 25 Jun 2013 13:37:14 +0200:
...
Do we need similar changes for map_sg case as well? They still passes '0'
as prot.
Yes, we could use the same trick there (probably worth moving the logic into
a helper function for translating dma_data_direction
On Tue, 2013-06-25 at 14:12 +0300, Felipe Balbi wrote:
On Tue, Jun 25, 2013 at 11:35:30AM +0300, Luciano Coelho wrote:
+- tcxoclock: the internal WLAN TCXO clock frequency (required for
+ WiLink7 not used for WiLink6 and WiLink8). Must be one of the
+ following:
+ 0 = 19.200 MHz
+
On 06/25/2013 06:32 AM, Ruslan Bilovol wrote:
The OMAP4 Blaze Tablet is TI OMAP4 processor-based
development platform in a tablet formfactor.
The platform contains many of the features found in
present-day handsets (such as audio, video, wireless
functions and user interfaces) and in addition
On Tue, Jun 25, 2013 at 12:52:26PM +0100, Hiroshi Doyu wrote:
Will Deacon will.dea...@arm.com wrote @ Tue, 25 Jun 2013 13:37:14 +0200:
...
Do we need similar changes for map_sg case as well? They still passes '0'
as prot.
Yes, we could use the same trick there (probably worth moving
On 06/25/2013 07:01 AM, Nishanth Menon wrote:
On 06/25/2013 06:32 AM, Ruslan Bilovol wrote:
The OMAP4 Blaze Tablet is TI OMAP4 processor-based
development platform in a tablet formfactor.
The platform contains many of the features found in
present-day handsets (such as audio, video, wireless
PULL_PIN_DEFAULT is meant for hardware completely hiding any pull
settings from the driver, so that it's really only possible to turn
the pull on or off, but it not being possible to determine any
pull settings from software.
Also the binding-documentation for the pull arguments did not match
the
As Stephen Warren pointed out, some pinconf bindings had deficits
either in documentation or in the whole thought process.
Therefore this series tries to fix these issues by improving
documentation and removing the real controversial bindings for now.
Of the changed pinconf bindings only the
As the binding for slew-rate is under discussion and seems to need
more tought it will get removed for now, so it doesn't get an offical
release.
Therefore remove it again from the only current user, tz1090.
Signed-off-by: Heiko Stuebner he...@sntech.de
---
Currently the debounce time pinconfig option uses an unspecified
time units unit. As pinconfig options should use SI units and a
real unit is also necessary for generic dt bindings, change it
to usec. Currently no driver is using the generic pinconfig option
for this, so the unit change is safe to
Some options currently take arguments in unspecified driver-specific units.
As pointed out by Stephen Warren, driver specific values should not be part
of generic devicetree bindings describing the hardware.
Therefore remove the critical bindings again, before they become part of
an official
Hi Heiko,
On 25/06/13 13:56, Heiko Stübner wrote:
As the binding for slew-rate is under discussion and seems to need
more tought it will get removed for now, so it doesn't get an offical
s/tought/thought/
s/offical/official/
release.
Therefore remove it again from the only current user,
On Tue, Jun 25, 2013 at 02:56:10PM +0300, Luciano Coelho wrote:
On Tue, 2013-06-25 at 14:12 +0300, Felipe Balbi wrote:
On Tue, Jun 25, 2013 at 11:35:30AM +0300, Luciano Coelho wrote:
+- tcxoclock: the internal WLAN TCXO clock frequency (required for
+ WiLink7 not used for WiLink6 and
On Tue, Jun 25, 2013 at 2:55 PM, Heiko Stübner he...@sntech.de wrote:
PULL_PIN_DEFAULT is meant for hardware completely hiding any pull
settings from the driver, so that it's really only possible to turn
the pull on or off, but it not being possible to determine any
pull settings from
On Tue, Jun 25, 2013 at 2:56 PM, Heiko Stübner he...@sntech.de wrote:
Currently the debounce time pinconfig option uses an unspecified
time units unit. As pinconfig options should use SI units and a
real unit is also necessary for generic dt bindings, change it
to usec. Currently no driver is
On Tue, 25 Jun 2013, Srinivas KANDAGATLA wrote:
If its not too late can this patch be considered for 3.11 via clocksource
tree?
Sure. No worry, though I noticed a little detail when reading through it
again. See below.
+/**
+ * To ensure that updates to comparator value register do not set
On 25/06/13 13:55, Heiko Stübner wrote:
As Stephen Warren pointed out, some pinconf bindings had deficits
either in documentation or in the whole thought process.
Therefore this series tries to fix these issues by improving
documentation and removing the real controversial bindings for now.
On Tue, Jun 25, 2013 at 3:05 PM, James Hogan james.ho...@imgtec.com wrote:
Hi Heiko,
On 25/06/13 13:56, Heiko Stübner wrote:
As the binding for slew-rate is under discussion and seems to need
more tought it will get removed for now, so it doesn't get an offical
s/tought/thought/
On 25/06/13 14:21, Heiko Stübner wrote:
Am Dienstag, 25. Juni 2013, 15:05:05 schrieb James Hogan:
Hi Heiko,
On 25/06/13 13:56, Heiko Stübner wrote:
As the binding for slew-rate is under discussion and seems to need
more tought it will get removed for now, so it doesn't get an offical
On Tue, Jun 25, 2013 at 3:27 PM, James Hogan james.ho...@imgtec.com wrote:
On 25/06/13 14:21, Heiko Stübner wrote:
My thoughts were that this code would never be reached when the parsing was
removed and to not cause confusion to the driver when an acceptable binding
was found for slew-rate.
On Tue, Jun 25, 2013 at 2:29 PM, Christian Ruppert
christian.rupp...@abilis.com wrote:
On Mon, Jun 03, 2013 at 10:51:06AM +0100, Grant Likely wrote:
On Mon, Jun 3, 2013 at 5:05 AM, Vineet Gupta vineet.gup...@synopsys.com
wrote:
On 06/01/2013 03:48 AM, Grant Likely wrote:
If I were working
On Tue, Jun 25, 2013 at 2:57 PM, Heiko Stübner he...@sntech.de wrote:
Some options currently take arguments in unspecified driver-specific units.
As pointed out by Stephen Warren, driver specific values should not be part
of generic devicetree bindings describing the hardware.
Therefore
Thanks for the comments.
On 25/06/13 14:17, Thomas Gleixner wrote:
On Tue, 25 Jun 2013, Srinivas KANDAGATLA wrote:
If its not too late can this patch be considered for 3.11 via clocksource
tree?
Sure. No worry, though I noticed a little detail when reading through it
again. See below.
On 25/06/13 14:32, Linus Walleij wrote:
On Tue, Jun 25, 2013 at 3:27 PM, James Hogan james.ho...@imgtec.com wrote:
On 25/06/13 14:21, Heiko Stübner wrote:
My thoughts were that this code would never be reached when the parsing was
removed and to not cause confusion to the driver when an
On Fri, 31 May 2013, Christian Ruppert wrote:
The SOC interrupt controller driver for the Abilis Systems TB10x series of
SOCs based on ARC700 CPUs.
This patch depends on commits eb76bdd407d8a90e59a06cb0158886df390e5d1c and
712bc93df9e7f14b8a163148d2aa7c778e151627 from branch irq/for-arm of
On Tue, 25 Jun 2013, Srinivas KANDAGATLA wrote:
On 25/06/13 14:17, Thomas Gleixner wrote:
On Tue, 25 Jun 2013, Srinivas KANDAGATLA wrote:
+static void gt_compare_set(unsigned long delta, int periodic)
+{
+ u64 counter = gt_counter_read();
+ unsigned long ctrl = readl(gt_base +
On 6/25/2013 12:24 PM, Tony Lindgren wrote:
* Benoit Cousson b-cous...@ti.com [130624 07:42]:
Hi Tony,
On 06/24/2013 12:19 PM, Tony Lindgren wrote:
Hi,
For merging this series, I suggest the following sets:
* Joel A Fernandes joelag...@ti.com [130620 14:13]:
Joel A Fernandes (3):
This patch series adds a simple driver for the Samsung S5P/Exynos SoC
series MIPI CSI-2 receiver (MIPI DSIM) and MIPI DSI transmitter (MIPI
DSIM) DPHYs, using the generic PHY framework [1]. Previously the MIPI
CSIS and MIPI DSIM used a platform callback to control the PHY power
enable and reset
Add a PHY provider driver for the Samsung S5P/Exynos SoC MIPI CSI-2
receiver and MIPI DSI transmitter DPHYs.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
Changes since v1:
- enabled build as module and with CONFIG_OF disabled
Add PHY provider node for the MIPI CSIS and MIPI DSIM PHYs.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
arch/arm/boot/dts/exynos4.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git
Use the generic PHY API instead of the platform callback to control
the MIPI CSIS DPHY. The 'phy_label' field is added to the platform
data structure to allow PHY lookup on non-dt platforms
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Signed-off-by: Kyungmin Park
Use the generic PHY API instead of the platform callback to control
the MIPI DSIM DPHY. The 'phy_label' field is added to the platform
data structure to allow PHY lookup on non-dt platforms.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Signed-off-by: Kyungmin Park
Generic PHY drivers are used to handle the MIPI CSIS and MIPI DSIM
DPHYs so we can remove now unused code at arch/arm/plat-samsung.
In case there is any board file for S5PV210 platforms using MIPI
CSIS/DSIM (not any upstream currently) it should use the generic
PHY API to bind the PHYs to
On Fri, Jun 21, 2013 at 11:17 PM, Stephen Warren swar...@wwwdotorg.org wrote:
When I pushed for the concept of groups, I intended it to mean precisely
one single thing. The points below describe this.
1) A pin is a single pin/ball/pad on the package.
2) Some register fields affect just a
Add a GPIO driver for the main GPIOs found in the TZ1090 (Comet) SoC.
This doesn't include low-power GPIOs as they're controlled separately
via the Powerdown Controller (PDC) registers.
The driver is instantiated by device tree and supports interrupts for
all GPIOs.
Signed-off-by: James Hogan
Add a GPIO driver for the low-power Powerdown Controller GPIOs in the
TZ1090 SoC.
The driver is instantiated by device tree and supports interrupts for
the SysWake GPIOs only.
Signed-off-by: James Hogan james.ho...@imgtec.com
Cc: Grant Likely grant.lik...@linaro.org
Cc: Rob Herring
This patchset adds GPIO drivers for the TZ1090, for both the general
GPIOs, and the low power (PDC) GPIOs.
LinusW: Please consider taking the first 2 patches for v3.11. Patch 3
converts gpio-tz1090 (from patch 1) to use generic irqchip, but it
depends on code currently in tip/irq/core (for
On Fri, Jun 21, 2013 at 11:17 PM, Stephen Warren swar...@wwwdotorg.org wrote:
On 06/20/2013 05:57 AM, Christian Ruppert wrote:
The Linux pinctrl subsystem specifically doesn't provide mutual
exclusion between mux function and GPIO usage within a pin group,
although perhaps a driver could
On Tue, 25 Jun 2013, Christian Ruppert wrote:
On Tue, Jun 25, 2013 at 03:58:43PM +0200, Thomas Gleixner wrote:
On Fri, 31 May 2013, Christian Ruppert wrote:
The SOC interrupt controller driver for the Abilis Systems TB10x series of
SOCs based on ARC700 CPUs.
This patch depends on
On Tuesday 25 June 2013 10:16 AM, Sekhar Nori wrote:
On 6/25/2013 12:24 PM, Tony Lindgren wrote:
* Benoit Cousson b-cous...@ti.com [130624 07:42]:
Hi Tony,
On 06/24/2013 12:19 PM, Tony Lindgren wrote:
Hi,
For merging this series, I suggest the following sets:
* Joel A Fernandes
On 06/25/2013 05:45 AM, Grant Likely wrote:
On Mon, Jun 24, 2013 at 5:33 PM, Lorenzo Pieralisi
lorenzo.pieral...@arm.com wrote:
Hi all,
I am dealing with a lingering problem related to init and probing of platform
devices early (before initcalls) in the kernel boot process. The problem,
On Fri, Jun 21, 2013 at 11:17 PM, Stephen Warren swar...@wwwdotorg.org wrote:
On 06/20/2013 05:57 AM, Christian Ruppert wrote:
Your remark seems to reflect one of the following two hardware
architectures:
+- SPI
Physical
On 25/06/13 14:22, Linus Walleij wrote:
Can't we just try to come up with a patch that nails down the meaning of
slew rate in some meaningful manner then?
So according to:
http://en.wikipedia.org/wiki/Slew_rate
a proper expression for slew rate would be dV/dt i.e.
something like microvolts
Hi,
On 06/25/2013 02:38 PM, Tero Kristo wrote:
Hi,
Changes compared to previous version:
PATCH 2 - removed some unnecessary headers + module defs
- added Mike under copyright
PATCH 4 - fixed the copyright in the header file
PATCH 8 - removed a few incorrect comments from the
Hi,
On Tue, Jun 25, 2013 at 04:21:46PM +0200, Sylwester Nawrocki wrote:
+enum phy_id {
+ PHY_CSIS0,
+ PHY_DSIM0,
+ PHY_CSIS1,
+ PHY_DSIM1,
+ NUM_PHYS
please prepend these with EXYNOS_PHY_ or EXYNOS_MIPI_PHY_
+struct exynos_video_phy {
+ spinlock_t slock;
+
Hi,
On Tue, Jun 25, 2013 at 04:21:48PM +0200, Sylwester Nawrocki wrote:
Use the generic PHY API instead of the platform callback to control
the MIPI DSIM DPHY. The 'phy_label' field is added to the platform
data structure to allow PHY lookup on non-dt platforms.
Signed-off-by: Sylwester
On Tue, Jun 25, 2013 at 04:21:49PM +0200, Sylwester Nawrocki wrote:
Use the generic PHY API instead of the platform callback to control
the MIPI CSIS DPHY. The 'phy_label' field is added to the platform
data structure to allow PHY lookup on non-dt platforms
Signed-off-by: Sylwester Nawrocki
On Tue, Jun 25, 2013 at 04:21:50PM +0200, Sylwester Nawrocki wrote:
Generic PHY drivers are used to handle the MIPI CSIS and MIPI DSIM
DPHYs so we can remove now unused code at arch/arm/plat-samsung.
In case there is any board file for S5PV210 platforms using MIPI
CSIS/DSIM (not any upstream
On Tue, Jun 25, 2013 at 11:28:40AM +0530, Kishon Vijay Abraham I wrote:
Used the generic PHY framework API to create the PHY. Now the power off and
power on are done in omap_usb_power_off and omap_usb_power_on respectively.
However using the old USB PHY library cannot be completely removed
On Tue, Jun 25, 2013 at 11:28:42AM +0530, Kishon Vijay Abraham I wrote:
In order for controllers to get PHY in case of non dt boot, the phy
binding information (phy device name) should be added in the platform
data of the controller.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
On Tue, Jun 25, 2013 at 11:28:44AM +0530, Kishon Vijay Abraham I wrote:
Use the generic PHY framework API to get the PHY. The usb_phy_set_resume
and usb_phy_set_suspend is replaced with power_on and
power_off to align with the new PHY framework.
musb-xceiv can't be removed as of now because
On Tue, Jun 25, 2013 at 11:28:45AM +0530, Kishon Vijay Abraham I wrote:
Now that omap-usb2 is adapted to the new generic PHY framework,
*set_suspend* ops can be removed from omap-usb2 driver.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
On Tue, Jun 25, 2013 at 11:28:46AM +0530, Kishon Vijay Abraham I wrote:
Now that twl4030-usb is adapted to the new generic PHY framework,
*set_suspend* and *phy_init* ops can be removed from twl4030-usb driver.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Reviewed-by: Felipe Balbi
On 06/25/2013 08:32 AM, Linus Walleij wrote:
On Fri, Jun 21, 2013 at 11:17 PM, Stephen Warren swar...@wwwdotorg.org
wrote:
On 06/20/2013 05:57 AM, Christian Ruppert wrote:
The Linux pinctrl subsystem specifically doesn't provide mutual
exclusion between mux function and GPIO usage within a
Hi,
On Tue, Jun 25, 2013 at 11:28:39AM +0530, Kishon Vijay Abraham I wrote:
diff --git a/include/linux/phy/phy.h b/include/linux/phy/phy.h
new file mode 100644
index 000..7abf573
--- /dev/null
+++ b/include/linux/phy/phy.h
on this header, how about adding phy_set_drvdata() and
On 06/25/2013 08:27 AM, Linus Walleij wrote:
On Fri, Jun 21, 2013 at 11:17 PM, Stephen Warren swar...@wwwdotorg.org
wrote:
When I pushed for the concept of groups, I intended it to mean precisely
one single thing. The points below describe this.
1) A pin is a single pin/ball/pad on the
On Thu, Jun 20, 2013 at 03:05:38PM +0100, Srinivas KANDAGATLA wrote:
This patch add pinctrl support to ST SoCs.
About hardware:
ST Set-Top-Box parts have two blocks called PIO and PIO-mux which handle
pin configurations.
Applied, thanks.
signature.asc
Description: Digital signature
This patch adds OF match table to the driver to allow instantiating it
using device tree.
Signed-off-by: Tomasz Figa t.f...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
.../devicetree/bindings/usb/samsung-hsotg.txt | 40 ++
On Tue, Jun 25, 2013 at 3:50 PM, James Hogan james.ho...@imgtec.com wrote:
On 25/06/13 14:32, Linus Walleij wrote:
Patches adding it back in with SI measures will be welcomed!
Okay.
So the most descriptive documentation I can find for the slew rate in
the TZ1090 pin config hardware is
This patch adds device tree node for USB HSOTG controller present on
Exynos4 SoCs.
Signed-off-by: Tomasz Figa t.f...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
arch/arm/boot/dts/exynos4.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git
This patch adds device tree nodes for USB OTG PHYs of Exynos4210 and
Exynos4x12 SoCs.
Signed-off-by: Tomasz Figa t.f...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
arch/arm/boot/dts/exynos4210.dtsi | 15 +++
arch/arm/boot/dts/exynos4x12.dtsi | 15
This patch adds device tree nodes necessary to enable USB gadget
functionality on Exynos4210-based Trats board.
Signed-off-by: Tomasz Figa t.f...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
arch/arm/boot/dts/exynos4210-trats.dts | 10 ++
1 file changed, 10
On 06/25/2013 09:28 AM, Linus Walleij wrote:
On Fri, Jun 21, 2013 at 11:17 PM, Stephen Warren swar...@wwwdotorg.org
wrote:
And finally, I don't really like using pin groups for the purpose of
defining these mappings, since I intended them to purely represent the
mapping from register
This series enables platforms booting with Device Tree to use the Samsung
HSOTG IP. Since USB PHY support has been already added, it's just a matter
of adding an OF match table to the driver and respective device tree nodes
to dts files.
[On Samsung Trats board based on Exynos 4210]
Tested-by:
On Tue, Jun 25, 2013 at 5:31 PM, Stephen Warren swar...@wwwdotorg.org wrote:
On 06/25/2013 08:56 AM, Linus Walleij wrote:
On Fri, Jun 21, 2013 at 11:17 PM, Stephen Warren swar...@wwwdotorg.org
wrote:
On 06/20/2013 05:57 AM, Christian Ruppert wrote:
Your remark seems to reflect one of the
1 - 100 of 132 matches
Mail list logo
