Enable rtc and watchdog support for exynos7 SoCs.
Signed-off-by: Abhilash Kesavan
---
arch/arm64/Kconfig |3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 238acff..9bb4e02 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -158,6 +15
Add nodes for 3 mmc channels, 12 i2c channels, rtc, and watchdog
on Exynos7.
Signed-off-by: Naveen Krishna Ch
Signed-off-by: Abhilash Kesavan
---
arch/arm64/boot/dts/exynos/exynos7-espresso.dts | 41
arch/arm64/boot/dts/exynos/exynos7.dtsi | 256 +++
2 files
Adds PMU DT node for exynos7 SoC.
Signed-off-by: Abhilash Kesavan
---
.../devicetree/bindings/arm/samsung/pmu.txt|1 +
arch/arm64/boot/dts/exynos/exynos7.dtsi|5 +
2 files changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/samsung/pmu.txt
From: Naveen Krishna Ch
Add clock support for the watchdog timer, pwm timer and thermal
management unit IPs in Exynos7.
Signed-off-by: Naveen Krishna Ch
Signed-off-by: Abhilash Kesavan
---
drivers/clk/samsung/clk-exynos7.c | 14 ++
include/dt-bindings/clock/exynos7-clk.h |
From: Naveen Krishna Ch
Exynos7 supports 3 MMC channels, add the MMC gate clocks to
support them.
Signed-off-by: Naveen Krishna Ch
Signed-off-by: Abhilash Kesavan
---
.../devicetree/bindings/clock/exynos7-clock.txt| 21 ++
drivers/clk/samsung/clk-exynos7.c | 224 ++
From: Naveen Krishna Ch
Add clock support for the RTC block in Exynos7.
Signed-off-by: Naveen Krishna Ch
Signed-off-by: Abhilash Kesavan
---
.../devicetree/bindings/clock/exynos7-clock.txt|5 ++
drivers/clk/samsung/clk-exynos7.c | 54
include/dt
From: Naveen Krishna Ch
Exynos7 supports 12 I2C channels, add the I2C gate clocks to
support them.
Signed-off-by: Naveen Krishna Ch
Signed-off-by: Abhilash Kesavan
---
drivers/clk/samsung/clk-exynos7.c | 24
include/dt-bindings/clock/exynos7-clk.h | 16 +
Changes since v1:
- Added documentation for input clocks of the newly added CMUs
Following are the dependencies:
1) dts, kbuild: Implement support for dtb vendor subdirs patchset
http://comments.gmane.org/gmane.linux.kbuild.devel/12131
2) arch: arm64: Enable support for Samsung Exynos7 So
ping!
On Fri, Oct 10, 2014 at 6:18 PM, Ajay Kumar wrote:
> This series is based on exynos-drm-next branch of Inki Dae's tree at:
> git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git
>
> DECON(Display and Enhancement Controller) is the new IP
> in exynos7 SOC for generating video
Register with kernel poweroff handler instead of setting pm_power_off
directly. Always use register_power_off_handler_simple as there is no
indication that more than one poweroff handler is registered.
If the poweroff handler only resets the system or puts the CPU in sleep mode,
select the fallbac
Hi Javier,
On 10/21/2014 06:05 AM, Javier Martinez Canillas wrote:
> This reverts commit b7cde7078d2344073c310aa65fc2b0a845d2cb5b
> ("mfd: sec-core: Prepare regulators for suspend state to reduce
> power-consumption")
>
> Commit b7cde7078d23 called regulator_suspend_prepare() to prepare the
> re
Hello Doug,
On 10/20/2014 11:40 PM, Doug Anderson wrote:
> Javier,
>
> On Mon, Oct 20, 2014 at 2:05 PM, Javier Martinez Canillas
> wrote:
>> The regulator framework has a set of helpers functions to be used when
>> the system is entering and leaving from suspend but these are not called
>> on Ex
Javier,
On Mon, Oct 20, 2014 at 2:05 PM, Javier Martinez Canillas
wrote:
> This reverts commit b7cde7078d2344073c310aa65fc2b0a845d2cb5b
> ("mfd: sec-core: Prepare regulators for suspend state to reduce
> power-consumption")
>
> Commit b7cde7078d23 called regulator_suspend_prepare() to prepare th
Javier,
On Mon, Oct 20, 2014 at 2:05 PM, Javier Martinez Canillas
wrote:
> The regulator framework has a set of helpers functions to be used when
> the system is entering and leaving from suspend but these are not called
> on Exynos platforms. This means that the .set_suspend_* function handlers
The regulator framework has a set of helpers functions to be used when
the system is entering and leaving from suspend but these are not called
on Exynos platforms. This means that the .set_suspend_* function handlers
defined by regulator drivers are not called when the system is suspended.
Sugges
This reverts commit b7cde7078d2344073c310aa65fc2b0a845d2cb5b
("mfd: sec-core: Prepare regulators for suspend state to reduce
power-consumption")
Commit b7cde7078d23 called regulator_suspend_prepare() to prepare the
regulators for a suspend state. But it did from the device pm suspend
handler whil
Hello,
This series add support for Exynos platforms to prepare regulators for
system suspend. The regulator core has a set of helpers functions to be
used when the system is entering and leaving from a suspend state but
currently there is only one user in mainline.
This user is drivers/mfd/sec-co
Hello Mark,
On 10/20/2014 09:56 PM, Mark Brown wrote:
> On Mon, Oct 20, 2014 at 09:50:57PM +0200, Javier Martinez Canillas wrote:
>> On 10/20/2014 07:36 PM, Doug Anderson wrote:
>
>> > I guess I was just trying to follow the suggestion that was in the
>> > regulator code:
>> > http://lxr.free-ele
On Mon, Oct 20, 2014 at 09:50:57PM +0200, Javier Martinez Canillas wrote:
> On 10/20/2014 07:36 PM, Doug Anderson wrote:
> > I guess I was just trying to follow the suggestion that was in the
> > regulator code:
> > http://lxr.free-electrons.com/source/drivers/regulator/core.c#L3699
> > that says
[adding Rafael Wysocki to cc as Suspend-to-RAM maintainer]
On 10/20/2014 07:36 PM, Doug Anderson wrote:
> Javier,
>
> On Mon, Oct 20, 2014 at 9:58 AM, Javier Martinez Canillas
> wrote:
>>> It turns out that regulator_suspend_finish() actually returns an error
>>> code. Could you print a warning
Javier,
On Mon, Oct 20, 2014 at 9:58 AM, Javier Martinez Canillas
wrote:
>> It turns out that regulator_suspend_finish() actually returns an error
>> code. Could you print a warning if you see it?
>>
>
> Yes, I noticed this when looking at Chris patch for Rockchip but didn't
> re-spin
> because
[adding Chris Zong as cc who posted a similar patch for Rockchip]
Hello Doug,
On 10/20/2014 06:26 PM, Doug Anderson wrote:
> Javier,
>
> On Thu, Oct 16, 2014 at 3:13 AM, Javier Martinez Canillas
> wrote:
>> The regulator framework has a set of helpers functions to be used when
>> the system is
Javier,
On Thu, Oct 16, 2014 at 3:13 AM, Javier Martinez Canillas
wrote:
> The regulator framework has a set of helpers functions to be used when
> the system is entering and leaving from suspend but these are not called
> on Exynos platforms. This means that the .set_suspend_* function handlers
Hi,
Here is Samsung DT updates for v3.19, please pull.
Thanks,
Kukjin
---
The following changes since commit f114040e3ea6e07372334ade75d1ee0775c355e1:
Linux 3.18-rc1 (2014-10-19 18:08:38 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kgene/l
Hi,
Same, I've just rebased for Samsung PM updates for v3.19.
Please pull.
Thanks,
Kukjin
---
The following changes since commit f114040e3ea6e07372334ade75d1ee0775c355e1:
Linux 3.18-rc1 (2014-10-19 18:08:38 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linu
Hi,
Here is 1st round of Samsung updates for v3.19 and actually it has been
sent out to arm-soc for v3.18 before but as you know missed. I've just
rebased the branch on top of v3.18-rc1, please pull.
Thanks,
Kukjin
The following changes since commit f114040e3ea6e07372334ade75d1ee0775c3
The max77802 PMIC regulators output can be configured in one of two
modes: Output ON (normal) and Output ON in Low Power Mode. Some of
the regulators support their operating mode to be changed on startup
or by consumers when the system is running while others only support
their operating mode to be
Some regulators from the max77802 PMIC support to be configured in one
of two operating mode: Output ON (normal) and Output On Low Power Mode.
Not all regulators support these two modes and for some of them, the
mode can be changed while the system is running in normal operation
while others only s
The regulator core now has support to choose if a regulator
has to be enabled or disabled during system suspend and also
the max77802 driver supports changing the regulator operating
mode during runtime and when the system enters into sleep mode.
To lower power during suspend, configure the regula
of_get_regulation_constraints() calls of_get_child_by_name() to find the
regulator-state-{mem,disk} child nodes for each regulator. This function
increments the device node reference counter but this is not decremented
once the function is done using the node.
Fix that by calling of_node_put() aft
Hello Mark,
This is the third version of the series that adds operating modes
support for the regulators in the max77802 PMIC. This version uses the
standard regulator suspend states bindings as you suggested and also
drops the patches already picked by you from the first [0] and second [1]
versio
Some regulators can run on different operating modes (opmodes). This
allows systems to choose the most efficient opmode for each regulator.
This patch adds a "regulator-initial-mode" property to configure at
startup the operating mode for the regulators that support changing
its mode during normal
On 20.10.2014 13:48, Thomas Abraham wrote:
> Hi Tomasz,
>
> On Mon, Oct 20, 2014 at 5:05 PM, Tomasz Figa wrote:
>> On 20.10.2014 13:41, Thomas Abraham wrote:
>>> Changes since v10:
>>> - Rebased on top of v3.18-rc1
>>>
>>> This patch series removes the use of Exynos4210 and Exynos5250 specific
Hi Linus,
On Sun, Oct 12, 2014 at 12:27 AM, Tomasz Figa wrote:
> Abhilash, Linus,
>
> On 09.10.2014 15:54, Abhilash Kesavan wrote:
>> Changes since v4:
>> - Rebased over Tomasz Figa's pinctrl clean-up patches[1]
>>
>> Changes since v3:
>> - Changed variable name from exynos_wkup_irq_c
Hi Vivek,
On Mon, Oct 20, 2014 at 3:19 PM, Vivek Gautam wrote:
> Hi Abhilash,
>
>
> On Fri, Oct 17, 2014 at 9:41 PM, Abhilash Kesavan
> wrote:
>> From: Naveen Krishna Ch
>>
>> Exynos7 supports 3 MMC channels, add the MMC gate clocks to
>> support them.
>>
>> Signed-off-by: Naveen Krishna Ch
>
Hi Kukjin,
On Wed, Oct 1, 2014 at 10:12 PM, Abhilash Kesavan wrote:
> Remove usage of CONFIG_SERIAL_SAMSUNG_UARTS symbol from platform
> specific code.
>
> Signed-off-by: Abhilash Kesavan
> Reviewed-by: Tomasz Figa
Can you please pick this up if it looks OK ?
Abhilash
> ---
> Changes in v2:
>
Hi,
Eduaro/Amit, any comments on this series?
Could it be merged for v3.19?
[ Currently this series conflicts with "[PATCH] thermal: exynos: fix IRQ
clearing on TMU initialization" patch so I'm planning to refresh it but
it would be great to get some feedback first. ]
Best regards,
--
Bartl
Hi,
Eduaro, could you please merge this patch?
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
On Friday, October 03, 2014 06:17:17 PM Bartlomiej Zolnierkiewicz wrote:
> * Factor out code for clearing raised IRQs from exynos_tmu_work() to
> exynos_t
Hi,
Eduardo, could you please merge this patch?
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
On Thursday, September 11, 2014 03:00:49 PM Bartlomiej Zolnierkiewicz wrote:
> In exynos5260_tmu_registers tmu_ctrl entry is erroneously
> assigned twice.
This patch add exynos3250 compatible string to exynos_cpufreq_matches
for supporting generic cpufreq driver on Exynos3250.
Cc: Kukjin Kim
Signed-off-by: Chanwoo Choi
Acked-by: Kyungmin Park
---
arch/arm/mach-exynos/exynos.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-exyn
This patch add CPU clock configuration data and instantiate the CPU clock type
for Exynos3250 to support Samsung specific cpu-clock type.
Cc: Tomasz Figa
Cc: Sylwester Nawrocki
Signed-off-by: Chanwoo Choi
Acked-by: Kyungmin Park
---
drivers/clk/samsung/clk-cpu.h| 4
drivers/clk/
This patch add CPU operating points which include CPU frequency and regulator
voltage to use generic cpufreq drivers.
Cc: Kukjin Kim
Cc: Tomasz Figa
Signed-off-by: Chanwoo Choi
Acked-by: Kyungmin Park
Reviewed-by: Thomas Abraham
---
arch/arm/boot/dts/exynos3250.dtsi | 15 +++
1 f
This patch update clock flags related to CPU with read only flag
to use cpu-clock type.
Cc: Tomasz Figa
Cc: Sylwester Nawrocki
Signed-off-by: Chanwoo Choi
Acked-by: Kyungmin Park
---
drivers/clk/samsung/clk-exynos3250.c | 30 --
1 file changed, 20 insertions(+), 10
This patchset use cpufreq-dt driver to support Exynos3250 cpufreq and tested it
on Exynos3250-based Rinato board.
Changes from v3:
- This patchset is based on 3.18-rc1 with new patchset[3] of Thomas Abraham
[3] [PATCH v11 0/6] cpufreq: use generic cpufreq drivers for exynos platforms
- http://
Exynos4210 and Exynos5250 based platforms have switched over to use generic
cpufreq drivers for cpufreq functionality. So the Exynos specific cpufreq
drivers for these platforms can be removed.
Cc: Bartlomiej Zolnierkiewicz
Signed-off-by: Thomas Abraham
Acked-by: Viresh Kumar
Tested-by: Javier
Hi Tomasz,
On Mon, Oct 20, 2014 at 5:05 PM, Tomasz Figa wrote:
> On 20.10.2014 13:41, Thomas Abraham wrote:
>> Changes since v10:
>> - Rebased on top of v3.18-rc1
>>
>> This patch series removes the use of Exynos4210 and Exynos5250 specific
>> cpufreq
>> drivers and enables the use of cpufreq-dt
On Mon, Oct 20, 2014 at 5:02 PM, Viresh Kumar wrote:
> On 20 October 2014 17:11, Thomas Abraham wrote:
>> Exynos4210 and Exynos5250 based platforms have switched over to use generic
>> cpufreq drivers for cpufreq functionality. So the Exynos specific cpufreq
>> drivers for these platforms can be
On 20.10.2014 13:41, Thomas Abraham wrote:
> Changes since v10:
> - Rebased on top of v3.18-rc1
>
> This patch series removes the use of Exynos4210 and Exynos5250 specific
> cpufreq
> drivers and enables the use of cpufreq-dt driver for these platforms. This
> series also enables cpufreq support
On 20 October 2014 17:11, Thomas Abraham wrote:
> Exynos4210 and Exynos5250 based platforms have switched over to use generic
> cpufreq drivers for cpufreq functionality. So the Exynos specific cpufreq
> drivers for these platforms can be removed.
>
> Cc: Bartlomiej Zolnierkiewicz
> Signed-off-by
Exynos4210 and Exynos5250 based platforms have switched over to use generic
cpufreq drivers for cpufreq functionality. So the Exynos specific cpufreq
drivers for these platforms can be removed.
Cc: Bartlomiej Zolnierkiewicz
Signed-off-by: Thomas Abraham
Acked-by: Viresh Kumar
Tested-by: Javier
With some of the Exynos SoCs switched over to use the generic CPUfreq drivers,
the unused clock aliases can be removed. In addition to this, the individual
clock blocks which are now encapsulated with the consolidate CPU clock type
can now be marked with read-only flags.
Cc: Tomasz Figa
Signed-of
The new CPU clock type allows the use of generic CPUfreq drivers. So for
Exynos4210/5250, switch to using generic cpufreq driver. For Exynos5420,
which did not have CPUfreq driver support, enable the use of generic
CPUfreq driver.
Suggested-by: Tomasz Figa
Cc: Kukjin Kim
Signed-off-by: Thomas Ab
For Exynos 4210/5250/5420 based platforms, add CPU operating points and CPU
regulator supply properties for migrating from Exynos specific cpufreq driver
to using generic cpufreq drivers.
Cc: Kukjin Kim
Cc: Doug Anderson
Cc: Javier Martinez Canillas
Cc: Andreas Faerber
Cc: Sachin Kamat
Signed
With the addition of the new Samsung specific cpu-clock type, the
arm clock can be represented as a cpu-clock type. Add the CPU clock
configuration data and instantiate the CPU clock type for Exynos4210,
Exynos5250 and Exynos5420.
Cc: Tomasz Figa
Signed-off-by: Thomas Abraham
Acked-by: Mike Turq
The CPU clock provider supplies the clock to the CPU clock domain. The
composition and organization of the CPU clock provider could vary among
Exynos SoCs. A CPU clock provider can be composed of clock mux, dividers
and gates. This patch defines a new clock type for CPU clock provider and
adds infr
Changes since v10:
- Rebased on top of v3.18-rc1
This patch series removes the use of Exynos4210 and Exynos5250 specific cpufreq
drivers and enables the use of cpufreq-dt driver for these platforms. This
series also enables cpufreq support for Exynos5420 using arm_big_little cpufreq
driver.
This
From: Tomasz Figa
This patch adds stdout-path property to chosen nodes of Exynos4 boards
to enable use of earlycon feature without the need to hardcode port
number in kernel itself.
Signed-off-by: Tomasz Figa
Signed-off-by: Marek Szyprowski
---
arch/arm/boot/dts/exynos4210-origen.dts
This patchset adds support for early console defined in device tree. As
an example, DTS files for all Exynos4 based machines are updated with
the correct value for common chosen/sdtout property.
To get it fully functional on ARM architecture, additional improvements
(support for early_ioremap) are
From: Tomasz Figa
This patch adds support for early console initialized from device tree
and kernel command line to all variants of Samsung serial driver.
Signed-off-by: Tomasz Figa
[mszyprow: added support for command line based initialization,
fixed comments, added documentation]
S
This patch moves udc initialization from pullup() method to
s3c_hsotg_udc_start(), so that method ends with hardware fully
initialized and left in soft-disconnected state. After this change, the
pullup() method simply clears soft-disconnect start() when called with
is_on=1. For completeness, a call
This patch fixes probe function to match the pattern used elsewhere in
the driver, where power regulators are turned off as the last element in
the device shutdown procedure.
Signed-off-by: Marek Szyprowski
---
drivers/usb/dwc2/gadget.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
di
Hello,
On 2014-10-16 15:42, Felipe Balbi wrote:
On Thu, Oct 16, 2014 at 02:58:04PM +0200, Marek Szyprowski wrote:
This patch moves calls to phy enable/disable out of spinlock protected
blocks in device suspend/resume to fix incorrect caller context. Phy
related functions must not be called from
This patch removes duplicated code and sets last_rst variable in the
function which does the hardware reset.
Signed-off-by: Marek Szyprowski
---
drivers/usb/dwc2/gadget.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/dwc2/gadget.c b/drivers/usb/dwc2/gadget.
This patch changes s3c_hsotg_core_init function to leave hardware in
soft disconnect mode, so the moment of coupling the hardware to the usb
bus can be later controlled by the separate functions for enabling and
disabling soft disconnect mode. This patch is a preparation to rework
pullup() method.
udc_stop() should clear ->driver pointer unconditionally to let the UDC
framework to work correctly with both registering/unregistering gadgets
and enabling/disabling gadgets by writing to
/sys/class/udc/*hsotg/soft_connect interface.
Signed-off-by: Marek Szyprowski
---
drivers/usb/dwc2/gadget.c
Hello,
On 2014-10-16 15:38, Felipe Balbi wrote:
On Thu, Oct 16, 2014 at 02:58:02PM +0200, Marek Szyprowski wrote:
This patch changes s3c_hsotg_core_init function to leave hardware in
soft disconnect mode, so the actual moment of coupling the hardware to
the usb bus can be later controlled by th
This patch moves phy enable/disable calls from pullup() method to
udc_start/stop functions. This solves the issue related to limited caller
context for PHY functions, because they cannot be called from non-sleeping
context. This is also a preparation for using soft-disconnect feature of
udc control
This patch moves calls to phy enable/disable out of spinlock protected
blocks in device suspend/resume to fix incorrect caller context. Phy
related functions must not be called from atomic context. To protect
device internal state from a race during suspend, a call to
s3c_hsotg_core_disconnect() is
Excessive debug messages might cause timing issues that prevent correct
usb enumeration. This patch hides information about USB bus reset to let
driver enumerate fast enough to avoid making host angry. This fixes
endless enumeration and usb reset loop observed with some Linux hosts.
Signed-off-by:
Suspend/resume code assumed that the gadget was always enabled and
connected to usb bus. This means that the actual state of the gadget
(soft-enabled/disabled or connected/disconnected) was not correctly
preserved on suspend/resume cycle. This patch fixes this issue.
Signed-off-by: Marek Szyprowsk
Hi!
This patchset contains a set of fixes to solve vaious minor issues
related to cable connect/disconnect events, pull-up control,
soft-disconnect mode, proper usb phy operation and restoring gadget
state after suspend/resume cycle.
Changes since v1 (http://www.spinics.net/lists/linux-samsung-so
This patch adds a call to s3c_hsotg_disconnect() from 'end session'
interrupt (GOTGINT_SES_END_DET) to correctly notify gadget subsystem
about unplugged usb cable. 'disconnected' interrupt (DISCONNINT) might
look a bit more suitable for this event, but it is asserted only in
host mode, so in device
Exynos7 has core power down state where cores can be powered off independently.
This patch adds support for this state.
Signed-off-by: Chander Kashyap
---
This patch has following dependencies:
- [PATCH v5 0/8] arch: arm64: Enable support for Samsung Exynos7 SoC
http://www
Hi Abhilash,
On Fri, Oct 17, 2014 at 9:41 PM, Abhilash Kesavan wrote:
> From: Naveen Krishna Ch
>
> Exynos7 supports 3 MMC channels, add the MMC gate clocks to
> support them.
>
> Signed-off-by: Naveen Krishna Ch
> Signed-off-by: Abhilash Kesavan
> ---
> .../devicetree/bindings/clock/exynos7
Hi Abhilash,
On Fri, Oct 17, 2014 at 9:41 PM, Abhilash Kesavan wrote:
> From: Naveen Krishna Ch
>
> Add clock support for the RTC block in Exynos7.
>
> Signed-off-by: Naveen Krishna Ch
> Signed-off-by: Abhilash Kesavan
> ---
> .../devicetree/bindings/clock/exynos7-clock.txt|1 +
> dr
75 matches
Mail list logo
