From: Young-Gun Jang
Add support for mapping Samsung Power Management Unit (PMU)
base address from device tree. This patch also adds helper
function as "get_exynos_pmuregmap". This function can be used
by other machine files such as "pm.c", "hotplug.c" for accessing
PMU regmap handle.
Signed-off
As we have removed static mappings from "regs-pmu.h" it does not
need map.h anymore. But "platsmp.c" needed this and till now it
got included indirectly. So lets move header inclusion of
"mach/map.h" from "regs-pmu.h" to "platsmp.c".
Signed-off-by: Pankaj Dubey
---
arch/arm/mach-exynos/platsmp.c
This patch removes unnecessary header file inclusion from pmu.c.
Signed-off-by: Young-Gun Jang
Reviewed-by: Tomasz Figa
---
arch/arm/mach-exynos/pmu.c |1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/mach-exynos/pmu.c b/arch/arm/mach-exynos/pmu.c
index 05c7ce1..4c3453a 100644
---
From: Young-Gun Jang
Current "pm_domain.c" file uses "S5P_INT_LOCAL_PWR_EN" definition from
"regs-pmu.h" and hence needs to include this header file. As there is
no other user of "S5P_INT_LOCAL_PWR_EN" definition other than pm_domain,
to remove "regs-pmu.h" header file dependency from "pm_domain.
Under "arm/mach-exynos" many files are using PMU register offsets.
Since we have added support for accessing PMU base address via DT,
now we can remove PMU mapping from exynosX_iodesc. Let's convert
all these access using either of iomapped address or regmap handle.
This will help us in removing st
Many files under "arm/mach-exynos" are having file path in file
comment section which is invalid now.
So for better code maintainability let's remove them.
Signed-off-by: Pankaj Dubey
Reviewed-by: Tomasz Figa
---
arch/arm/mach-exynos/headsmp.S |2 --
arch/arm/mach-exynos/hotplug
This patch modifies Exynos Power Management Unit (PMU) initialization
implementation in following way:
- Added platform_device support by registering static platform device.
- Added platform struct exynos_pmu_data to hold platform specific data.
- For each SoC's PMU support now we can add platform
From: Young-Gun Jang
This patch moves PMU specific definitions into a new file
as exynos-pmu.h. This will help in making PMU implementation
independent of common.h header.
Signed-off-by: Young-Gun Jang
Signed-off-by: Pankaj Dubey
---
arch/arm/mach-exynos/common.h | 17 -
From: Young-Gun Jang
While making PMU implementation to be device tree based, there are
few register offsets related with SYSREG present in regs-pmu.h, so
let's make a new header file "regs-sys.h" to keep all such SYSREG
related register offsets and remove them from "regs-pmu.h"
Signed-off-by: Y
As machine function ops are used only in this file let's make
them static. Also remove unused and unwanted declarations from
common.h.
Signed-off-by: Pankaj Dubey
---
arch/arm/mach-exynos/common.h |8
arch/arm/mach-exynos/exynos.c |6 +++---
2 files changed, 3 insertions(+), 11
As exynos_cpuidle_init and exynos_cpufreq_init function have just one lines
of code for registering platform devices. We can move these lines to
exynos_dt_machine_init and delete exynos_cpuidle_init and exynos_cpufreq_init
function. This will help in reducing lines of code in exynos.c, making it
mo
This patch series, does some minor cleanup of exynos machine files.
It also modifies Exynos Power Management Unit (PMU) related code for
converting it into a platform_driver. This is also preparation for moving
PMU related code out of machine folder into a either "drivers/mfd", or
"drivers/power" o
This patch updates samsung pmu (power management unit) binding information.
CC: Leela Krishna Amudala
CC: Tomasz Figa
CC: Guenter Roeck
CC: Rob Landley
Signed-off-by: Pankaj Dubey
---
Documentation/devicetree/bindings/arm/samsung/pmu.txt |3 +++
1 file changed, 3 insertions(+)
diff --gi
This patch adds pmu regnode to exynos4210 dtsi to handle
PMU register access via DT.
Signed-off-by: Pankaj Dubey
---
arch/arm/boot/dts/exynos4210.dtsi |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4210.dtsi
b/arch/arm/boot/dts/exynos4210.dtsi
index d3d727b.
This patch adds pmu regnode to exynos4212 and exynos4412 dtsi to
handle PMU register access via DT.
Signed-off-by: Pankaj Dubey
---
arch/arm/boot/dts/exynos4212.dtsi |5 +
arch/arm/boot/dts/exynos4412.dtsi |5 +
2 files changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/ex
This patch updates Exynos4210, Exynos4412 and Exynos4212 dtsi files
for adding PMU (Power Management Unit) reg node.
Updated binding document for the same.
These patches are required for converting PMU implementation free from
static mapping of PMU registers as well as it's dependency from machine
Hi Vikas,
On 05/08/2014 07:52 PM, Vikas Sajjan wrote:
Add intial PMU settings for exynos5420. This is required for
future S2R and Switching support.
Signed-off-by: Thomas Abraham
Signed-off-by: Abhilash Kesavan
Signed-off-by: Vikas Sajjan
---
arch/arm/mach-exynos/common.h |9 ++
arc
Hi Vikas,
On 05/08/2014 07:52 PM, Vikas Sajjan wrote:
Adds Suspend-to-RAM support for EXYNOS5420
Signed-off-by: Abhilash Kesavan
Signed-off-by: Vikas Sajjan
---
arch/arm/mach-exynos/pm.c | 163 ++-
arch/arm/mach-exynos/regs-pmu.h |2 +
2 file
On Fri, May 9, 2014 at 12:32 AM, Jaehoon Chung wrote:
> Hi, Sonny.
>
> You can discard the my previous some comment.
> As you mentioned, this reset sequence is recommended at Synopsys TRM.
>
> Add the minor question.
>
> On 05/09/2014 01:27 PM, Jaehoon Chung wrote:
>> Hi, Sonny.
>>
>> I have check
On 05/09/2014 10:00 PM, Tushar Behera wrote:
All SoC in Exynos-series have a clock with name XCLKOUT to provide
debug information about various clocks available in the SoC. The register
controlling the MUX and GATE of this clock is provided within PMU domain.
Since PMU domain can't be dedicatedly
Hi Tushar,
On 05/09/2014 10:00 PM, Tushar Behera wrote:
The MUX/GATE register for XCLKOUT doesn't resides within PMU domain,
this can be accessed through a regmap provided by syscon driver. Adding
another clock provider to handle regmap based handing of XCLKOUT.
Dependency:
1. [PATCH v3] mfd: s
;> by somebody with knowledge about the specific hardware.
> >>>>
> >>>> Signed-off-by: Heiko Stuebner
> >>>> Reviewed-by: Tomasz Figa
> >>>
> >>> It seems this one just hit linux-next (in next-20140509).
> >>
>
specific hardware.
Signed-off-by: Heiko Stuebner
Reviewed-by: Tomasz Figa
It seems this one just hit linux-next (in next-20140509).
Which is bad, because:
a) it conflicts with patches already applied in samsung-clk tree,
I remember seeing patches regarding more than one clk-samsung clock
the external clocks will have to be set
> >> by somebody with knowledge about the specific hardware.
> >>
> >> Signed-off-by: Heiko Stuebner
> >> Reviewed-by: Tomasz Figa
> >
> > It seems this one just hit linux-next (in next-20140509).
>
> Which
Am Freitag, 9. Mai 2014, 18:49:41 schrieb Paul Bolle:
> > @@ -643,7 +654,8 @@ config MACH_RX1950
> >
> > select PM_H1940 if PM
> > select S3C2410_IOTIMING if ARM_S3C2440_CPUFREQ
> > select S3C2440_XTAL_16934400
> >
> > - select S3C24XX_DCLK
> > + select S3C24XX_DCLK if SAMSUNG_CLO
linux-next (in next-20140509).
Which is bad, because:
a) it conflicts with patches already applied in samsung-clk tree,
b) the DT binding added by patch 4/9 has not been acked .
Kukjin, might I ask you to drop this series from your tree and let me
send you a pull request with necessary
his one just hit linux-next (in next-20140509).
> --- a/arch/arm/mach-s3c24xx/Kconfig
> +++ b/arch/arm/mach-s3c24xx/Kconfig
> @@ -18,6 +18,13 @@ config PLAT_S3C24XX
> help
> Base platform code for any Samsung S3C24XX device
>
> +config S3C2410_COMMON_
On Mon, May 05, 2014 at 10:27:20AM +0100, Chander Kashyap wrote:
> In order to support cpuidle through mcpm, suspend and powered-up
> callbacks are required in mcpm platform code.
> Hence populate the same callbacks.
>
> Signed-off-by: Chander Kashyap
> Signed-off-by: Chander Kashyap
> ---
> Cha
Hi,
On Friday, May 09, 2014 02:02:14 PM Tomasz Figa wrote:
> Hi Arnd,
>
> On 09.05.2014 12:56, Arnd Bergmann wrote:
> > On Friday 11 April 2014, Daniel Lezcano wrote:
> >> No more dependency on the arch code. The platform_data field is used to
> >> set the
> >> PM callback as the other cpuidle
On Fri, May 9, 2014 at 7:29 PM, Rob Clark wrote:
> On Fri, May 9, 2014 at 5:08 AM, Andrzej Hajda wrote:
>> On 05/08/2014 08:24 PM, Rob Clark wrote:
>>> On Thu, May 8, 2014 at 2:41 AM, Andrzej Hajda wrote:
On 05/05/2014 09:52 PM, Ajay Kumar wrote:
> This patchset is based on exynos-drm-n
implement basic panel controls as a drm_bridge so that
the existing bridges can make use of it.
The driver assumes that it is the last entity in the bridge chain.
Signed-off-by: Ajay Kumar
---
.../bindings/drm/bridge/bridge_panel.txt | 45
drivers/gpu/drm/bridge/Kconfig
On Fri, May 09, 2014 at 08:12:47PM +0530, Naveen Krishna Ch wrote:
> On 9 May 2014 19:21, Mark Brown wrote:
> > On Fri, May 09, 2014 at 05:50:00PM +0530, Naveen Krishna Ch wrote:
> >> DRM related drivers like DP, FIMD, HDMI, Mixer wants to be probed ASAP
> >> during the boot.
> >> The real proble
Add helper functions to create bridge chain and to call the
corresponding next_bridge functions.
Signed-off-by: Ajay Kumar
Suggested-by: Rob Clark
---
include/drm/drm_crtc.h | 72
1 file changed, 72 insertions(+)
diff --git a/include/drm/drm_c
use drm_bridge helpers to demonstrate chaining of bridges(ptn3460 and
bridge_panel) with exynos_dp encoder.
Signed-off-by: Ajay Kumar
---
drivers/gpu/drm/bridge/ptn3460.c| 60 +++
drivers/gpu/drm/exynos/exynos_dp_core.c | 25 -
include/drm/brid
This patchset is based on exynos-drm-next-todo branch of Inki Dae's tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git
Inital discussion can be found at:
http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg30008.html
As Rob suggested, I have added few stati
Hello Mark,
On 9 May 2014 19:21, Mark Brown wrote:
> On Fri, May 09, 2014 at 05:50:00PM +0530, Naveen Krishna Ch wrote:
>> On 24 April 2014 21:55, Mark Brown wrote:
>
>> >> Such solution has been proposed by Mark Brown to fix the problem of
>> >> the regulators not beeing available on the periph
On Fri, May 9, 2014 at 5:08 AM, Andrzej Hajda wrote:
> On 05/08/2014 08:24 PM, Rob Clark wrote:
>> On Thu, May 8, 2014 at 2:41 AM, Andrzej Hajda wrote:
>>> On 05/05/2014 09:52 PM, Ajay Kumar wrote:
This patchset is based on exynos-drm-next-todo branch of Inki Dae's tree
at:
git://
Adding support to enable/disable VBUS controlled by a
regulator, to enable vbus supply on the port.
Signed-off-by: Vivek Gautam
---
Changes from v7:
- Rebased on top of [PATCH v8 1/2] phy: Add new Exynos5 USB 3.0 PHY driver.
drivers/phy/phy-exynos5-usbdrd.c | 32
Add a new driver for the USB 3.0 PHY on Exynos5 series of SoCs.
The new driver uses the generic PHY framework and will interact
with DWC3 controller present on Exynos5 series of SoCs.
Also, created a new header file in linux/mfd/syscon/ for
Exynos5 SoCs and put the required PMU offset definitions
On Fri, May 9, 2014 at 4:21 PM, Vivek Gautam wrote:
> Hi Sylwester,
>
>
> On Fri, May 9, 2014 at 3:43 PM, Sylwester Nawrocki
> wrote:
>> Hi Vivek,
>>
>> On 08/05/14 11:03, Vivek Gautam wrote:
>> diff --git a/Documentation/devicetree/bindings/phy/samsung-phy.txt
>> b/Documentation/devicet
On Fri, May 09, 2014 at 05:50:00PM +0530, Naveen Krishna Ch wrote:
> On 24 April 2014 21:55, Mark Brown wrote:
> >> Such solution has been proposed by Mark Brown to fix the problem of
> >> the regulators not beeing available on the peripheral device probe():
> >> http://lists.infradead.org/piperm
On 05/09/14 13:49, Tomasz Figa wrote:
Hi Kukjin,
Hi Tomasz,
On 09.05.2014 04:14, Kukjin Kim wrote:
Tomasz Figa wrote:
Hi Sachin,
On 08.05.2014 06:16, Sachin Kamat wrote:
Instead of hardcoding the SYSRAM details for each SoC,
pass this information through device tree (DT) and make
the cod
From: Andrew Bresticker
The RPMB partition should only be accessed through the RPMB ioctls
and not through read()/write(). This patch makes mmc_blk_open()
reject open attempts to the RPMB partition in read or write mode.
Signed-off-by: Andrew Bresticker
Signed-off-by: Yuvaraj Kumar C D
---
d
This patch adds sysreg-syscon node to exynos5250 and exynos5420 device
tree, to access System Register's registers using syscon driver.
Signed-off-by: Kamil Debski
[gautam.vi...@samsung.com: Split this syreg-syscon dts entry from
dts: Add usb2phy to Exynos 5250 patch]
[gautam.vi...@samsung.com: a
From: Kamil Debski
Add support to PHY of USB2 of the Exynos 5250 SoC.
Signed-off-by: Kamil Debski
[gautam.vi...@samsung.com: Split the usb phy entries from
syscon entries from earlier patch: dts: Add usb2phy to Exynos 5250]
[gautam.vi...@samsung.com: Added phy entry for OHCI also along with EHC
Add required device node for usb2phy to let enable USB 2.0
support.
Signed-off-by: Vivek Gautam
---
Changes from v1:
- Added node references for the phy node.
arch/arm/boot/dts/exynos5420.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5420.dtsi
Add required device node for ehci and ohci controllers to
enable USB 2.0 support.
Signed-off-by: Vivek Gautam
---
Changes from v1:
- Removed 'phy-names' property from the 'port'.
- Added node references for the nodes.
arch/arm/boot/dts/exynos5420.dtsi | 30 ++
1
Based on 'for-next' branch of Kgene's linux-samsung tree.
These patches are as per discussions on the driver side patches
which have already been acked. [1]
Changes from v1:
- Rebase on 'for-next' branch.
- Removed 'phy-names' property as per discuusion in the driver patches. [1]
V1 of this ser
On 05/09/2014 03:09 PM, Laurent Pinchart wrote:
> Hi Arun,
>
> Thank you for the patch. We're slowly getting there :-)
>
> On Thursday 08 May 2014 17:19:15 Arun Kumar K wrote:
>> This event indicates that the video device has encountered
>> a source parameter change during runtime. This can typic
On 05/09/14 19:56, Arnd Bergmann wrote:
On Friday 11 April 2014, Daniel Lezcano wrote:
No more dependency on the arch code. The platform_data field is used to set the
PM callback as the other cpuidle drivers.
Signed-off-by: Daniel Lezcano
Reviewed-by: Viresh Kumar
Reviewed-by: Bartlomiej Zolnie
Hi Arun,
Thank you for the patch. We're slowly getting there :-)
On Thursday 08 May 2014 17:19:15 Arun Kumar K wrote:
> This event indicates that the video device has encountered
> a source parameter change during runtime. This can typically be a
> resolution change detected by a video decoder OR
The MUX/GATE register for XCLKOUT doesn't resides within PMU domain,
this can be accessed through a regmap provided by syscon driver. Adding
another clock provider to handle regmap based handing of XCLKOUT.
Dependency:
1. [PATCH v3] mfd: syscon: Support early initialization
http://article.gmane.or
A new clock provider has been added to configure the XCLKOUT debug
clock. Added a minimal implemetation for Exynos5420 clock driver.
Right now, only one valid parent clock from XCLKOUT is defined
in existing clock driver. The driver will be updated later for other
for other parent clocks.
Signed-
All SoC in Exynos-series have a clock with name XCLKOUT to provide
debug information about various clocks available in the SoC. The register
controlling the MUX and GATE of this clock is provided within PMU domain.
Since PMU domain can't be dedicatedly mapped by every driver, the register
needs to
XCLKOUT in Exynos5420/Exynos5250 is controlled through a register in
PMU domain. Pass pmu-syscon handle to the clock driver so that XCLKOUT
can be properly configured.
Signed-off-by: Tushar Behera
CC: Kukjin Kim
---
arch/arm/boot/dts/exynos5250.dtsi |1 +
arch/arm/boot/dts/exynos5420.dtsi |
A new clock provider has been added to configure the XCLKOUT debug
clock. Added a minimal implemetation for Exynos5420 clock driver.
Right now, only one valid parent clock from XCLKOUT is defined
in existing clock driver. The driver will be updated later for other
for other parent clocks.
Signed-
From: Alim Akhtar
Exynos5800 clock structure is mostly similar to 5420 with only
a small delta changes. So the 5420 clock file is re-used for
5800 also. The common clocks for both are seggreagated and few
clocks which are different for both are separately initialized.
Signed-off-by: Alim Akhtar
Adds support for google peach-pi board having the
Exynos5800 SoC.
Signed-off-by: Arun Kumar K
Signed-off-by: Doug Anderson
Reviewed-by: Tomasz Figa
---
Changes from v1
- Updated memory node with a safe size of 2GB
---
arch/arm/boot/dts/Makefile|3 +-
arch/arm/boot/dts/exyno
Most of the nodes of exynos5420 remains same for exynos5800.
So the exynos5420.dtsi is included in exynos5800 and the changed
node properties will be overriden.
Signed-off-by: Arun Kumar K
Reviewed-by: Tomasz Figa
Acked-by: Olof Johansson
---
No changes from v1
---
arch/arm/boot/dts/exynos5800
Exynos5800 is a derivative of Exynos5420 with higher
clock speeds and most other IP blocks remaining the same
except for a few.
This patchset is based on Kukjin's for-next branch
and Tomasz's samsung-next branch containing Shaik's clock
cleanup series for 5420.
Changes from v1
--
- Re
Hello Mark,
On 24 April 2014 21:55, Mark Brown wrote:
> On Thu, Apr 24, 2014 at 08:18:36PM +0530, Naveen Krishna Chatradhi wrote:
>> This patch moves initialization code to subsys_initcall() to ensure
>> that the i2c bus is available early so the regulators can be quickly
>> probed and available
Hi Arnd,
On 09.05.2014 12:56, Arnd Bergmann wrote:
> On Friday 11 April 2014, Daniel Lezcano wrote:
>> No more dependency on the arch code. The platform_data field is used to set
>> the
>> PM callback as the other cpuidle drivers.
>>
>> Signed-off-by: Daniel Lezcano
>> Reviewed-by: Viresh Kumar
On Thursday 08 May 2014, Guenter Roeck wrote:
> On Thu, May 08, 2014 at 04:46:51PM +0200, Arnd Bergmann wrote:
> > These are a bunch of fixes I had to do to get all randconfig
> > configurations on ARM working. Most of these are really old
> > bugs, but there are also some new ones. I don't think a
On 04/24/2014 11:48 AM, Amit Kachhap wrote:
> On 4/14/14, Tushar Behera wrote:
>> Currently the threshold limits are updated in 2 stages, once for all
>> software trigger levels and again for hardware trip point.
> I guess the first stage is bootloader as could not find this in this file.
> Anyway
As we are preparing to enable multiplatform support on EXYNOS,
we can no longer include mach/*.h or plat/*.h headers from device
drivers.
The s5p-sss driver was just enabled for EXYNOS when it used to
be used only on s5pv210, and it includes two samsung platform
specific header files for historic
On Friday 11 April 2014, Daniel Lezcano wrote:
> No more dependency on the arch code. The platform_data field is used to set
> the
> PM callback as the other cpuidle drivers.
>
> Signed-off-by: Daniel Lezcano
> Reviewed-by: Viresh Kumar
> Reviewed-by: Bartlomiej Zolnierkiewicz
This has just s
On Tue, 06 May 2014 20:05:14 +0200, Tomasz Figa wrote:
> On 27.04.2014 09:37, Shaik Ameer Basha wrote:
> > From: Cho KyongHo
> >
> > Some master device descriptor like fimc-is which is an abstraction
> > of very complex H/W may have multiple System MMUs. For those devices,
> > the design of the li
Hi Sylwester,
On Fri, May 9, 2014 at 3:43 PM, Sylwester Nawrocki
wrote:
> Hi Vivek,
>
> On 08/05/14 11:03, Vivek Gautam wrote:
> diff --git a/Documentation/devicetree/bindings/phy/samsung-phy.txt
> b/Documentation/devicetree/bindings/phy/samsung-phy.txt
> >>> index b422e38..51efe4c
The i2c drivers for ddc and hdmiphy are already removed from build
and instead, i2c clients registered via devicetree are used. So this
patch removes the unnecessary i2c drivers.
Signed-off-by: Seung-Woo Kim
---
drivers/gpu/drm/exynos/exynos_ddc.c | 63 --
drive
+ Jingoo Han.
On 9 May 2014 15:39, Rahul Sharma wrote:
> From: Rahul Sharma
>
> Add nodes for fimd and dp controller for exynos5250 based snow
> and exynos5420 based peach-pit board.
>
> This series is based on Kukjin Kims, for-next branch.
>
> V3:
> 1) Dropped 1 patch "ARM: dts: move dp hpd lin
Hi Vivek,
On 08/05/14 11:03, Vivek Gautam wrote:
diff --git a/Documentation/devicetree/bindings/phy/samsung-phy.txt
b/Documentation/devicetree/bindings/phy/samsung-phy.txt
>>> index b422e38..51efe4c 100644
>>> --- a/Documentation/devicetree/bindings/phy/samsung-phy.txt
>>
From: Rahul Sharma
Enable dp-controller for peach-pit board.
Signed-off-by: Rahul Sharma
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 36
1 file changed, 36 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5420-peach-pit.dts
b/arch/arm/boot/dts/exynos5420
From: Rahul Sharma
Enable fimd for peach-pit board.
Signed-off-by: Rahul Sharma
---
arch/arm/boot/dts/exynos5420-peach-pit.dts |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5420-peach-pit.dts
b/arch/arm/boot/dts/exynos5420-peach-pit.dts
index fae33dd..f75
From: Rahul Sharma
Enable dp-controller for snow board.
Signed-off-by: Rahul Sharma
---
arch/arm/boot/dts/exynos5250-snow.dts | 29 +
1 file changed, 29 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5250-snow.dts
b/arch/arm/boot/dts/exynos5250-snow.dts
inde
From: Rahul Sharma
Add nodes for fimd and dp controller for exynos5250 based snow
and exynos5420 based peach-pit board.
This series is based on Kukjin Kims, for-next branch.
V3:
1) Dropped 1 patch "ARM: dts: move dp hpd line to the board file for
exynos5420".
2) Extra blank lines for readabili
From: Rahul Sharma
Enable fimd node for snow board.
Signed-off-by: Rahul Sharma
---
arch/arm/boot/dts/exynos5250-snow.dts |6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5250-snow.dts
b/arch/arm/boot/dts/exynos5250-snow.dts
index 1ce1088..796954c 100644
--
[CCing DT maintainers]
On 08.05.2014 11:03, Vivek Gautam wrote:
> On Thu, May 8, 2014 at 11:35 AM, Vivek Gautam
> wrote:
>> Hi Sylwester,
>>
>>
>> On Tue, May 6, 2014 at 7:57 PM, Sylwester Nawrocki
>> wrote:
>>> On 28/04/14 08:17, Vivek Gautam wrote:
Add a new driver for the USB 3.0 PHY on
On 05/08/2014 08:24 PM, Rob Clark wrote:
> On Thu, May 8, 2014 at 2:41 AM, Andrzej Hajda wrote:
>> On 05/05/2014 09:52 PM, Ajay Kumar wrote:
>>> This patchset is based on exynos-drm-next-todo branch of Inki Dae's tree at:
>>> git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git
>>>
On 9 May 2014 13:47, Tomasz Figa wrote:
> Hi Chander,
>
> On 09.05.2014 09:50, Chander Kashyap wrote:
>> On 5 May 2014 09:37, Chander Kashyap wrote:
>>> On 25 April 2014 11:14, Chander Kashyap wrote:
The address of cpu power registers in pmu is based on cpu number
offsets. This functio
Hi Vivek,
On 05.05.2014 07:02, Vivek Gautam wrote:
> From: Kamil Debski
>
> Add the phy provider, supplied by new Exynos-usb2phy using
> Generic phy framework.
> Keeping the support for older USB phy intact right now, in order
> to prevent any functionality break in absence of relevant
> device
Hi Vivek,
On 05.05.2014 07:02, Vivek Gautam wrote:
> Add support to consume phy provided by Generic phy framework.
> Keeping the support for older usb-phy intact right now, in order
> to prevent any functionality break in absence of relevant
> device tree side change for ohci-exynos.
> Once we mov
Hi Chander,
On 09.05.2014 09:50, Chander Kashyap wrote:
> On 5 May 2014 09:37, Chander Kashyap wrote:
>> On 25 April 2014 11:14, Chander Kashyap wrote:
>>> The address of cpu power registers in pmu is based on cpu number
>>> offsets. This function calculate the same. This is essentially
>>> requ
Hi Tomasz,
On 05/09/2014 05:01 PM, Tomasz Figa wrote:
> On 09.05.2014 08:49, Chanwoo Choi wrote:
>> Hi Tomasz,
>>
>> On 04/26/2014 08:38 PM, Tomasz Figa wrote:
>>> On 26.04.2014 02:51, Tomasz Figa wrote:
Hi Chanwoo,
On 25.04.2014 03:16, Chanwoo Choi wrote:
> From: Tomasz Figa
>
On 09.05.2014 09:10, Chanwoo Choi wrote:
> Hi Tomasz,
>
> On 05/09/2014 02:02 PM, Tomasz Figa wrote:
>> Hi Chanwoo,
>>
>> On 09.05.2014 03:06, Chanwoo Choi wrote:
>>> On 04/26/2014 09:51 AM, Tomasz Figa wrote:
On 25.04.2014 03:16, Chanwoo Choi wrote:
>>
>> [snip]
>>
> +cpus {
>
On 09.05.2014 08:49, Chanwoo Choi wrote:
> Hi Tomasz,
>
> On 04/26/2014 08:38 PM, Tomasz Figa wrote:
>> On 26.04.2014 02:51, Tomasz Figa wrote:
>>> Hi Chanwoo,
>>>
>>> On 25.04.2014 03:16, Chanwoo Choi wrote:
From: Tomasz Figa
This patch add new exynos3250.dtsi to support Exynos325
On 5 May 2014 09:37, Chander Kashyap wrote:
> On 25 April 2014 11:14, Chander Kashyap wrote:
>> The address of cpu power registers in pmu is based on cpu number
>> offsets. This function calculate the same. This is essentially
>> required in case of multicluster SoC's e.g Exynos5420.
>>
>> Signed
This patch uses devm_devfreq_add_device()/devm_devfreq_register_opp_notifier()
to control automatically the resource of devfreq.
Signed-off-by: Chanwoo Choi
Cc: Kukjin Kim
Cc: Bartlomiej Zolnierkiewicz
Cc: Wei Yongjun
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-samsung-soc@vger.kernel.o
This patch uses devm_devfreq_add_device()/devm_devfreq_register_opp_notifier()
to control automatically the resource of devfreq.
Signed-off-by: Chanwoo Choi
Cc: Kukjin Kim
Cc: Sachin Kamat
Cc: Bartlomiej Zolnierkiewicz
Cc: Manish Badarkhe
Cc: Abhilash Kesavan
Cc: linux-arm-ker...@lists.infra
Hi, Sonny.
You can discard the my previous some comment.
As you mentioned, this reset sequence is recommended at Synopsys TRM.
Add the minor question.
On 05/09/2014 01:27 PM, Jaehoon Chung wrote:
> Hi, Sonny.
>
> I have checked the Synopsys TRM..
>
> On 05/09/2014 10:34 AM, Sonny Rao wrote:
>>
Hi Tomasz,
On 05/09/2014 02:02 PM, Tomasz Figa wrote:
> Hi Chanwoo,
>
> On 09.05.2014 03:06, Chanwoo Choi wrote:
>> On 04/26/2014 09:51 AM, Tomasz Figa wrote:
>>> On 25.04.2014 03:16, Chanwoo Choi wrote:
>
> [snip]
>
+cpus {
+#address-cells = <1>;
+#size-cells
90 matches
Mail list logo
