Hello Andrew,
On 09/13/2014 12:13 AM, Andrew Morton wrote:
On Fri, 12 Sep 2014 10:17:43 +0200 Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
The MAX7802 PMIC has a Real-Time-Clock (RTC) with two alarms.
This patch adds support for the RTC and is based on a driver
added
;
+ };
+ };
+ };
+ };
+
mmc@1255 {
num-slots = 1;
supports-highspeed;
Once those two issues are addressed, feel free to add my
Reviewed-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Best regards,
Javier
and today's linux-next (20140818).
Doug Anderson (1):
rtc: max77686: Allow the max77686 rtc to wakeup the system
Javier Martinez Canillas (4):
rtc: max77686: Remove dead code for SMPL and WTSR.
rtc: max77686: Fail to probe if no RTC regmap irqchip is set
rtc: max77686: Remove unneded info log
The MAX7802 PMIC has a Real-Time-Clock (RTC) with two alarms.
This patch adds support for the RTC and is based on a driver
added by Simon Glass to the Chrome OS kernel 3.8 tree.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Reviewed-by: Krzysztof Kozlowski k.kozlow
If devm_rtc_device_register() fails a dev_err() is already
reported so there is no need to do an additional dev_info().
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
drivers/rtc/rtc-max77686.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/rtc/rtc
the i2c
bus up before the max77686 wakeup runs.
Signed-off-by: Doug Anderson diand...@chromium.org
Reviewed-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Reviewed-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
Changes since v6: None
Changes since v5:
- Fix $SUBJECT since
the driver was original merged in
commit fca1dd03 (rtc: max77686: add Maxim 77686 driver).
So, since this code has never been built, let's just remove it.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Reviewed-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
drivers/rtc
instead of getting an OOPS.
Reported-by: Krzysztof Kozlowski k.kozlow...@samsung.com
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
Fixes the issue reported by Krzystof in: https://lkml.org/lkml/2014/8/8/121
---
drivers/rtc/rtc-max77686.c | 6 ++
1 file changed, 6
Hello Kukjin,
On 09/12/2014 02:26 PM, kg...@kernel.org wrote:
This is a third version of th series that adds max77802 support for
the Peach Pit and Pi boards. The series also have all the pending
patches that were posted but depended on this support. I've picked
all the patches I found and
Hello Doug,
On 09/12/2014 05:12 PM, Doug Anderson wrote:
Hi,
On Fri, Sep 12, 2014 at 1:17 AM, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
From: Doug Anderson diand...@chromium.org
The max77686 includes an RTC that keeps power during suspend. It's
convenient
Hello Lee,
On 09/11/2014 10:00 AM, Sjoerd Simons wrote:
-static const struct of_device_id mxt_of_match[] = {
-{ .compatible = atmel,maxtouch, },
-{},
-};
-MODULE_DEVICE_TABLE(of, mxt_of_match);
-
static const struct i2c_device_id mxt_id[] = {
it across the different
drivers.
Signed-off-by: Andrew Bresticker abres...@chromium.org
Reviewed-by: Simon Glass s...@chromium.org
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Reviewed-by: Doug Anderson diand...@chromium.org
Acked-by: Lee Jones lee.jo...@linaro.org
-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
Changes since v2:
- Explain in the commit message from where the delay and retry values come
from.
Commented by Andrew Bresticker.
- Move the needed definitions inside the if block. Suggested by Lee Jones.
- Only check if result
From: Todd Broch tbr...@chromium.org
If the EC device tree node has sub-nodes, try to instantiate them as
MFD sub-devices. We can configure the EC features provided by the board.
Signed-off-by: Todd Broch tbr...@chromium.org
Signed-off-by: Javier Martinez Canillas javier.marti
Hello,
This is a second batch of cleanups patches for the mfd cros_ec
driver and its subdevices drivers. The first batch of cleanups
was posted by Doug Anderson [0] and have already been merged.
The patches were picked from the ChromeOS 3.8 kernel and after
these no cleanups patches for cros_ec
...@chromium.org
Reviewed-by: Doug Anderson diand...@chromium.org
Acked-by: Wolfram Sang w...@the-dreams.de
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
drivers/i2c/busses/i2c-cros-ec-tunnel.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/i2c/busses/i2c-cros
From: Andrew Bresticker abres...@chromium.org
Now that there's a central cros_ec_cmd_xfer(), move the locking
out of the SPI driver.
Signed-off-by: Andrew Bresticker abres...@chromium.org
Reviewed-by: Simon Glass s...@chromium.org
Signed-off-by: Javier Martinez Canillas javier.marti
long term.
* This same logic probably needs to be applied to the i2c driver.
Signed-off-by: Doug Anderson diand...@chromium.org
Reviewed-by: Randall Spangler rspang...@chromium.org
Reviewed-by: Vadim Bendebury vben...@chromium.org
Signed-off-by: Javier Martinez Canillas javier.marti
Hello Dmitry,
On 09/11/2014 12:25 AM, Dmitry Torokhov wrote:
+hsi2c_8 {
+status = okay;
+clock-frequency = 333000;
+
+/* Atmel mXT336S */
+trackpad@4b {
+compatible = atmel,maxtouch;
+reg = 0x4b;
+interrupt-parent = gpx1;
+
Hello Nick,
On 09/11/2014 11:19 AM, Nick Dyer wrote:
Thanks for the clear explanation.
The i2c aliases are a bit confusing. The original device the driver was
written for was called qt602240, which was renamed by Atmel to mXT224 when
the chip series was called maXTouch. The driver now
Hello Wolfram,
On 09/11/2014 01:08 PM, Wolfram Sang wrote:
Funny timing. I am just reviewing the series from Lee and also stumbled
over modaliases, too...
On Thu, Sep 11, 2014 at 10:19:54AM +0100, Nick Dyer wrote:
On 11/09/14 09:38, Javier Martinez Canillas wrote:
To expand on what
Hello Wolfram,
On 09/11/2014 01:35 PM, Wolfram Sang wrote:
This is a workaround. It would make sense, however, to add it because we
want to support i2c_board_info structures.
I think it really depends if an IP block can be used on non-DT platforms
(which I think is true for this
Hello Mike,
On 09/09/2014 10:57 PM, Mike Turquette wrote:
Quoting Javier Martinez Canillas (2014-09-07 23:49:28)
Since we are in 3.17-rc4 already, I'm afraid that this series may miss
3.18 again, is there anything else you need from me to pick this
series? It will obviously conflict
Hello Doug,
On 09/10/2014 06:42 AM, Doug Anderson wrote:
+
+ ldo35_reg: LDO35 {
+ regulator-name = ldo_35;
+ regulator-min-microvolt = 120;
+ regulator-max-microvolt = 120;
Hello Doug,
On 09/10/2014 06:45 AM, Doug Anderson wrote:
Reviewed-by: Doug Anderson diand...@chromium.org
Meant to add this to the v2. Sorry for the spam...
No worries, I've to re-spin anyways to fix the issue you pointed on Patch #1
so I'll include your Reviewed-by tag.
Best regards,
Hello Doug,
On 09/10/2014 06:52 AM, Doug Anderson wrote:
I would note that the downstream dts file has this i2c bus at 400kHz.
...but that's not a problem with your patch. Perhaps you could submit
that as a separate patch?
Indeed, I've to re-spin anyways so I'll include that on the next
Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/configs/exynos_defconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/configs/exynos_defconfig
b/arch/arm/configs/exynos_defconfig
index 676c744..fbbac06 100644
--- a/arch/arm/configs/exynos_defconfig
+++ b/arch/arm
...@samsung.com
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Reviewed-by: Doug Anderson diand...@chromium.org
---
arch/arm/boot/dts/cros-adc-thermistors.dtsi | 44 +
arch/arm/boot/dts/exynos5420-peach-pit.dts | 6
arch/arm/boot/dts
The downstream ChromeOS 3.8 kernel sets the clock frequency
for the I2C bus 7 at 400kHz. Do the same change in mainline.
Suggested-by: Doug Anderson diand...@chromium.org
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 1
-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Reviewed-by: Doug Anderson diand...@chromium.org
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 6 ++
arch/arm/boot/dts/exynos5800-peach-pi.dts | 6 ++
2 files changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts
From: Rahul Sharma rahul.sha...@samsung.com
Adding regulators for hdmi for peach-pit board.
Signed-off-by: Rahul Sharma rahul.sha...@samsung.com
Reviewed-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Reviewed
by
Andreas Faerber.
The series is composed of the following patches:
Javier Martinez Canillas (3):
ARM: dts: Add Peach Pit and Pi dts entry for max77802 PMIC
ARM: dts: Add Peach Pit and Pi dts entry for ISL29018 sensor
ARM: dts: Set i2c7 clock at 400kHz for Peach boards
Naveen Krishna Chatradhi (1
in the
the Chrome OS kernel 3.8 tree.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Tested-by: Naveen Krishna Chatradhi ch.nav...@samsung.com
Reviewed-by: Doug Anderson diand...@chromium.org
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 371
The Peach Pi board has an Atmel maXTouch trackpad device.
Add the needed Device Tree nodes to support it.
This Device Tree change is based on the Chrome OS 3.8 tree
but adapted to use the mainline Atmel maXTouch DT binding.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
to be merged
through the linux-samsung tree. I'll post a separate series
to sync exynos_defconfig and multi_v7_defconfig so those can
be picked through the arm-soc tree.
This series must be merged after [0] to avoid merge conflicts.
Javier Martinez Canillas (2):
ARM: dts: Add Peach Pi dts entry
Many Exynos based Chromebooks have an Atmel trackpad so enable
support for it by default will make easier for users.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
Changes since v3: None
arch/arm/configs/exynos_defconfig | 1 +
1 file changed, 1 insertion(+)
diff
-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
Changes since v3:
- Use KEY_RESERVED even for not reserved pins with a GPIO not hooked.
Suggested by Nick Dyer.
- Add a comment to specify the maXTouch chip version so is more
Hello Kukjin,
On 09/09/2014 05:47 AM, kg...@kernel.org wrote:
Javier Martinez Canillas wrote:
Any comments on this series?
Looks good to me but I just wanted to get ack from chrome guy, Doug? But since
Naveen tested, it should be fine I think. I'll take the series.
Great, thanks
[adding Lee Jones to cc list since I'm referring on a series he posted]
Hello Sjoerd,
On 09/09/2014 09:52 AM, Sjoerd Simons wrote:
For i2c devices in OF the modalias exposed to userspace is i2c:node
type, for the Maxtouch driver this is i2c:maxtouch.
Add maxtouch to the i2c id table such
Hello Doug,
On 09/08/2014 06:36 AM, Doug Anderson wrote:
One (ugly?) solution would be to add a feature to your bootloader to
modify the device tree to mark regulators as always-on. Since the
booloader gets to touch the device tree and the bootloader is involved
in communicating into about
Hello Mike,
On Mon, Aug 18, 2014 at 10:32 AM, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
This series add support for the clocks present in the Maxim
77802 Power Managment IC. Previously, the series was part
of a bigger one [0] that aimed to add support for all the
devices
Hello Alessandro,
On Mon, Aug 18, 2014 at 10:34 AM, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
This series add support for the Real Time clock present in
the Maxim 77802 Power Managment IC. Previously, the series
was part of a bigger one [0] that aimed to add support
Hello Krzysztof,
Sorry for the late response, I was on holidays and slowly catching up on email.
On 08/28/2014 11:21 AM, Krzysztof Kozlowski wrote:
On pon, 2014-08-18 at 10:34 +0200, Javier Martinez Canillas wrote:
The max77686 mfd driver adds a regmap IRQ chip which creates an
IRQ domain
Hello Nick,
On 09/02/2014 03:46 PM, Nick Dyer wrote:
On 27/08/14 15:22, Javier Martinez Canillas wrote:
If there was a BTN_NONE or KEY_UNUSED it would had been better but I think
that making a distinction between these two cases (reserved pin vs GPIO
available but not used) is useful.
Maybe
Hello Lee,
Sorry for the delay but had been on holidays last week.
On 09/04/2014 10:25 AM, Lee Jones wrote:
-static const struct mfd_cell cros_devs[] = {
-{
-.name = cros-ec-keyb,
-.id = 1,
-.of_compatible = google,cros-ec-keyb,
-},
-{
-
Hello Lee,
On 09/04/2014 10:34 AM, Lee Jones wrote:
On Mon, 25 Aug 2014, Javier Martinez Canillas wrote:
From: Andrew Bresticker abres...@chromium.org
When an EC command returns EC_RES_IN_PROGRESS, we need to query
the state of the EC until it indicates that it is no longer busy.
Do
Hello Will,
On 09/08/2014 01:21 PM, Will Deacon wrote:
On Sun, Sep 07, 2014 at 05:19:03PM +0100, Tomasz Figa wrote:
At least for next 3.17-rc I'd suggest fixing this up in respective clock
driver and dropping the hack only after Exynos DRM patches are merged
and confirmed working.
Whilst
Hello Kukjin,
On Wed, Aug 20, 2014 at 1:19 PM, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
This is a second version of the series that adds max77802 support for
the Peach Pit and Pi boards. The series also have all the pending
patches that were posted but depended
Hello Andreas,
On 08/27/2014 06:10 PM, Andreas Färber wrote:
Am 27.08.2014 13:02, schrieb Javier Martinez Canillas:
systemd needs control groups support to be enabled in the
kernel so let's enable it by default since is quite likely
that a user-space with systemd will be used.
Signed-off
Hello Will,
On 09/08/2014 03:49 PM, Mark Brown wrote:
On Mon, Sep 08, 2014 at 01:20:11PM +0100, Grant Likely wrote:
On Mon, Sep 8, 2014 at 12:21 PM, Will Deacon will.dea...@arm.com wrote:
Whilst I'm sympathetic to people working to enable DRM, I think this is
the right solution to the
regulators? If Mark agrees with that idea
I'll be glad to propose a patch.
Best regards,
Javier
[0]: https://www.mail-archive.com/linux-sunxi@googlegroups.com/msg06623.html
[1]:
From bdbb3bc1d69c10dce58affe74e6b64636f7810b5 Mon Sep 17 00:00:00 2001
From: Javier Martinez Canillas javier.marti
Hello Mark,
On 09/07/2014 05:01 PM, Mark Brown wrote:
On Sun, Sep 07, 2014 at 11:06:54AM +0200, Javier Martinez Canillas wrote:
But maybe we could add a boot argument similar to clk_ignore_unused but for
regulators? Something like regulator_ignore_unused that would prevent the
regulator
Hello Tomasz,
On 09/07/2014 05:52 PM, Tomasz Figa wrote:
So I believe we've got a process issue here. If you don't have normal
support for display hardware, but you want to keep the display
operational thanks to bootloader already initializing it, you should not
add anything to the kernel
Hello Tomasz,
On 09/07/2014 06:19 PM, Tomasz Figa wrote:
On 07.09.2014 18:12, Javier Martinez Canillas wrote:
Clocks is not an issue at least on this machine since the bootloader already
passes the clk_ignore_unused parameter to the kernel command line so in that
sense there isn't
Hello Mark,
On 28/08/2014, at 10:28, Mark Brown broo...@kernel.org wrote:
Yes, AFAIK the bootloader (none of them because Chromebooks use two
chained U-boots) change the regulators default opmode so once is set
to OFF on .disable, that value is preserved on warm reboot. This made
sense with
Hello Andreas,
On 08/27/2014 12:53 AM, Andreas Färber wrote:
+hsi2c_8 {
+status = okay;
+clock-frequency = 333000;
+
+trackpad@4b {
+compatible=atmel,maxtouch;
+reg=0x4b;
+interrupt-parent=gpx1;
+interrupts=1
systemd needs control groups support to be enabled in the
kernel so let's enable it by default since is quite likely
that a user-space with systemd will be used.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed
systemd needs control groups support to be enabled in the
kernel so let's enable it by default since is quite likely
that a user-space with systemd will be used.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/configs/exynos_defconfig | 1 +
1 file changed, 1
Hello Andreas,
On 08/27/2014 03:11 PM, Andreas Färber wrote:
Hi Javier,
+ trackpad@4b {
+ compatible = atmel,maxtouch;
+ reg = 0x4b;
+ interrupt-parent = gpx1;
+ interrupts = 2 IRQ_TYPE_NONE;
+ pinctrl-names = default;
+
Some boards with multi platform support (e.g: Exynos based
Chromebooks) have an Atmel trackpad so enable support for
as a module will make easier for users.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1
multi-platform supported machines have this touchpad device.
Javier Martinez Canillas (2):
ARM: exynos_defconfig: Enable Atmel maXTouch support
ARM: multi_v7_defconfig: Enable Atmel maXTouch support
Sjoerd Simons (1):
ARM: dts: Add Peach Pit dts entry for Atmel touchpad
arch/arm/boot/dts
Many Exynos based Chromebooks have an Atmel trackpad so enable
support for it by default will make easier for users.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/configs/exynos_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs
-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
[javier.martinez: added linux,gpio-keymap property and changed IRQ type]
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
Changes since v2:
- Add spaces around '=' on properties. Suggested by Andreas Faerber.
Changes since v1
Hello Tomasz and Mark,
Sorry for not answering before but I'm on vacations until Sep, 5 and I
have limited access to my email.
On Wed, Aug 27, 2014 at 11:03 PM, Tomasz Figa tomasz.f...@gmail.com wrote:
From what I know based on my experience with Samsung boards we used, the
opmodes of
Hello Dmitry,
On 08/25/2014 08:01 PM, Dmitry Torokhov wrote:
On Mon, Aug 25, 2014 at 07:28:01PM +0200, Javier Martinez Canillas wrote:
#7 does not apply to my tree (I guess it depends on the 1st batch which I
expect will go through MFD tree?). Maybe you could rebase it on top of my
Hello Mark,
On 08/26/2014 09:17 AM, Mark Brown wrote:
On Mon, Aug 25, 2014 at 08:40:40AM -0700, Doug Anderson wrote:
Can you please test the following change [0] so I can post as a proper
patch? Doug, Mark do you think that forcing the regulator to opmode normal
when enabling is the right
is read
from the hardware register.
Reported-by: Yuvaraj Cd yuvaraj.l...@gmail.com
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
This patch fixes the issue reported in https://lkml.org/lkml/2014/8/25/69
drivers/regulator/max77802.c | 12 +++-
1 file changed
-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
[javier.martinez: added linux,gpio-keymap property and changed IRQ type]
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
Changes since v1:
- Change trackpad IRQ pad function from 0x0 (GPIO input) to 0xf (GPIO IRQ).
suggested
multi-platform supported machines have this touchpad device.
Javier Martinez Canillas (2):
ARM: exynos_defconfig: Enable Atmel maXTouch support
ARM: multi_v7_defconfig: Enable Atmel maXTouch support
Sjoerd Simons (1):
ARM: dts: Add Peach Pit dts entry for Atmel touchpad
arch/arm/boot/dts
Many Exynos based Chromebooks have an Atmel trackpad so enable
support for it by default will make easier for users.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/configs/exynos_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs
Some boards with multi platform support (e.g: Exynos based
Chromebooks) have an Atmel trackpad so enable support for
as a module will make easier for users.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1
-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Tested-by: Kevin Hilman khil...@linaro.org
---
Changes since v1:
- Forgot to enable ptn3460 eDP/LVDS bridge config option
which is used for some boards (e.g: Exynos5250 Snow).
arch/arm/configs/exynos_defconfig | 15 +++
1
Hello Yuvaraj,
On 08/25/2014 10:22 AM, Yuvaraj Cd wrote:
Good question. I'm not that familiar with the dw_mmc host controller nor
its driver implementation so I'll let Yuvaraj or Doug to answer that.
Well,here it goes!
1. Power ON the board LDO4CTRL1[7:6] 11b
2. dw_mmc driver enable the
),
There shouldn't be space before (.
Will fix the identation issues in a v2.
Thanks for the review,
Sjoerd
After fixing the empty lines:
Reviewed-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Best regards,
Javier
--
To unsubscribe from this list: send the line unsubscribe
driver registers
the MFD subdevices with an of_compatibility string.
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
Looks good to me:
Reviewed-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Best regards,
Javier
--
To unsubscribe from this list: send the line
Hello Ajay,
On Mon, Aug 25, 2014 at 8:11 AM, Ajay kumar ajayn...@gmail.com wrote:
Do you plan to address Thierry's concerns and re-spin this patch?
Same question for patches:
drm/bridge: Add i2c based driver for ptn3460 bridge
drm/bridge: Add i2c based driver for ps8622/ps8625 bridge
Yes,
Hello Bartlomiej,
On 08/25/2014 01:43 PM, Bartlomiej Zolnierkiewicz wrote:
Hi,
On Monday, August 25, 2014 10:45:36 AM Javier Martinez Canillas wrote:
Many Exynos devices have a display panel. Most of them just have
a simple panel while others have more complex configurations
Hello Andreas,
On 08/25/2014 01:49 PM, Andreas Färber wrote:
Could you please also do corresponding update to multi_v7_defconfig?
As was mentioned in v1 (but now below), some of these options depend on
Sorry for missing the mention about the dependencies on v2...
patches yet to be respun
...@chromium.org
Reviewed-by: Doug Anderson diand...@chromium.org
Acked-by: Wolfram Sang w...@the-dreams.de
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
drivers/i2c/busses/i2c-cros-ec-tunnel.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/i2c/busses/i2c-cros
it across the different
drivers.
Signed-off-by: Andrew Bresticker abres...@chromium.org
Reviewed-by: Simon Glass s...@chromium.org
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Reviewed-by: Doug Anderson diand...@chromium.org
Acked-by: Lee Jones lee.jo...@linaro.org
long term.
* This same logic probably needs to be applied to the i2c driver.
Signed-off-by: Doug Anderson diand...@chromium.org
Reviewed-by: Randall Spangler rspang...@chromium.org
Reviewed-by: Vadim Bendebury vben...@chromium.org
Signed-off-by: Javier Martinez Canillas javier.marti
From: Andrew Bresticker abres...@chromium.org
Now that there's a central cros_ec_cmd_xfer(), move the locking
out of the SPI driver.
Signed-off-by: Andrew Bresticker abres...@chromium.org
Reviewed-by: Simon Glass s...@chromium.org
Signed-off-by: Javier Martinez Canillas javier.marti
-by: Andreas Färber afaer...@suse.de
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
drivers/input/keyboard/cros_ec_keyb.c | 92 +++
1 file changed, 49 insertions(+), 43 deletions(-)
diff --git a/drivers/input/keyboard/cros_ec_keyb.c
b
to the EC while
it is working on the in-progress command.
Signed-off-by: Andrew Bresticker abres...@chromium.org
Reviewed-by: Simon Glass s...@chromium.org
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
Changes since v1:
- The *xfer() calls don't modify the passed
This is a second batch of cleanups patches for the mfd cros_ec
driver and its subdevices drivers. The first batch of cleanups
was posted by Doug Anderson [0] and have already been merged.
The patches were picked from the ChromeOS 3.8 kernel and after
these no cleanups patches for cros_ec are left,
From: Todd Broch tbr...@chromium.org
If the EC device tree node has sub-nodes, try to instantiate them as
MFD sub-devices. We can configure the EC features provided by the board.
Signed-off-by: Todd Broch tbr...@chromium.org
Signed-off-by: Javier Martinez Canillas javier.marti
Hello Doug,
On 08/25/2014 05:40 PM, Doug Anderson wrote:
I see, so probably until we have a way to define the operating mode for
each regulator using DT we should set the opmode to normal when enabling a
regulator independently of the value the hardware register reported on probe.
Can you
Hello Dmitry,
On 08/25/2014 07:05 PM, Dmitry Torokhov wrote:
Patches #1, #2, #6 and #7 do not depend of others so they can be
merged independently but patches #3, #4 and #5 have to be merged
in that specific order since they depend on the previous one.
#7 does not apply to my tree (I
Hello Lee,
Thanks a lot for your feedback.
On 08/21/2014 04:21 PM, Lee Jones wrote:
On Wed, 20 Aug 2014, Javier Martinez Canillas wrote:
From: Andrew Bresticker abres...@chromium.org
When an EC command returns EC_RES_IN_PROGRESS, we need to query
the state of the EC until it indicates
Hello Lee,
On 08/21/2014 04:25 PM, Lee Jones wrote:
static const struct mfd_cell cros_devs[] = {
-{
-.name = cros-ec-keyb,
-.id = 1,
-.of_compatible = google,cros-ec-keyb,
-},
-{
-.name = cros-ec-i2c-tunnel,
-.id
Hello Yuvaraj,
On 08/22/2014 08:01 AM, Yuvaraj Cd 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
Hello Mark,
On 08/22/2014 04:45 PM, Mark Brown wrote:
On Fri, Aug 22, 2014 at 02:15:46PM +0200, Javier Martinez Canillas wrote:
Mark, any opinions on how this should be solved will be highly appreciated.
If someone could tell me what this is that'd help...
Sorry for not being clear
Hello Mark,
On 08/22/2014 08:30 PM, Mark Brown wrote:
The problem is that one of these regulators is used as the vqmmc-supply
(VCCQ/VDD_IO) so the mmc host controller driver disables it on
MMC_POWER_OFF. Now AFAIK (Yuvaraj can correct me what I got wrong) this
shouldn't be an issue since on
)
- DRM bridge registration and lookup framework
- Parade ps8622/ps8625 eDP/LVDS bridge
- NXP ptn3460 eDP/LVDS bridge
- Exynos Fully Interactive Mobile Display controller (FIMD)
- Panel registration and lookup framework
- Simple panels
- Backlight and LCD device support
Signed-off-by: Javier Martinez
support chunghwa,claa101wb01 panel,
but still we choose to reuse the binding since chunghwa,claa101wb01
has similar LCD timings.
Signed-off-by: Ajay Kumar ajaykumar...@samsung.com
---
Tested-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Best regards,
Javier
--
To unsubscribe
-by: Ajay Kumar ajaykumar...@samsung.com
---
Looks good to me.
Reviewed-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Best regards,
Javier
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo
Hello Ajay,
On Thu, Jul 31, 2014 at 12:58 PM, Thierry Reding
thierry.red...@gmail.com wrote:
On Wed, Jul 30, 2014 at 09:33:28PM +0530, Ajay kumar wrote:
On Wed, Jul 30, 2014 at 8:38 PM, Thierry Reding thierry.red...@gmail.com
wrote:
[...]
I think it should even be possible to do this in
Hello Doug,
On 08/21/2014 12:36 AM, Doug Anderson wrote:
Javier,
On Wed, Aug 20, 2014 at 5:13 AM, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
From: Andrew Bresticker abres...@chromium.org
Now that there's a central cros_ec_cmd_xfer(), move the locking
out of the SPI
Hello Lee,
On 08/21/2014 03:37 PM, Lee Jones wrote:
On Wed, 20 Aug 2014, Javier Martinez Canillas wrote:
From: Doug Anderson diand...@chromium.org
If someone sends a EC_CMD_REBOOT_EC to the EC, the EC will likely be
unresponsive for quite a while. Add a delay to the end of the command
+Bartlomiej Zolnierkiewicz
Hello Marek,
On Wed, Aug 20, 2014 at 8:29 AM, Marek Szyprowski
m.szyprow...@samsung.com wrote:
Yes, discussed in the thread titled [PATCH 1/2] ARM: dts: Enable PMIC
interrupts on ODROID
Those patches weren't important for boot at the time of submission,
but it
901 - 1000 of 1325 matches
Mail list logo
