By using the generic IRQ support in the Register map API, it
is possible to get rid max77686-irq.c and simplify the code.
Suggested-by: Krzysztof Kozlowski
Signed-off-by: Javier Martinez Canillas
Acked-by: Lee Jones
Reviewed-by: Doug Anderson
Tested-by: Doug Anderson
---
Changes since v3
The MAX77802 PMIC has two 32.768kHz Buffered Clock Outputs with
Low Jitter Mode. This patch adds support for these two clocks.
Signed-off-by: Javier Martinez Canillas
---
Changes since v3: None
Changes since v2: None
Changes since v1:
- Use module_platform_driver() instead of having init
.
Signed-off-by: Javier Martinez Canillas
---
Changes since v3:
- Add support for Exynos5800 based Peach pi board. Suggested by Doug Anderson.
- Model the actual regulators relationship instead of a simplistic model.
Suggested by Mark Brown.
Changes since v2: None
Changes since v1:
- Use
Add Device Tree binding documentation for the clocks
outputs in the Maxim 77802 Power Management IC.
Signed-off-by: Javier Martinez Canillas
---
Changes since v3:
- Don't use the same clock driver name in clock-names since it's a consumer
concept and most probably will be
Add Device Tree binding documentation for Maxim 77802 PMIC.
Signed-off-by: Javier Martinez Canillas
---
Changes since v3: None
Changes since v2:
- Explain better the Dynamic Voltage Scaling (DVS) support in some Buck
regulators and the max77802,pmic-buck-{dvs,selb}-gpios properties
, clocks outputs and the RTC.
This patch adds the core support for MAX77802 PMIC and is based
on a driver added by Simon Glass to the Chrome OS kernel 3.8 tree.
Signed-off-by: Javier Martinez Canillas
---
Changes since v3:
- Remove unnecessary OOM error message since the mm subsystem already logs
up before the max77686 wakeup runs.
Signed-off-by: Doug Anderson
Reviewed-by: Javier Martinez Canillas
---
Changes since v3:
- Keep the note that this patch needs another change due wakeup
ordering problems.
drivers/rtc/rtc-max77686.c | 28
1 file changed, 28
Clocks drivers for Maxim PMIC are very similar so they can
be converted to use the generic Maxim clock driver.
Also, while being there use module_platform_driver() helper
macro to eliminate more boilerplate code.
Signed-off-by: Javier Martinez Canillas
Reviewed-by: Krzysztof Kozlowski
This patch adds a dt-binding include for Maxim 77686
PMIC clock IDs that can be to be shared between the
clk-max77686 clock driver and DeviceTree source files.
Signed-off-by: Javier Martinez Canillas
Reviewed-by: Krzysztof Kozlowski
---
Changes since v3: None
drivers/clk/clk-max77686.c
ks outputs.
Also, explain that the clocks identifiers are defined in a
header file that can be included by Device Tree source with
client nodes to avoid using magic numbers.
Signed-off-by: Javier Martinez Canillas
Reviewed-by: Krzysztof Kozlowski
---
Changes since v3:
- Don't change clock-na
Doug Anderson (1):
mfd: max77686: Allow the max77686 rtc to wakeup the system
Javier Martinez Canillas (13):
mfd: max77686: Convert to use regmap_irq
clk: max77686: Add DT include for MAX77686 PMIC clock
clk: max77686: Improve Maxim 77686 PMIC clocks binding
clk: Add generic driver for Ma
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
---
Changes since v3: None
drivers/rtc/Kconfig| 10 +
drivers/rtc
the regmap lock.
Signed-off-by: Javier Martinez Canillas
---
Changes since v3: None
drivers/base/regmap/regmap.c | 34 ++
include/linux/regmap.h | 9 +
2 files changed, 43 insertions(+)
diff --git a/drivers/base/regmap/regmap.c b/drivers/base
Hi Kishon,
On Mon, Dec 9, 2013 at 7:07 AM, Kishon Vijay Abraham I wrote:
> Hi,
>
>
> On Saturday 07 December 2013 02:38 AM, Felipe Balbi wrote:
>>
>> Hi,
>>
>> On Fri, Dec 06, 2013 at 01:14:38PM +0100, Javier Martinez Canillas wrote:
>>>
>>>
Hi Kishon,
On Fri, Dec 6, 2013 at 1:06 PM, Kishon Vijay Abraham I wrote:
> Previously MUSB wrapper (OMAP) device used PLATFORM_DEVID_AUTO while creating
> MUSB core device. So in usb_bind_phy (binds the controller with the PHY), the
> device name of the controller had *.auto* in it. Since with us
Signed-off-by: Nishanth Menon
>> ---
>> based on v3.17-rc1
> Looks good..
> Acked-by: Santosh Shilimkar
>
Looks good to me as well.
Acked-by: Javier Martinez Canillas
Best regards,
Javier
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
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);
>> +
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'
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
)
- 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
-off-by: Javier Martinez Canillas
Tested-by: Kevin Hilman
---
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 file changed, 15 insertions(+)
diff --g
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
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 com
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
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.
>>
>
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 t
is read
from the hardware register.
Reported-by: Yuvaraj Cd
Signed-off-by: Javier Martinez Canillas
---
This patch fixes the issue reported in https://lkml.org/lkml/2014/8/25/69
drivers/regulator/max77802.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a
only some
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/ar
: added linux,gpio-keymap property and changed IRQ type]
Signed-off-by: Javier Martinez Canillas
---
Changes since v1:
- Change trackpad IRQ pad function from 0x0 (GPIO input) to 0xf (GPIO IRQ).
suggested by Tomasz Figa.
- Remove BTN_TOOL_* from "linux,gpio-keymap" property since tho
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
---
arch/arm/configs/exynos_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/exynos_defconfig
b/arch/arm
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
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch
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>;
>> +
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
---
arch/arm/configs/exynos_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --
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
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --
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
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
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch
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
---
arch/arm/configs/exynos_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/exynos_defconfig
b/arch/arm
only some
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/ar
: added linux,gpio-keymap property and changed IRQ type]
Signed-off-by: Javier Martinez Canillas
---
Changes since v2:
- Add spaces around '=' on properties. Suggested by Andreas Faerber.
Changes since v1:
- Change trackpad IRQ pad function from 0x0 (GPIO input) to 0xf (GPIO IRQ).
su
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 wrote:
From what I know based on my experience with Samsung boards we used, the
opmodes of regulators are preconf
Hello Mark,
> On 28/08/2014, at 10:28, Mark Brown 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 the Chrome
Hello Alessandro,
On Mon, Aug 18, 2014 at 10:34 AM, Javier Martinez Canillas
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 for
> all the de
Hello Mike,
On Mon, Aug 18, 2014 at 10:32 AM, Javier Martinez Canillas
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 in the max778
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
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
>
Hello Kukjin,
On Wed, Aug 20, 2014 at 1:19 PM, Javier Martinez Canillas
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 on this support. I
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
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&#
[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: type>, for the Maxtouch driver this is i2c:maxtouch.
>
> Add maxtouch to the i2c id table such that
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
&g
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-microvo
Hello Doug,
On 09/10/2014 06:45 AM, Doug Anderson wrote:
>>
>> Reviewed-by: Doug Anderson
>
> 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,
Javier
--
To uns
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 ne
From: Rahul Sharma
Adding regulators for HDMI for Peach-pi board.
Signed-off-by: Rahul Sharma
Reviewed-by: Javier Martinez Canillas
Signed-off-by: Javier Martinez Canillas
Reviewed-by: Doug Anderson
---
arch/arm/boot/dts/exynos5800-peach-pi.dts | 5 +
1 file changed, 5 insertions
From: Vivek Gautam
Enabled MAX77802 pmic for exynos systems.
One config USB_ANNOUNCE_NEW_DEVICES to display device
information on connect.
Another config for I2C_CHARDEV to see i2c device nodes.
Signed-off-by: Vivek Gautam
Signed-off-by: Javier Martinez Canillas
---
arch/arm/configs
-by: Javier Martinez Canillas
Reviewed-by: Doug Anderson
---
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/exynos5420-peach-pit.dts
b/arch/arm/boot/dts/exynos5420
ggested 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 Ch
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
Signed-off-by: Javier Martinez Canillas
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 1 +
arch/arm/boot/dts/exynos5800-peach-pi.dts | 1 +
2
From: Naveen Krishna Chatradhi
This patch creates a thermistor fragment carrying the NTC Thermistor
nodes as children of the IIO based ADC.
This fragment is included in exynos5420-peach-pit.dts and
exynos5800-peach-pi.dts.
Signed-off-by: Naveen Krishna Chatradhi
Signed-off-by: Javier Martinez
From: Rahul Sharma
Adding regulators for hdmi for peach-pit board.
Signed-off-by: Rahul Sharma
Reviewed-by: Javier Martinez Canillas
Signed-off-by: Javier Martinez Canillas
Reviewed-by: Doug Anderson
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 5 +
1 file changed, 5 insertions
in the
the Chrome OS kernel 3.8 tree.
Signed-off-by: Javier Martinez Canillas
Tested-by: Naveen Krishna Chatradhi
Reviewed-by: Doug Anderson
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 371 +
arch/arm/boot/dts/exynos5800-peach-pi.dts | 371
: Javier Martinez Canillas
---
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 clear.
Suggested by Nick Dyer.
- Omit trailing omit KEY_RESERVED after the GPIO pins
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 entr
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
---
Changes since v3: None
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
---
Changes since v3: None
arch/arm/configs/exynos_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs
e regmap values but it checks unconditionally in
both cases if the resulting endiannes is REGMAP_ENDIAN_NATIVE.
b) REGMAP_ENDIAN_NATIVE is not even a valid DT property according
to the regmap DT binding documentation so it shouldn't be set.
Signed-off-by: Javier Martinez Canillas
---
Hello Nick,
On 08/15/2014 06:08 PM, Nick Dyer wrote:
>>
>> Any comments on this? I would really appreciate if you can expand on how
>> this DT property is supposed to be used so I can re-spin the atmel support
>> patch for Peach boards.
>
> The below patch improves the documentation for the gpio
adding Mike Turquette to cc since this is also a clock driver.
Hello Chris,
Overall it looks good to me, I've just a comment about the driver structure.
On 08/17/2014 04:02 AM, Chris Zhong wrote:
> RK808 PMIC is a MFD with RTC as one of the device. Adding RTC driver
> for supporting RTC device p
Hello Kukjin,
On 08/18/2014 08:27 PM, Kukjin Kim wrote:
> On 08/11/14 10:46, Doug Anderson wrote:
>>
> OK, I've applied this but 2nd in this series...
>
Thanks for picking this and yes PATCH 2/2 from this series was dropped.
>> Acked-by: Doug Anderson
>>
> Thanks,
> Kukjin
>
I've posted PATCH
Hello Ulf,
On 08/15/2014 04:51 PM, Ulf Hansson wrote:
>
> Just wanted to add some input regarding the errors in the mmc case.
> These are of high importance. In principle if you get, "Failed getting
> OCR mask: -22", likely you will be using a wrong OCR mask while
> negotiating the voltage level
On 08/19/2014 02:43 PM, Ulf Hansson wrote:
>
> Well, currently this seems like the best approach. If we end up having
> some new regulator helper function, future wise, we can convert to
> such later on.
>
Great, thanks a lot for your help!
> Kind regards
> Uffe
>
Best regards,
Javier
--
To un
in the
the Chrome OS kernel 3.8 tree.
Signed-off-by: Javier Martinez Canillas
Tested-by: Naveen Krishna Chatradhi
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 371 +
arch/arm/boot/dts/exynos5800-peach-pi.dts | 371 +
2 files changed
apply cleanly on top of linux-next. Also I've taken some DT snippets
from the downstream Chrome OS 3.8 kernel DTS for devices that use
one of the regulators of these regulators has their input supply.
The series is composed of the following patches:
Javier Martinez Canillas (3):
ARM: dts: Add Pea
-by: Javier Martinez Canillas
---
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/exynos5420-peach-pit.dts
b/arch/arm/boot/dts/exynos5420-peach-pit.dts
index 5b9dbb9
From: Rahul Sharma
Adding regulators for hdmi for peach-pit board.
Signed-off-by: Rahul Sharma
Reviewed-by: Javier Martinez Canillas
Signed-off-by: Javier Martinez Canillas
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot
Peach Pit and Pi boards.
Signed-off-by: Javier Martinez Canillas
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 2 ++
arch/arm/boot/dts/exynos5800-peach-pi.dts | 2 ++
2 files changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5420-peach-pit.dts
b/arch/arm/boot/dts/exynos5420
From: Rahul Sharma
Adding regulators for HDMI for Peach-pi board.
Signed-off-by: Rahul Sharma
Reviewed-by: Javier Martinez Canillas
Signed-off-by: Javier Martinez Canillas
---
v2: 1) Add blank line before hdmi regulators.
arch/arm/boot/dts/exynos5800-peach-pi.dts | 5 +
1 file changed
From: Naveen Krishna Chatradhi
This patch creates a thermistor fragment carrying the NTC Thermistor
nodes as children of the IIO based ADC.
This fragment is included in exynos5420-peach-pit.dts and
exynos5800-peach-pi.dts.
Signed-off-by: Naveen Krishna Chatradhi
Signed-off-by: Javier Martinez
Hello Lee, Marek,
On 08/20/2014 10:19 AM, Lee Jones wrote:
> On Wed, 20 Aug 2014, Marek Szyprowski wrote:
>
>> Commit 6f1c1e71d93 ("mfd: max77686: Convert to use regmap_irq") broke
>> support for boards, which provide no irq for MAX 77686 PMIC. In such
>> case, not all functions of PMIC are avail
Hello Stephen,
On 08/19/2014 06:49 PM, Stephen Warren wrote:
> From: Stephen Warren
>
> Commit d647c199510c ("regmap: add DT endianness binding support") had
> some issues. Commit ba1b53feb8ca ("regmap: Fix DT endianess parsing
> logic") fixed the main problem. This patch fixes the other.
>
> S
Hello Doug,
On 08/19/2014 06:26 PM, Doug Anderson wrote:
>
> While your change is correct, I have a worry that it will break things
> if it's merged before some patches that Yuvaraj is working on.
>
> Specifically the problem on pit and pi (and any exynos5250 / 5420 /
> 5800 / ... boards using t
Hello Andreas,
Thanks a lot for your feedback.
On 08/19/2014 08:37 PM, Andreas Färber wrote:
>> &mmc_2 {
>> +vmmc-supply = <&tps65090_fet4>;
>> +vqmmc-supply = <&vqmmc_sdcard>;
>> status = "okay";
>> num-slots = <1>;
>> supports-highspeed;
>
> A convention that I picked u
Hello Andreas,
On 08/19/2014 08:52 PM, Andreas Färber wrote:
>> +
>> +max77802-pmic@9 {
>> +compatible = "maxim,max77802";
>> +interrupt-parent = <&gpx3>;
>> +interrupts = <1 0>;
>
> <1 IRQ_TYPE_NONE>?
>
Indeed, I'll change both on v2. Thanks a lot.
>
>
Hello Andreas,
On 08/20/2014 12:21 PM, Javier Martinez Canillas wrote:
> Hello Andreas,
>
> Thanks a lot for your feedback.
>
> On 08/19/2014 08:37 PM, Andreas Färber wrote:
>>> &mmc_2 {
>>> + vmmc-supply = <&tps65090_fet4>;
>>> +
From: Naveen Krishna Chatradhi
This patch creates a thermistor fragment carrying the NTC Thermistor
nodes as children of the IIO based ADC.
This fragment is included in exynos5420-peach-pit.dts and
exynos5800-peach-pi.dts.
Signed-off-by: Naveen Krishna Chatradhi
Signed-off-by: Javier Martinez
From: Rahul Sharma
Adding regulators for hdmi for peach-pit board.
Signed-off-by: Rahul Sharma
Reviewed-by: Javier Martinez Canillas
Signed-off-by: Javier Martinez Canillas
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot
in the
the Chrome OS kernel 3.8 tree.
Signed-off-by: Javier Martinez Canillas
Tested-by: Naveen Krishna Chatradhi
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 372 +
arch/arm/boot/dts/exynos5800-peach-pi.dts | 372 +
2 files changed
From: Rahul Sharma
Adding regulators for HDMI for Peach-pi board.
Signed-off-by: Rahul Sharma
Reviewed-by: Javier Martinez Canillas
Signed-off-by: Javier Martinez Canillas
---
arch/arm/boot/dts/exynos5800-peach-pi.dts | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot
ags define instead of a magic number as suggested by
Andreas Färber.
The series is composed of the following patches:
Javier Martinez Canillas (2):
ARM: dts: Add Peach Pit and Pi dts entry for max77802 PMIC
ARM: dts: Add Peach Pit and Pi dts entry for ISL29018 sensor
Naveen Krishna Chatradhi
-by: Javier Martinez Canillas
---
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/exynos5420-peach-pit.dts
b/arch/arm/boot/dts/exynos5420-peach-pit.dts
index 94225e6
Hello Viresh,
On Wed, Aug 20, 2014 at 8:39 AM, Viresh Kumar wrote:
> On 20 August 2014 01:14, Tuomas Tynkkynen wrote:
>> There's actually a (mis-?)feature in git format-patch: a literal '---'
>> line in a commit message won't be escaped, so the patch notes can be
>> written in the commit message
applied this but fwiw:
Acked-by: Javier Martinez Canillas
Best regards,
Javier
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Hello Andreas,
On Wed, Aug 20, 2014 at 10:02 PM, Andreas Färber wrote:
>>
>> So the second "---" from Tuomas patch is actually the one generated by
>> git format-patch but that gets discarded by git am just like any other
>> text so it causes no harm when other apply the patches.
>>
>> If this no
;>>>
>>>> Am 20.08.2014 17:39, schrieb Javier Martinez Canillas:
>>>>>
>>>>> If this not the correct workflow and you have a better way to manage
>>>>> this, I would love to know about it.
>>
>>
>> Oh yes, this w
type
than IRQ_TYPE_NONE. The right approach is to get the IRQ flags
that was parsed by OF from the "interrupt" Device Tree propery.
Signed-off-by: Javier Martinez Canillas
---
drivers/input/touchscreen/atmel_mxt_ts.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
di
four entries but the driver dynamically allocates the
keymap array and does not limit the array size.
Signed-off-by: Javier Martinez Canillas
---
Documentation/devicetree/bindings/input/atmel,maxtouch.txt | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/Documentation
From: Sjoerd Simons
The Peach Pit and Pi boards have an Atmel maXTouch device.
Add the needed Device Tree nodes to support it.
Signed-off-by: Sjoerd Simons
[javier.martinez: added linux,gpio-keymap property and changed IRQ type]
Signed-off-by: Javier Martinez Canillas
---
With only this
Hello Tomasz,
Thanks a lot for your feedback.
On 08/07/2014 03:14 AM, Tomasz Figa wrote:
> Hi Javier,
>
>
> Have you observed an actual failure due to this? I believe that
Yes, I found this issue since the driver was not taking into account the value
defined in the edge/level type cells from t
Hello Fabio,
On 08/07/2014 03:35 AM, Fabio Estevam wrote:
> On Wed, Aug 6, 2014 at 10:08 PM, Javier Martinez Canillas
> wrote:
>
>> +&hsi2c_8 {
>> + status = "okay";
>> + clock-frequency = <333000>;
>
> Doesn't it work a
type
than IRQ_TYPE_NONE. The right approach is to get the IRQ flags
that was parsed by OF from the "interrupt" Device Tree propery.
Signed-off-by: Javier Martinez Canillas
---
This patch was first sent as a part of a two part series along
with [PATCH 2/2] Input: atmel_mxt_ts - Add keyc
901 - 1000 of 3499 matches
Mail list logo
