On Tue, Oct 28, 2014 at 03:35:50PM +0100, Thierry Reding wrote:
On Mon, Oct 27, 2014 at 11:26:30PM +0100, Daniel Vetter wrote:
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
On Tue, Oct 28, 2014 at 03:29:47PM +0100, Thierry Reding wrote:
On Mon, Oct 27, 2014 at 11:20:31PM +0100, Daniel Vetter 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
On Tue, Oct 28, 2014 at 04:05:34PM +0100, Thierry Reding wrote:
On Tue, Oct 28, 2014 at 08:16:44PM +0530, Ajay kumar wrote:
On Tue, Oct 28, 2014 at 8:11 PM, Thierry Reding
thierry.red...@gmail.com wrote:
On Tue, Oct 28, 2014 at 03:19:36PM +0100, Daniel Vetter wrote:
On Tue, Oct 28, 2014
On Wed, Oct 29, 2014 at 08:43:14AM +0100, Daniel Vetter wrote:
On Tue, Oct 28, 2014 at 03:35:50PM +0100, Thierry Reding wrote:
On Mon, Oct 27, 2014 at 11:26:30PM +0100, Daniel Vetter wrote:
On Mon, Oct 27, 2014 at 11:20 PM, Daniel Vetter dan...@ffwll.ch wrote:
On Mon, Oct 27, 2014 at
On 10/29/2014 08:58 AM, Daniel Vetter wrote:
On Tue, Oct 28, 2014 at 04:05:34PM +0100, Thierry Reding wrote:
On Tue, Oct 28, 2014 at 08:16:44PM +0530, Ajay kumar wrote:
On Tue, Oct 28, 2014 at 8:11 PM, Thierry Reding
thierry.red...@gmail.com wrote:
On Tue, Oct 28, 2014 at 03:19:36PM +0100,
On Wed, Oct 29, 2014 at 09:57:02AM +0100, Daniel Vetter wrote:
On Wed, Oct 29, 2014 at 09:38:23AM +0100, Thierry Reding wrote:
On Wed, Oct 29, 2014 at 08:43:14AM +0100, Daniel Vetter wrote:
On Tue, Oct 28, 2014 at 03:35:50PM +0100, Thierry Reding wrote:
On Mon, Oct 27, 2014 at 11:26:30PM
On Wed, Oct 29, 2014 at 08:51:27AM +0100, Daniel Vetter wrote:
On Tue, Oct 28, 2014 at 03:29:47PM +0100, Thierry Reding wrote:
On Mon, Oct 27, 2014 at 11:20:31PM +0100, Daniel Vetter wrote:
On Mon, Oct 27, 2014 at 8:58 PM, Sean Paul seanp...@chromium.org wrote:
@@ -660,8 +662,11 @@
On wto, 2014-10-28 at 22:31 +, Mark Brown wrote:
On Mon, Oct 27, 2014 at 01:11:49PM +0100, Krzysztof Kozlowski wrote:
@@ -247,6 +250,8 @@ static struct regulator_ops max77686_ldo_ops = {
.set_voltage_sel= regulator_set_voltage_sel_regmap,
.set_voltage_time_sel =
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
Warning message about missing/incorrect associativity was a bit too
long, so shorten it to fit a single line.
Suggested-by: Russell King - ARM Linux li...@arm.linux.org.uk
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
---
arch/arm/mm/cache-l2x0.c | 4 ++--
1 file changed, 2
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
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
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
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
On 28 October 2014 21:31, Geert Uytterhoeven ge...@linux-m68k.org wrote:
Hi Ulf, Rafael,
On Tue, Oct 28, 2014 at 3:38 PM, Ulf Hansson ulf.hans...@linaro.org wrote:
Typically an -attach_dev() callback would fetch some PM resourses.
Those operations, like for example clk_get() may fail with
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
Hi Ulf,
On Wed, Oct 29, 2014 at 10:26 AM, Ulf Hansson ulf.hans...@linaro.org wrote:
On 28 October 2014 21:31, Geert Uytterhoeven ge...@linux-m68k.org wrote:
On Tue, Oct 28, 2014 at 3:38 PM, Ulf Hansson ulf.hans...@linaro.org wrote:
Typically an -attach_dev() callback would fetch some PM
On Wed, Oct 29, 2014 at 10:20:13AM +0100, Krzysztof Kozlowski wrote:
On wto, 2014-10-28 at 22:31 +, Mark Brown wrote:
This looks wrong, you're using the regular enable operation as suspend
enable. How does that work without disrupting the current runtime
state?
Currently it
On 29 October 2014 10:32, Geert Uytterhoeven ge...@linux-m68k.org wrote:
Hi Ulf,
On Wed, Oct 29, 2014 at 10:26 AM, Ulf Hansson ulf.hans...@linaro.org wrote:
On 28 October 2014 21:31, Geert Uytterhoeven ge...@linux-m68k.org wrote:
On Tue, Oct 28, 2014 at 3:38 PM, Ulf Hansson
On śro, 2014-10-29 at 10:01 +, Mark Brown wrote:
On Wed, Oct 29, 2014 at 10:20:13AM +0100, Krzysztof Kozlowski wrote:
On wto, 2014-10-28 at 22:31 +, Mark Brown wrote:
This looks wrong, you're using the regular enable operation as suspend
enable. How does that work without
Hi Ulf,
On Wed, Oct 29, 2014 at 11:14 AM, Ulf Hansson ulf.hans...@linaro.org wrote:
Given that several patch series using -attach_dev() are already floating
around and will be in -next soon, what is the plan of getting this in?
Doing it ASAP (in v3.18-rc3)?
Delaying this to v3.19-rc2, which
On Wed, Oct 29, 2014 at 11:18:54AM +0100, Krzysztof Kozlowski wrote:
On śro, 2014-10-29 at 10:01 +, Mark Brown wrote:
No, this isn't suspend enable control - this is normal, standard enable
control and the device has no suspend enable control.
You mean that for such regulator the
So I've tried this patch, it resolves one problem but introduces also
new ones. As expected the BUG warning is not showing after applying this
patch but there are some interesting side effects.
I was looking on /proc/interrupts output. IRQ for CPU0 have MCT name
and IRQ for CPU1 has
On wto, 2014-10-28 at 13:11 +0100, Krzysztof Kozlowski wrote:
On wto, 2014-10-28 at 09:52 +0100, Krzysztof Kozlowski wrote:
On pon, 2014-10-27 at 21:03 +0100, Javier Martinez Canillas wrote:
Hello Krzysztof,
On 10/27/2014 04:03 PM, Krzysztof Kozlowski wrote:
@@ -85,6 +91,9 @@
On śro, 2014-10-29 at 10:31 +, Mark Brown wrote:
On Wed, Oct 29, 2014 at 11:18:54AM +0100, Krzysztof Kozlowski wrote:
On śro, 2014-10-29 at 10:01 +, Mark Brown wrote:
No, this isn't suspend enable control - this is normal, standard enable
control and the device has no suspend
[adding Linus and Alexandre to the cc list]
Hello Krzysztof,
On 10/29/2014 11:42 AM, Krzysztof Kozlowski wrote:
On wto, 2014-10-28 at 13:11 +0100, Krzysztof Kozlowski wrote:
On wto, 2014-10-28 at 09:52 +0100, Krzysztof Kozlowski wrote:
On pon, 2014-10-27 at 21:03 +0100, Javier Martinez
Hello Krzysztof,
On 10/29/2014 11:44 AM, Krzysztof Kozlowski wrote:
On śro, 2014-10-29 at 10:31 +, Mark Brown wrote:
On Wed, Oct 29, 2014 at 11:18:54AM +0100, Krzysztof Kozlowski wrote:
On śro, 2014-10-29 at 10:01 +, Mark Brown wrote:
No, this isn't suspend enable control - this
On śro, 2014-10-29 at 11:51 +0100, Javier Martinez Canillas wrote:
Hello Krzysztof,
On 10/29/2014 11:44 AM, Krzysztof Kozlowski wrote:
On śro, 2014-10-29 at 10:31 +, Mark Brown wrote:
On Wed, Oct 29, 2014 at 11:18:54AM +0100, Krzysztof Kozlowski wrote:
On śro, 2014-10-29 at 10:01
Hi,
Changes since v5
1. Remove patch 1 and 2 - applied.
2. Patch 1/3: remove suspend_enable functions (suggested by Mark Brown).
3. Patch 1/3: Add Javier's reviewed-by.
4. Add patch 2/3: remove suspend_enable for max77802 also.
Changes since v4
1. New patch:
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
The Maxim 77802 PMIC regulators do not have special enable configuration
for suspend. The driver instead enabled them manually which is not a
best way to deal with suspend.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
drivers/regulator/max77802.c | 4
1 file changed, 4
Hello Krzysztof,
On 10/29/2014 12:14 PM, Krzysztof Kozlowski wrote:
The Maxim 77802 PMIC regulators do not have special enable configuration
for suspend. The driver instead enabled them manually which is not a
best way to deal with suspend.
Signed-off-by: Krzysztof Kozlowski
This patch adds node which enables board-specific reboot/poweroff code.
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
---
arch/arm/boot/dts/exynos4412-odroid-common.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4412-odroid-common.dtsi
This patch adds a driver implementing correct reboot and poweroff
procedures for Exynos4412-based Hardkernel's Odroid X/X2/U2/U3/U3+
boards.
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
---
.../bindings/power/reset/odroid-reset.txt | 18
drivers/power/reset/Kconfig
Mixed indexes were used for array of opmodes in max77686_data structure:
id of regulator and index of regulator_desc array.
These indexes are exactly the same but the mixture may confuse. Use
consistently the id of regulator.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
The driver is used only on Exynos based boards with DTS support.
Convert the driver to DTS-only version. Parse all regulators at once,
not one-by-one. Remove dependency on data provided by max77686 MFD
driver.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
The driver is used only on Exynos based boards with DTS support.
Convert the driver to DTS-only version. Parse all regulators at once,
not one-by-one. Remove dependency on data provided by max77686 MFD
driver.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
Add enable 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
---
Hi,
Patch 2/8: not tested on hardware. I am kindly asking for testing it
because I don't have the board with Maxim 77802.
Changes since v1
1. Add patch: 1/8 regulator: max77686: Consistently index opmode
array by rdev id.
2. Remove patch regulator: max77686: Make
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.
Document usage of gpio property which turns on external/GPIO 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
Reviewed-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
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: 68 insertions(+), 156
deletions).
3. Regulator driver
Krzysztof Kozlowski k.kozlow...@samsung.com writes:
When resuming the system the power domain has to be powered on early so
any runtime PM aware devices could resume.
This fixes following scenario reproduced on Exynos DRM:
1. Power domain is off before suspending the system.
2. System is
Ulf Hansson ulf.hans...@linaro.org writes:
The reference counting isn't needed, let's remove it.
After reading the commit that added this feature[1], I think this
changelog needs a more detail explaining why it's not needed anymore.
Kevin
[1]
commit 1d5fcfec22ce5f69db0d29284d2b65ff8ab1bfaa
Dear Sir
Did your website get hit by Google Penguin update on October 17th 2014? What
basically is Google Penguin Update? It is actually a code name for Google
algorithm which aims at decreasing your websites search engine rankings that
violate Googles guidelines by using black hat SEO
Geert Uytterhoeven ge...@linux-m68k.org writes:
Hi Ulf, Rafael,
On Tue, Oct 28, 2014 at 3:38 PM, Ulf Hansson ulf.hans...@linaro.org wrote:
Typically an -attach_dev() callback would fetch some PM resourses.
Those operations, like for example clk_get() may fail with different
errors,
Hi Kevin,
On Wed, Oct 29, 2014 at 10:10 PM, Kevin Hilman khil...@kernel.org wrote:
Geert Uytterhoeven ge...@linux-m68k.org writes:
On Tue, Oct 28, 2014 at 3:38 PM, Ulf Hansson ulf.hans...@linaro.org wrote:
Typically an -attach_dev() callback would fetch some PM resourses.
Those operations,
Ulf Hansson ulf.hans...@linaro.org writes:
While adding devices to the generic PM domain we allocate data for the
struct generic_pm_domain_data.
Don't allow existing generic_pm_domain_data in this case, since that
indicates the device is already being added from another context. Let's
Hello Krzysztof,
On 10/29/2014 04:06 PM, Krzysztof Kozlowski wrote:
static int max77802_pmic_probe(struct platform_device *pdev)
{
struct max77686_dev *iodev = dev_get_drvdata(pdev-dev.parent);
- struct max77686_platform_data *pdata = dev_get_platdata(iodev-dev);
struct
Ulf Hansson ulf.hans...@linaro.org writes:
To improve error handling while adding/removing devices from their PM
domains, we need to restructure the code a bit. Let's do this by moving
the device specific parts into a separate function.
Signed-off-by: Ulf Hansson ulf.hans...@linaro.org
This
Ulf Hansson ulf.hans...@linaro.org writes:
To improve error handling while adding/removing devices from their PM
domains, we need to restructure the code a bit. Let's do this by moving
the device specific parts into a separate function.
Signed-off-by: Ulf Hansson ulf.hans...@linaro.org
Bartlomiej,
On Thu, Sep 18, 2014 at 05:27:17PM +0200, Bartlomiej Zolnierkiewicz wrote:
Hi,
This patch series replaces the hardware registers abstractions in
the Exynos thermal driver by the usage of per-SoC type operations.
Such solution provides simpler, easier to understand code and
56 matches
Mail list logo
