These patches add machine driver to instantiate I2S based realtek's
ALC5631 based sound card on Arndale board.
There are other variants of Audio Daughter Cards for Arndale
Board for which support already exists but there is no support for
Realtek's alc5631 codec based card hence support for
Document the device tree binding for the ALC5631 codec and update vendor
specific prefix for the Realtek.
Signed-off-by: Krishna Mohan Dani krishna...@samsung.com
---
Documentation/devicetree/bindings/sound/rt5631.txt | 41
1 file changed, 41 insertions(+)
create mode
Signed-off-by: Krishna Mohan Dani krishna...@samsung.com
---
sound/soc/codecs/rt5631.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/sound/soc/codecs/rt5631.c b/sound/soc/codecs/rt5631.c
index 1ba27db..d7c3f42 100644
--- a/sound/soc/codecs/rt5631.c
+++
Adding machine driver to instantiate I2S based realtek's ALC5631
sound card on Arndale board.
There are other variants of Audio Daughter Cards for Arndale
Board for which support already exists but there is no support for
Realtek's alc5631 codec hence support for ALC5631 based machine
driver is
Signed-off-by: Krishna Mohan Dani krishna...@samsung.com
---
sound/soc/codecs/Kconfig |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/sound/soc/codecs/Kconfig b/sound/soc/codecs/Kconfig
index a68d173..2d85887 100644
--- a/sound/soc/codecs/Kconfig
+++
Hello,
On 2014-10-25 03:16, Paul Zimmerman wrote:
From: Marek Szyprowski [mailto:m.szyprow...@samsung.com]
Sent: Monday, October 20, 2014 3:46 AM
Suspend/resume code assumed that the gadget was always enabled and
connected to usb bus. This means that the actual state of the gadget
Commit 6e80e3d87549 (ARM: exynos_defconfig: Enable MAX77802)
enabled support for the max77802 regulators but the PMIC also
has a Real-Time-Clock (RTC) and 2-channel 32kHz clock outputs.
Enable the kernel config options to have the drivers for these
devices built-in since they are present in many
Hi,
Changes since v3
1. Dropped patch 3/4 (mfd/regulator: dt-bindings: max77686: Document
regulators off in suspend), applied by Lee Jones.
2. Patch 2/3: Fix missing shift when checking if current opmode is
equal to off in suspend. The shift is various so I added a simple
Add suspend to RAM configuration for max77686 regulators. Some LDOs and
bucks are disabled. This reduces energy consumption during S2R,
approximately from 17 mA to 9 mA.
Additionally remove old and not supported bindings:
- regulator-mem-off
- regulator-mem-idle
- regulator-mem-on
The max77686
Some LDOs of Maxim 77686 PMIC support disabling during system suspend
(LDO{2,6,7,8,10,11,12,14,15,16}). This was already implemented as part
of set_suspend_mode function. In that case the mode was one of:
- disable,
- normal mode,
- low power mode.
However there are no bindings for setting the
Add defines for regulator operating modes which should be more readable,
especially if one does not have Maxim 77686 datasheet.
The patch does not introduce any functional change.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
Suggested-by: Javier Martinez Canillas
Hello Krzysztof,
On 10/27/2014 10:44 AM, Krzysztof Kozlowski wrote:
Some LDOs of Maxim 77686 PMIC support disabling during system suspend
(LDO{2,6,7,8,10,11,12,14,15,16}). This was already implemented as part
of set_suspend_mode function. In that case the mode was one of:
- disable,
-
On pon, 2014-10-27 at 11:08 +0100, Javier Martinez Canillas wrote:
Hello Krzysztof,
On 10/27/2014 10:44 AM, Krzysztof Kozlowski wrote:
Some LDOs of Maxim 77686 PMIC support disabling during system suspend
(LDO{2,6,7,8,10,11,12,14,15,16}). This was already implemented as part
of
On 10/27/2014 11:27 AM, Krzysztof Kozlowski wrote:
Storing opmode in non-shifted form is intuitive also to me. That's way I
slipped the bug in previous version.
Great.
I'll change this to non-shifted opmode. The patch will grow bigger but
the code should be more readable.
Maybe split
On pon, 2014-10-27 at 11:32 +0100, Javier Martinez Canillas wrote:
On 10/27/2014 11:27 AM, Krzysztof Kozlowski wrote:
Storing opmode in non-shifted form is intuitive also to me. That's way I
slipped the bug in previous version.
Great.
I'll change this to non-shifted opmode. The
On 27/10/14 02:11, Chanwoo Choi wrote:
Chanwoo Choi (2):
clk: samsung: exynos4415: Add clocks using common clock framework
clk: samsung: Document binding for Exynos4415 clock controller
Added both to my tree, thanks. In future please put DT binding
documentation first in the series, before
On 10/27/2014 07:39 PM, Sylwester Nawrocki wrote:
On 27/10/14 02:11, Chanwoo Choi wrote:
Chanwoo Choi (2):
clk: samsung: exynos4415: Add clocks using common clock framework
clk: samsung: Document binding for Exynos4415 clock controller
Added both to my tree, thanks. In future please put
From: Tomasz Figa t.f...@samsung.com
Firmware on certain boards (e.g. ODROID-U3) can leave incorrect L2C prefetch
settings configured in registers leading to crashes if L2C is enabled
without overriding them. This patch introduces bindings to enable
prefetch settings to be specified from DT and
From: Tomasz Figa t.f...@samsung.com
On Exynos SoCs it is necessary to resume operation of L2C early in
assembly code, because otherwise certain systems will crash. This patch
adds necessary code to non-secure resume handler.
Signed-off-by: Tomasz Figa t.f...@samsung.com
[rewrote the code
From: Tomasz Figa t.f...@samsung.com
Exynos4 SoCs equipped with an L2C-310 cache controller and running under
secure firmware require certain registers of aforementioned IP to be
accessed only from secure mode. This means that SMC calls are required
for certain register writes. To handle this, an
From: Tomasz Figa t.f...@samsung.com
This patch adds device tree nodes for L2 cache controller present on
Exynos4 SoCs.
Signed-off-by: Tomasz Figa t.f...@samsung.com
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
---
arch/arm/boot/dts/exynos4210.dtsi | 9 +
From: Tomasz Figa t.f...@samsung.com
Certain platforms (i.e. Exynos) might need to set .write_sec callback
from firmware initialization which is happenning in .init_early callback
of machine descriptor. However current code will overwrite the pointer
with whatever is present in machine
From: Tomasz Figa t.f...@samsung.com
Because certain secure hypervisor do not allow writes to individual L2C
registers, but rather expect set of parameters to be passed as argument
to secure monitor calls, there is a need to provide an interface for the
L2C driver to ask the firmware to configure
From: Tomasz Figa t.f...@samsung.com
Certain implementations of secure hypervisors (namely the one found on
Samsung Exynos-based boards) do not provide access to individual L2C
registers. This makes the .write_sec()-based interface insufficient and
provoking ugly hacks.
This patch is first step
This is an updated patchset, which intends to add support for L2 cache
on Exynos4 SoCs on boards running under secure firmware, which requires
certain initialization steps to be done with help of firmware, as
selected registers are writable only from secure mode.
First four patches extend
On Mon, Oct 27, 2014 at 12:05:47PM +0100, Marek Szyprowski wrote:
From: Tomasz Figa t.f...@samsung.com
Firmware on certain boards (e.g. ODROID-U3) can leave incorrect L2C prefetch
settings configured in registers leading to crashes if L2C is enabled
without overriding them. This patch
Hello,
On 2014-10-27 12:14, Russell King - ARM Linux wrote:
On Mon, Oct 27, 2014 at 12:05:47PM +0100, Marek Szyprowski wrote:
From: Tomasz Figa t.f...@samsung.com
Firmware on certain boards (e.g. ODROID-U3) can leave incorrect L2C prefetch
settings configured in registers leading to crashes
Some LDOs of Maxim 77686 PMIC support disabling during system suspend
(LDO{2,6,7,8,10,11,12,14,15,16}). This was already implemented as part
of set_suspend_mode function. In that case the mode was one of:
- disable,
- normal mode,
- low power mode.
However there are no bindings for setting the
Add suspend to RAM configuration for max77686 regulators. Some LDOs and
bucks are disabled. This reduces energy consumption during S2R,
approximately from 17 mA to 9 mA.
Additionally remove old and not supported bindings:
- regulator-mem-off
- regulator-mem-idle
- regulator-mem-on
The max77686
Hi,
Changes since v4
1. New patch: 2/4. Store the current value of opmode in
non-shifted form. Along with changes in defines used for opmodes
this simplifies everything a lot. Suggested by Javier.
2. Drop Javier's review-by from patch 1 because I changed the
defines to
Add defines for regulator operating modes which should be more readable,
especially if one does not have Maxim 77686 datasheet.
The patch does not introduce any functional change.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
Suggested-by: Javier Martinez Canillas
Introduce simple helper for calculating the shift for OPMODE field in
registers. This allows storing the current value of opmode in
non-shifted form and simplifies a little set_suspend_disable and enable
functions. Additionally this will allow adding support LDOs to the
existing
Hello Krzysztof,
On 10/27/2014 01:11 PM, Krzysztof Kozlowski wrote:
Introduce simple helper for calculating the shift for OPMODE field in
registers. This allows storing the current value of opmode in
non-shifted form and simplifies a little set_suspend_disable and enable
functions.
Hello Krzysztof,
On 10/27/2014 01:11 PM, Krzysztof Kozlowski wrote:
Some LDOs of Maxim 77686 PMIC support disabling during system suspend
(LDO{2,6,7,8,10,11,12,14,15,16}). This was already implemented as part
of set_suspend_mode function. In that case the mode was one of:
- disable,
-
On pon, 2014-10-27 at 14:37 +0100, Javier Martinez Canillas wrote:
Hello Krzysztof,
On 10/27/2014 01:11 PM, Krzysztof Kozlowski wrote:
Introduce simple helper for calculating the shift for OPMODE field in
registers. This allows storing the current value of opmode in
non-shifted form and
Hello,
On 2014-10-25 02:35, Paul Zimmerman wrote:
From: Marek Szyprowski [mailto:m.szyprow...@samsung.com]
Sent: Monday, October 20, 2014 3:46 AM
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
Add SDHCI node for supporting the micro SD card. On Trats2 board the
SDHCI does not use sd2_cd pins (gpk2-2) for card detect but gpx3-4
instead.
Power is supplied from LDO21 regulator which in off state is controlled
by external GPIO pin.
Signed-off-by: Krzysztof Kozlowski
Add SDHCI node for supporting the micro SD card. On Trats2 board the
SDHCI does not use sd2_cd pins (gpk2-2) for card detect but gpx3-4
instead.
Power is supplied from LDO21 regulator which in off state is controlled
by external GPIO pin.
Signed-off-by: Krzysztof Kozlowski
Hi,
This patch helps in proper description of max77686 regulators in DTS by
allowing to control them over GPIO. This allows removal of
fixed regulators from DTS which duplicate the description of hardware.
The first five patches are cleanups, including board support removal.
The whole patchset
Remove fixed regulators (duplicating what max77686 provides) and
add GPIO control to max77686 regulators.
This gives the system full control over those regulators. Previously
the state of such regulators was a mixture of what max77686 driver set
over I2C and what regulator-fixed set through GPIO.
The driver is used only on Exynos based boards with DTS support.
Convert the driver to DTS-only version. This simplifies a little the
code:
1. No dead (unused) entries in platform_data structure.
2. More code removed (from all three patches: 34 insertions(+), 107
deletions).
3. Regulator driver
The driver is used only on Exynos4 based boards with DTS support.
Convert the driver to DTS-only version.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
drivers/regulator/max77686.c | 51 +---
1 file changed, 19 insertions(+), 32
The regulator_register() expects array of 'regulator_desc' to be const.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
drivers/regulator/max77686.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/max77686.c b/drivers/regulator/max77686.c
The driver is used only on Exynos based boards with DTS support.
Convert the driver to DTS-only version.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
drivers/regulator/max77802.c | 44 +++-
1 file changed, 15 insertions(+), 29
Document usage of gpio property which turns on external control over
regulator.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
Documentation/devicetree/bindings/mfd/max77686.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git
Minor nit: Initialize the opmode for each regulator to normal mode in a
readable explicit way.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
Suggested-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
drivers/regulator/max77686.c | 4 ++--
1 file changed, 2
Add control over GPIO for regulators supporting this: LDO20, LDO21,
LDO22, buck8 and buck9.
This is needed for proper (and full) configuration of the Maxim 77686
PMIC without creating redundant 'regulator-fixed' entries.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
Register with kernel power-off handler instead of setting pm_power_off
directly. Always use register_power_off_handler_simple as there is no
indication that more than one power-off handler is registered.
If the power-off handler only resets the system or puts the CPU in sleep mode,
select the
Hi,
On 21/10/14 07:43, Abhilash Kesavan wrote:
From: Naveen Krishna Ch naveenkrishna...@gmail.com
Add clock support for the RTC block in Exynos7.
Signed-off-by: Naveen Krishna Ch naveenkrishna...@gmail.com
Signed-off-by: Abhilash Kesavan a.kesa...@samsung.com
---
Hi Abhilash,
On 24/10/14 16:32, Abhilash Kesavan wrote:
On Wed, Oct 8, 2014 at 11:18 AM, Abhilash Kesavan
kesavan.abhil...@gmail.com wrote:
On Tue, Oct 7, 2014 at 9:46 AM, Kukjin Kim kg...@kernel.org wrote:
Tomasz Figa wrote:
On 30.09.2014 17:12, Abhilash Kesavan wrote:
On Mon, Sep 22, 2014
So don't ask why but I accidentally ended up in a branch looking at this
patch and didn't like it. So very quickgrumpy review.
First, please make the patch subject more descriptive: I'd expect a helper
function scaffolding like the various crtc/probe/dp ... helpers we already
have. You instead
Mauro Ribeiro mdr...@gmail.com writes:
As I wrote you previously outside the list this is the commit ARM:
EXYNOS: SWRESET is needed to boot secondary CPU on exynos3250 that I
was expecting it to fix XU3 as well and apparently it is..
I'm not sure about that, since I haven't been able to get
Hello Krzysztof,
On 10/27/2014 04:03 PM, Krzysztof Kozlowski wrote:
The driver is used only on Exynos based boards with DTS support.
Convert the driver to DTS-only version.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
drivers/regulator/max77802.c | 44
Hello Krzysztof,
On 10/27/2014 04:03 PM, Krzysztof Kozlowski wrote:
The driver is used only on Exynos4 based boards with DTS support.
Convert the driver to DTS-only version.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
drivers/regulator/max77686.c | 51
Hello Krzysztof,
On 10/27/2014 04:03 PM, Krzysztof Kozlowski wrote:
The driver is used only on Exynos based boards with DTS support.
Convert the driver to DTS-only version. This simplifies a little the
code:
1. No dead (unused) entries in platform_data structure.
2. More code removed (from
Hello Krzysztof,
On 10/27/2014 04:03 PM, Krzysztof Kozlowski wrote:
The regulator_register() expects array of 'regulator_desc' to be const.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
drivers/regulator/max77686.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Wed, Aug 27, 2014 at 10:29 AM, Ajay Kumar ajaykumar...@samsung.com wrote:
Assign the pointer to bridge ops structure(drm_bridge_funcs) in
the bridge driver itself, instead of passing it to drm_bridge_init.
This will allow bridge driver developer to pack bridge private
information inside
Hello Krzysztof,
On 10/27/2014 04:03 PM, Krzysztof Kozlowski wrote:
Minor nit: Initialize the opmode for each regulator to normal mode in a
readable explicit way.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
Suggested-by: Javier Martinez Canillas
On Mon, Oct 27, 2014 at 3:01 PM, Daniel Vetter dan...@ffwll.ch wrote:
So don't ask why but I accidentally ended up in a branch looking at this
patch and didn't like it. So very quickgrumpy review.
First, please make the patch subject more descriptive: I'd expect a helper
function scaffolding
Hello Krzysztof,
On 10/27/2014 04:03 PM, Krzysztof Kozlowski wrote:
@@ -85,6 +91,9 @@ struct max77686_data {
struct max77686_regulator_data *regulators;
int num_regulators;
+ /* Array of size num_regulators with GPIOs for external control. */
+ int *ext_control_gpio;
On Wed, Aug 27, 2014 at 10:29 AM, Ajay Kumar ajaykumar...@samsung.com wrote:
A set of helper functions are defined in this patch to make
bridge driver probe independent of the drm flow.
The bridge devices register themselves on a lookup table
when they get probed by calling drm_bridge_add.
Hello Krzysztof,
On 10/27/2014 04:03 PM, Krzysztof Kozlowski wrote:
Document usage of gpio property which turns on external control over
regulator.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
Documentation/devicetree/bindings/mfd/max77686.txt | 3 +++
1 file changed, 3
On 10/24/2014 06:22 AM, Marcin Jabrzyk wrote:
On 23/10/14 20:41, Stephen Boyd wrote:
On 10/23/2014 07:06 AM, Russell King - ARM Linux wrote:
The CPU notifier is called via notify_cpu_starting(), which is called
with interrupts disabled, and a reason code of CPU_STARTING.
Interrupts
at
On Mon, Oct 27, 2014 at 8:58 PM, Sean Paul seanp...@chromium.org wrote:
@@ -660,8 +662,11 @@ struct drm_bridge_funcs {
* @driver_private: pointer to the bridge driver's internal context
*/
struct drm_bridge {
- struct drm_device *dev;
+ struct device *dev;
Please don't rename
On Mon, Oct 27, 2014 at 11:20 PM, Daniel Vetter dan...@ffwll.ch wrote:
On Mon, Oct 27, 2014 at 8:58 PM, Sean Paul seanp...@chromium.org wrote:
@@ -660,8 +662,11 @@ struct drm_bridge_funcs {
* @driver_private: pointer to the bridge driver's internal context
*/
struct drm_bridge {
-
Dear Kukjin,
Did you please pick up this patchset on 3.19 queue?
Best Regards,
Chanwoo Choi
On 10/24/2014 10:12 PM, Chanwoo Choi wrote:
This patchset adds new board dts file for Samsung Rinato board (Gear 2) which
is based on Exynos3250 SoC and adds sleep mode pin configuration using pinctrl
On Mon, Oct 27, 2014 at 11:26:30PM +0100, Daniel Vetter wrote:
Looking at the of_drm_find_panel function I actually wonder how that
works - the drm_panel doesn't really need to stick around afaics.
After all panel_list is global so some other driver can unload.
Russell's of support for
Chanwoo Choi wrote:
Dear Kukjin,
Hi,
Did you please pick up this patchset on 3.19 queue?
I'll apply this series once my previous pull-request which has been sent out
last week is merged into arm-soc tree.
If any comments on this series, I'll let you know.
Thanks,
Kukjin
Best Regards,
Dear Kukjin,
On 10/28/2014 09:19 AM, Kukjin Kim wrote:
Chanwoo Choi wrote:
Dear Kukjin,
Hi,
Did you please pick up this patchset on 3.19 queue?
I'll apply this series once my previous pull-request which has been sent out
last week is merged into arm-soc tree.
If any comments on this
On Mon, Oct 27, 2014 at 04:03:40PM +0100, Krzysztof Kozlowski wrote:
The driver is used only on Exynos4 based boards with DTS support.
Convert the driver to DTS-only version.
This doesn't seem like a particularly persuasive reason honestly and if
you're going to mess around with this stuff
On Mon, Oct 27, 2014 at 04:03:42PM +0100, Krzysztof Kozlowski wrote:
The regulator_register() expects array of 'regulator_desc' to be const.
Applied, thanks.
signature.asc
Description: Digital signature
Hi,
I'm sending new pull-request for tags/samsung-pm-v2 instead of tags/samsung-pm.
Note that just added fix build with ARM_CPU_SUSPEND=n from Arnd, please pull.
Thanks,
Kukjin
The following changes since commit f114040e3ea6e07372334ade75d1ee0775c355e1:
Linux 3.18-rc1
Dear Kukjin,
On 10/28/2014 12:48 PM, Kukjin Kim wrote:
Chanwoo Choi wrote:
This patch add Exynos4415's SoC ID.
Since the CPU ID has been removed as per comments, need to update the commit
message accordingly.
OK, I'll update it.
Exynos4415 is based on the 32-bit RISC
processor for
Sylwester Nawrocki wrote:
On 27/10/14 02:11, Chanwoo Choi wrote:
Chanwoo Choi (2):
clk: samsung: exynos4415: Add clocks using common clock framework
clk: samsung: Document binding for Exynos4415 clock controller
Added both to my tree, thanks. In future please put DT binding
Chanwoo Choi wrote:
Dear Kukjin,
[...]
+config SOC_EXYNOS4415
+ bool SAMSUNG EXYNOS4415
+ default y
+ depends on ARCH_EXYNOS4
+
I think, this is not required more...
But,
The clock driver must need to CONFIG_SOC_EXYNOS4415 configuration
to build it. The clock
This patchset support new Exynos4415 Samsung SoC based on Cortex-A9 quad cores.
Exynos4415 is a System-On-Chip (SoC) that is based on 32-bit RISC processor
for Smartphone. It is desigend with the 28nm low-power high-K metal gate
process
and provides the best performance features.
This patchset
This patch add Exynos4415's SoC. Exynos4415 is based on the 32-bit RISC
processor for Smartphone. Exynos4415 uses Cortex A9 quad-cores and has a target
speed of 1.6GHz and provides 8.5GB/s memory bandwidth.
Cc: Kukjin Kim kgene@samsung.com
Signed-off-by: Chanwoo Choi cw00.c...@samsung.com
This patch adds new exynos4415.dtsi to support Exynos4415 SoC
based on Cortex-A9 quad cores and includes following dt nodes:
- GIC interrupt controller (GIC-400)
- Pinctrl to control three GPIO parts
- CMU (Clock Management Unit) for CMU/CMU_DMC/AUDSS
- CPU information (Cortex-A9 quad cores)
-
78 matches
Mail list logo
