Hi Jaewon,
On Thu, Jun 19, 2014 at 7:33 AM, Jaewon Kim wrote:
> pwm-cells should be 3. Third cell is optional PWM flags. And This flag
> supported by this binding is PWM_POLARITY_INVERTED.
>
> Signed-off-by: Jaewon Kim
> ---
>
> Changes in v2:
> - Remove unnecessary handle.
>
> arch/arm/boot/d
On Thu, Jun 19, 2014 at 11:17 AM, Rahul Sharma wrote:
> Change bit from 2 to 9 for tv (mixer) sysmmu clock.
>
> Signed-off-by: Rahul Sharma
> ---
> Based on Kukjin's for-next branch.
>
> drivers/clk/samsung/clk-exynos5250.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --gi
Change bit from 2 to 9 for tv (mixer) sysmmu clock.
Signed-off-by: Rahul Sharma
---
Based on Kukjin's for-next branch.
drivers/clk/samsung/clk-exynos5250.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clk/samsung/clk-exynos5250.c
b/drivers/clk/samsung/clk-exyn
Hi,
On Wed, Jun 18, 2014 at 9:54 PM, Doug Anderson wrote:
> From: Vincent Palatin
>
> When the wake-up is triggered by the PMIC RTC, the RTC driver is trying
> to read the PMIC interrupt status over I2C and fails because the I2C
> controller is not resumed yet.
> Let's resume the I2C controller
The original code for the exynos i2c controller registered for the
"noirq" variants. However during review feedback it was moved to
SIMPLE_DEV_PM_OPS without anyone noticing that it meant we were no
longer actually "noirq" (despite functions named
exynos5_i2c_suspend_noirq and exynos5_i2c_resume_n
From: Vincent Palatin
When the wake-up is triggered by the PMIC RTC, the RTC driver is trying
to read the PMIC interrupt status over I2C and fails because the I2C
controller is not resumed yet.
Let's resume the I2C controller earlier in the _noirq phase
(as other hardwares are doing), so we can p
Thanks Inki,
On 19 June 2014 09:34, Inki Dae wrote:
> On 2014년 06월 18일 22:42, Rahul Sharma wrote:
>> HDMI probe proceeds with dummy regulators when the regulators
>> are not provided in DT node or regulator provider has not get
>> probed or failed to register the regulators.
>>
>> This patch modi
Hi Thomas,
On 06/19/2014 01:21 PM, Thomas Abraham wrote:
> On Wed, Jun 18, 2014 at 2:09 PM, Chanwoo Choi wrote:
>> This patchset use cpufreq-cpu0 driver to support Exynos3250 cpufreq. So, this
>> patchset is based on following patchset[1] by Thomas Abraham.
>> [1] http://www.spinics.net/lists/ar
On Wed, Jun 18, 2014 at 2:09 PM, Chanwoo Choi wrote:
> This patchset use cpufreq-cpu0 driver to support Exynos3250 cpufreq. So, this
> patchset is based on following patchset[1] by Thomas Abraham.
> [1] http://www.spinics.net/lists/arm-kernel/msg339392.html
>
> Changes from v1:
> - Rebased on new
On Wed, Jun 18, 2014 at 1:21 PM, Viresh Kumar wrote:
> On 17 June 2014 20:55, Thomas Abraham wrote:
>> Changes since v5:
>> - Configuration data for cpu clock block is embedded with the code. The cpu
>> clock
>> logic can later to extended to obtain this data from DT.
>> - Excluded the support
On 2014년 06월 18일 22:42, Rahul Sharma wrote:
> HDMI probe proceeds with dummy regulators when the regulators
> are not provided in DT node or regulator provider has not get
> probed or failed to register the regulators.
>
> This patch modify hdmi driver to defer the probe in case the
> regulators a
On Wed, Jun 18, 2014 at 7:41 PM, Tim Kryger wrote:
> On Wed, Jun 18, 2014 at 4:33 AM, Sachin Kamat wrote:
>> Hi Tim,
>>
>> I see the below error on Exynos4210 based Origen board with linux-next
>> (20140618).
>> Reverting the below commit works fine.
>>
>
Hi, all.
On 06/18/2014 08:22 PM, Sachin Kamat wrote:
> Hi Ulf,
>
> On Wed, Jun 18, 2014 at 4:43 PM, Ulf Hansson wrote:
>> On 18 June 2014 13:10, Sachin Kamat wrote:
>>> Hi Jaehoon,
>>>
>>> On Wed, Jun 18, 2014 at 3:50 PM, Jaehoon Chung
>>> wrote:
Hi, Sachin.
Did you check the b
pwm-cells should be 3. Third cell is optional PWM flags. And This flag
supported by this binding is PWM_POLARITY_INVERTED.
Signed-off-by: Jaewon Kim
---
Changes in v2:
- Remove unnecessary handle.
arch/arm/boot/dts/exynos4.dtsi |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --
Hi,
On 06/18/2014 02:57 PM, Arnd Bergmann wrote:
> On Tuesday 17 June 2014 23:26:22 Tomasz Figa wrote:
>> On 17.06.2014 17:42, Arnd Bergmann wrote:
>>> This seems like a reasonable way of solving the problem, but I think
>>> there is an even better one that we have about in the past: if we
>>> pro
Amit,
Thanks for posting!
On Wed, Jun 18, 2014 at 4:31 AM, Amit Daniel Kachhap
wrote:
> This patch register the exynos mct clocksource as the current timer
> as it has constant clock rate. This will generate correct udelay for the
> exynos platform and avoid using unnecessary calibrated jiffies.
From: Bill Richardson
struct cros_ec_device has a superfluous "name" field. We can get all the
debugging info we need from the existing ec_name and phys_name fields, so
let's take out the extra field.
The printout also has sufficient info in it without explicitly adding
the transport. Before th
From: Bill Richardson
This comment was incorrect, so update it.
Signed-off-by: Bill Richardson
Signed-off-by: Simon Glass
Signed-off-by: Doug Anderson
Acked-by: Lee Jones
---
Changes in v2: None
include/linux/mfd/cros_ec.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
From: Bill Richardson
Remove the three wrapper functions that talk to the EC without passing all
the desired arguments and just use the underlying communication function
that passes everything in a struct intead.
This is internal code refactoring only. Nothing should change.
Signed-off-by: Bill
From: Bill Richardson
This is some internal structure reorganization / renaming to prepare
for future patches that will add a userspace API to cros_ec. There
should be no visible changes.
Signed-off-by: Bill Richardson
Signed-off-by: Doug Anderson
Acked-by: Lee Jones
---
Changes in v2: None
From: Bill Richardson
The lower-level driver may want to provide its own buffers. If so,
there's no need to allocate new ones. This already happens to work
just fine (since we check for size of 0 and use devm allocation), but
it's good to document it.
[dianders: Resolved conflicts; documented t
From: Simon Glass
Some commands take a while to execute. Use -EAGAIN to signal this to the
caller.
Signed-off-by: Simon Glass
Signed-off-by: Doug Anderson
Acked-by: Lee Jones
---
Changes in v2: None
drivers/mfd/cros_ec_spi.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/
From: Andrew Bresticker
If we receive EC interrupts after the cros_ec driver has probed, but
before the cros_ec_keyb driver has probed, the cros_ec IRQ handler
will not run the cros_ec_keyb notifier and the EC will leave the IRQ
line asserted. The cros_ec IRQ handler then returns IRQ_HANDLED and
From: Bill Richardson
Just because the host was able to talk to the EC doesn't mean that the EC
was happy with what it was told. Errors in communincation are not the same
as error messages from the EC itself.
This change lets the EC report its errors separately.
[dianders: Added common function
From: Bill Richardson
When communicating with the EC, the cmd_xfer() function should return the
number of bytes it received from the EC, or negative on error.
Signed-off-by: Bill Richardson
Signed-off-by: Doug Anderson
Acked-by: Lee Jones
Reviewed-by: Simon Glass
---
Changes in v2: None
dr
This is a batch of cleanup patches picked from the ChromeOS 3.8 kernel
tree and applied to ToT. Most of these patches were authored by Bill
Richardson (CCed). Where appropriate I've squashed patches together,
though I have erred on the side of keeping patches logically distinct
rather than squash
From: Bill Richardson
The members of struct cros_ec_device were improperly commented, and
intermixed the private and public sections. This is just cleanup to make it
more obvious what goes with what.
[dianders: left lock in the structure but gave it the name that will
eventually be used.]
Signe
Lee,
On Wed, Jun 18, 2014 at 9:46 AM, Lee Jones wrote:
> On Wed, 18 Jun 2014, Doug Anderson wrote:
>
>> Lee,
>>
>> On Wed, Jun 18, 2014 at 12:55 AM, Lee Jones wrote:
>> > On Mon, 16 Jun 2014, Doug Anderson wrote:
>> >
>> >> From: Bill Richardson
>> >>
>> >> Preparing the way for the LPC device,
On Wed, 18 Jun 2014, Doug Anderson wrote:
> Lee,
>
> On Wed, Jun 18, 2014 at 12:55 AM, Lee Jones wrote:
> > On Mon, 16 Jun 2014, Doug Anderson wrote:
> >
> >> From: Bill Richardson
> >>
> >> Preparing the way for the LPC device, which is just a plaform_device
> >> without
> >> interrupts.
> >>
On Wed, 18 Jun 2014, Doug Anderson wrote:
> Lee,
>
> On Wed, Jun 18, 2014 at 12:57 AM, Lee Jones wrote:
> > On Mon, 16 Jun 2014, Doug Anderson wrote:
> >
> >> From: Bill Richardson
> >>
> >> This comment was incorrect, so update it.
> >>
> >> Signed-off-by: Bill Richardson
> >> Signed-off-by:
Lee,
On Wed, Jun 18, 2014 at 12:53 AM, Lee Jones wrote:
> On Mon, 16 Jun 2014, Doug Anderson wrote:
>
>> From: Bill Richardson
>>
>> The lower-level driver may want to provide its own buffers. If so,
>> there's no need to allocate new ones. This already happens to work
>> just fine (since we ch
Lee,
On Wed, Jun 18, 2014 at 12:57 AM, Lee Jones wrote:
> On Mon, 16 Jun 2014, Doug Anderson wrote:
>
>> From: Bill Richardson
>>
>> This comment was incorrect, so update it.
>>
>> Signed-off-by: Bill Richardson
>> Signed-off-by: Simon Glass
>
> How many people did it take to write this patch?
Signed-off-by: Sylwester Nawrocki
---
.../bindings/sound/samsung,odroidx2-max98090.txt | 35
1 file changed, 35 insertions(+)
create mode 100644
Documentation/devicetree/bindings/sound/samsung,odroidx2-max98090.txt
diff --git
a/Documentation/devicetree/bindings/sound/
Lee,
On Wed, Jun 18, 2014 at 12:55 AM, Lee Jones wrote:
> On Mon, 16 Jun 2014, Doug Anderson wrote:
>
>> From: Bill Richardson
>>
>> Preparing the way for the LPC device, which is just a plaform_device without
>> interrupts.
>>
>> Signed-off-by: Bill Richardson
>> Signed-off-by: Doug Anderson
This patch adds the sound subsystem driver for Odroid-X2 and
Odroid-U3 boards. The codec works in I2S master mode; there are
2 separate audio routing paths defined as there are differences
in the signal routing between the X2 and U3 boards, i.e. U3 uses
single jack for headphones and microphone.
S
This series adds basic sound support for the Odroid X2/U3 boards.
It relies on specific Exynos Audio Subsystem clock parent and
frequencies being pre-configured.
My full testing git branch has been pushed to:
git://linuxtv.org/snawrocki/samsung.git v3.16-rc1-odroid-sound-clk
It can be browsed at:
Hi Tomasz,
On Tue, May 20, 2014 at 5:43 PM, Tomasz Figa wrote:
> Since the block responsible for handling the pin is PMU, not CMU,
> a separate driver, that binds to PMU node is required and acquires
> all input clocks by standard DT clock look-up. This way we don't need
> any cross-IP block driv
Ensure the clock provider is not registered until after all its related
clocks were created and are ready to use. Currently there are races
possible and any (of_)clk_get() call right after a clock provider's
clk_init_cb callback call may fail.
Signed-off-by: Sylwester Nawrocki
---
NOTE: Tested o
On Wed, 18 Jun 2014, Abhilash Kesavan wrote:
> Turning off a cluster when all 4 cores of the cluster are powered off
> saves power significantly. Powering off the A15 L2 alone gives around
> 100mW in savings. Add support for powering off the A15/A7 clusters on
> exynos5420/5800.
>
> The patch ena
polling the cluster power
status register.
Signed-off-by: Abhilash Kesavan
---
The patch is based on Linux-next 20140618. It has been tested on an
exynos5420-based chromebook using the "/dev/bL_switcher" interface as
well as the script provided by Nicolas Pitre and Dave Martin [1].
Patch
On Wed, Jun 18, 2014 at 4:33 AM, Sachin Kamat wrote:
> Hi Tim,
>
> I see the below error on Exynos4210 based Origen board with linux-next
> (20140618).
> Reverting the below commit works fine.
>
> Commit: 8d02e775a6 "mmc: sdhci: Use mmc core regulator in
On Wed, 18 Jun 2014, Javier Martinez Canillas wrote:
> Hello Lee,
>
> Thanks a lot for your feedback.
>
> On 06/17/2014 11:17 PM, Lee Jones wrote:
> >> The MAX77802 PMIC has 10 high-efficiency Buck and 32 Low-dropout
> >> (LDO) regulators. This patch adds support for all these regulators
> >> fo
Adding regulators for hdmi for peach-pit board.
Signed-off-by: Rahul Sharma
---
Based on for-next branch in Kukjin's tree.
Dependent on:
1) PMIC DT patch at http://www.gossamer-threads.com/lists/linux/kernel/1945703
2) tps65090 DT patch at https://lkml.org/lkml/2014/6/13/483
arch/arm/boot/dts/e
HDMI probe proceeds with dummy regulators when the regulators
are not provided in DT node or regulator provider has not get
probed or failed to register the regulators.
This patch modify hdmi driver to defer the probe in case the
regulators are not available.
Signed-off-by: Rahul Sharma
---
Base
On Tuesday 17 June 2014 23:26:22 Tomasz Figa wrote:
> On 17.06.2014 17:42, Arnd Bergmann wrote:
> > This seems like a reasonable way of solving the problem, but I think
> > there is an even better one that we have about in the past: if we
> > promote syscon from a platform driver into a a drivers/b
mixer_wait_for_vblank function expects that the upcoming
vsync interrupt handler routine will clear the
wait_vsync_event atomic variable.
For this to happen, interrupts should be enabled and
disabled properly.
Signed-off-by: Rahul Sharma
---
drivers/gpu/drm/exynos/exynos_mixer.c |4
1
Mixer soft reset is a recommended step before reconfiguring
the mixer after power on. Mixer looses the previous state of
DMAs if soft reset. This is the recommendation from the
hardware team.
Signed-off-by: Rahul Sharma
---
drivers/gpu/drm/exynos/exynos_mixer.c |2 ++
1 file changed, 2 inser
Allowing only one layer update per vsync can cause issues
while there are update available for both layers. There is
a good amount of possibility to loose updates if we allow
single update per vsync.
Signed-off-by: Rahul Sharma
---
drivers/gpu/drm/exynos/exynos_mixer.c |7 +--
1 file cha
Mixer should be power gated only after it is gracefully stopped.
The recommended sequence is to Stop the mixer and wait till
it enters to IDLE state before gating the clocks and power to
the mixer.
Signed-off-by: Rahul Sharma
---
drivers/gpu/drm/exynos/exynos_mixer.c | 15 +++
driv
Power state variable holds the state of the mixer device.
Power on and power off functions are toggling these variable
at wrong place.
State variable should be changed to true only after Runtime
PM and clocks are enabled. Else it may result to a situation
where mixer registers are accessed with de
Fixes for various issues which are to Power On/Off sequence,
Layer update, waiting for vblank in exynos mixer driver.
This series is based on exynos-drm-fixes branch in Inki dae's tree.
Rahul Sharma (5):
drm/exynos: set power state variable after enabling clocks and power
drm/exynos: stop mix
Hi Tim,
I see the below error on Exynos4210 based Origen board with linux-next
(20140618).
Reverting the below commit works fine.
Commit: 8d02e775a6 "mmc: sdhci: Use mmc core regulator infrastucture"
Any ideas?
***
-- [2.068992] sdhci: Secure Digital Host Controller
This patch register the exynos mct clocksource as the current timer
as it has constant clock rate. This will generate correct udelay for the
exynos platform and avoid using unnecessary calibrated jiffies. This change
have been tested on exynos5420 based board.
Signed-off-by: Amit Daniel Kachhap
-
Hi Ulf,
On Wed, Jun 18, 2014 at 4:43 PM, Ulf Hansson wrote:
> On 18 June 2014 13:10, Sachin Kamat wrote:
>> Hi Jaehoon,
>>
>> On Wed, Jun 18, 2014 at 3:50 PM, Jaehoon Chung
>> wrote:
>>> Hi, Sachin.
>>>
>>> Did you check the below patch?
>>> https://patchwork.kernel.org/patch/4346781/
>>
>> Th
On 18 June 2014 13:10, Sachin Kamat wrote:
> Hi Jaehoon,
>
> On Wed, Jun 18, 2014 at 3:50 PM, Jaehoon Chung wrote:
>> Hi, Sachin.
>>
>> Did you check the below patch?
>> https://patchwork.kernel.org/patch/4346781/
>
> Thanks for the patch. But even with this patch, I continue to get the
> aforeme
Hi Jaehoon,
On Wed, Jun 18, 2014 at 3:50 PM, Jaehoon Chung wrote:
> Hi, Sachin.
>
> Did you check the below patch?
> https://patchwork.kernel.org/patch/4346781/
Thanks for the patch. But even with this patch, I continue to get the
aforementioned crash.
>
> I will resend the patch after includin
ehoon Chung
On 06/18/2014 07:11 PM, Sachin Kamat wrote:
> Hi Jaehoon,
>
> I get the below crash on Exyos5250 based Arndale board with linux-next
> (20140618) kernel.
> Looks like the following patch is causing it
> Commit da118915cc72 " mmc: dw_mmc: replace "disable-
On Wed, Jun 18, 2014 at 12:37:16AM +0100, Thierry Reding wrote:
> On Tue, Jun 17, 2014 at 01:18:11PM +0100, Will Deacon wrote:
> > On Tue, Jun 17, 2014 at 12:58:30PM +0100, Thierry Reding wrote:
> > > On Mon, Jun 16, 2014 at 01:57:04PM +0100, Will Deacon wrote:
> > > > On Wed, Jun 04, 2014 at 10:12
Hi Mike,
Do you have any comments about this patch?
The patch is needed to provide a clean fix for recently
broken support for HDMI on Exynos4210 SoC in mainline.
Regards,
Tomasz Stanislawski
On 05/01/2014 12:19 AM, Tomasz Figa wrote:
> Mike,
>
> On 08.04.2014 17:45, Tomasz Figa wrote:
>> Hi,
>
Hi Jaehoon,
I get the below crash on Exyos5250 based Arndale board with linux-next
(20140618) kernel.
Looks like the following patch is causing it
Commit da118915cc72 " mmc: dw_mmc: replace "disable-wp" from slot's
quirk to host's quirk"
Reverting the above pat
In the move to this clock driver the hookups for the SPI clocks were
dropped, which causes my system Cragganmore (s3c6410 based) to be unable
to locate any spibus clocks. This patch adds them back in.
When taking the clock from the epll clock (SCLK) the rates on the SPI
bus are incorrect, this nee
Hello Lee,
On 06/18/2014 10:32 AM, Lee Jones wrote:
>> >> +config MFD_MAX77802
>> >> + tristate "Maxim Integrated MAX77802 PMIC Support"
>> >> + depends on I2C=y
>> >> + select MFD_CORE
>> >> + select REGMAP_I2C
>> >> + select REGMAP_IRQ
>> >> + select IRQ_DOMAIN
>> >> + help
>> >> + Say yes her
Hello Lee,
Thanks a lot for your feedback.
On 06/17/2014 11:17 PM, Lee Jones wrote:
>> The MAX77802 PMIC has 10 high-efficiency Buck and 32 Low-dropout
>> (LDO) regulators. This patch adds support for all these regulators
>> found on the MAX77802 PMIC and is based on a driver added by Simon
>> Gl
On Tue, Jun 17, 2014 at 03:50:25PM +0100, Stuart Yoder wrote:
> > > I think for simple masters (i.e. those that have all their StreamIDs
> > > under control of one driver), then setting something during attach (or
> > > add?) based on the DT could work pretty well. The other case is when we
> > > h
Hello Doug,
On 06/17/2014 10:57 PM, Doug Anderson wrote:
> Javier,
>
> On Mon, Jun 16, 2014 at 11:02 AM, Javier Martinez Canillas
> wrote:
>> @@ -127,15 +175,48 @@ static int max77686_i2c_probe(struct i2c_client *i2c,
>> }
>> i2c_set_clientdata(max77686->rtc, max77686);
>>
>> -
> From: Prathyush K
>
> Set the device as wakeup capable and register the wakeup source.
>
> Note: Though it makes more sense to have the SPI framework do this,
> (either via device tree or by board_info)
> this change is as per an existing mail chain:
> https://lkml.org/lkml/2009/8/27/291
>
>
Hi Tomasz,
On 06/18/2014 05:35 PM, Tomasz Figa wrote:
> Hi Chanwoo,
>
> On 18.06.2014 04:21, Chanwoo Choi wrote:
>> This patch add DT binding documentation for Exynos3250 ADC IP. Exynos3250 has
>> special clock ('sclk_tsadc') for ADC which provide clock to internal ADC.
>>
>> Signed-off-by: Chanw
Hi Tomasz,
On 06/18/2014 05:37 PM, Tomasz Figa wrote:
> Hi Chanwoo,
>
> On 18.06.2014 04:21, Chanwoo Choi wrote:
>> This patchset fix wrong compatible string for Exynos3250 ADC. Exynos3250 SoC
>> need to control only special clock for ADC. Exynos SoC except for Exynos3250
>> has not included spec
This patchset use cpufreq-cpu0 driver to support Exynos3250 cpufreq. So, this
patchset is based on following patchset[1] by Thomas Abraham.
[1] http://www.spinics.net/lists/arm-kernel/msg339392.html
Changes from v1:
- Rebased on new patchset[1] by Thomas Abraham
- Modify clk-cpu.c to support Exyn
This patch add cpu clock table (CPU clock and voltage) to support generic
cpufreq-cpu0 driver for Exynos3250.
Signed-off-by: Chanwoo Choi
Acked-by: Kyungmin Park
---
arch/arm/boot/dts/exynos3250.dtsi | 15 +++
1 file changed, 15 insertions(+)
diff --git a/arch/arm/boot/dts/exynos32
This patch use cpu-clock provider type to support cpufreq for Exynos3250. The
clock-exynos3250.c didn't add separate 'arm_clk' divider for 'div_core2'.
The 'div_core2' can be represented as a cpu-clock type and then use 'div_core2'
directly to change cpu clock.
Signed-off-by: Chanwoo Choi
Acked-b
This patch add support for a new clock type for Exynos3250 CPU clock provider
and modify little difference of DIV_CPU0 between Exynos4 and Exynos3250.
Signed-off-by: Chanwoo Choi
Acked-by: Kyungmin Park
---
drivers/clk/samsung/clk-cpu.c | 31 +++
1 file changed, 31 i
Hi Chanwoo,
On 18.06.2014 04:21, Chanwoo Choi wrote:
> This patchset fix wrong compatible string for Exynos3250 ADC. Exynos3250 SoC
> need to control only special clock for ADC. Exynos SoC except for Exynos3250
> has not included special clock for ADC. The exynos ADC driver can control
> special c
Hi Chanwoo,
On 18.06.2014 04:21, Chanwoo Choi wrote:
> This patch add DT binding documentation for Exynos3250 ADC IP. Exynos3250 has
> special clock ('sclk_tsadc') for ADC which provide clock to internal ADC.
>
> Signed-off-by: Chanwoo Choi
> Acked-by: Kyungmin Park
> ---
> .../devicetree/bind
> >> +config MFD_MAX77802
> >> + tristate "Maxim Integrated MAX77802 PMIC Support"
> >> + depends on I2C=y
> >> + select MFD_CORE
> >> + select REGMAP_I2C
> >> + select REGMAP_IRQ
> >> + select IRQ_DOMAIN
> >> + help
> >> +Say yes here to support for Maxim Integrated MAX77802.
> >> +
On Tue, 17 Jun 2014, Tomasz Figa wrote:
> On 17.06.2014 17:42, Arnd Bergmann wrote:
> > On Tuesday 17 June 2014 17:32:44 Tomasz Figa wrote:
> >> Currently a syscon entity can be only registered directly through a
> >> platform device that binds to a dedicated driver. However in certain use
> >> cas
Hi Chanwoo,
On 18.06.2014 04:20, Chanwoo Choi wrote:
> This patch control special clock for ADC in Exynos series's FSYS block.
> If special clock of ADC is registerd on clock list of common clk framework,
> Exynos ADC drvier have to control this clock.
>
> Exynos3250/Exynos4/Exynos5 has 'adc' clo
On Mon, 16 Jun 2014, Doug Anderson wrote:
> From: Bill Richardson
>
> This comment was incorrect, so update it.
>
> Signed-off-by: Bill Richardson
> Signed-off-by: Simon Glass
How many people did it take to write this patch? ;)
Acked-by: Lee Jones
> Signed-off-by: Doug Anderson
> ---
>
Hi Chanwoo,
On 18.06.2014 04:20, Chanwoo Choi wrote:
> This patchset add 'exynos_adc_ops' structure which includes some functions
> to control ADC operation according to ADC version (v1 or v2).
>
> Signed-off-by: Chanwoo Choi
> Acked-by: Kyungmin Park
> ---
> drivers/iio/adc/exynos_adc.c | 174
On Mon, 16 Jun 2014, Doug Anderson wrote:
> From: Bill Richardson
>
> Preparing the way for the LPC device, which is just a plaform_device without
> interrupts.
>
> Signed-off-by: Bill Richardson
> Signed-off-by: Doug Anderson
> ---
> drivers/mfd/cros_ec.c | 26 +-
>
On Mon, 16 Jun 2014, Doug Anderson wrote:
> From: Bill Richardson
>
> The lower-level driver may want to provide its own buffers. If so,
> there's no need to allocate new ones. This already happens to work
> just fine (since we check for size of 0 and use devm allocation), but
> it's good to do
On 17 June 2014 20:55, Thomas Abraham wrote:
> Changes since v5:
> - Configuration data for cpu clock block is embedded with the code. The cpu
> clock
> logic can later to extended to obtain this data from DT.
> - Excluded the support for Exynos4x12 SoC since the work on boost OPP
> bindings i
On Mon, 16 Jun 2014, Doug Anderson wrote:
> From: Bill Richardson
>
> The members of struct cros_ec_device were improperly commented, and
> intermixed the private and public sections. This is just cleanup to make it
> more obvious what goes with what.
>
> [dianders: left lock in the structure b
On Mon, 16 Jun 2014, Doug Anderson wrote:
> From: Simon Glass
>
> Some commands take a while to execute. Use -EAGAIN to signal this to the
> caller.
>
> Signed-off-by: Simon Glass
> Signed-off-by: Doug Anderson
> ---
> drivers/mfd/cros_ec_spi.c | 6 ++
> 1 file changed, 6 insertions(+)
On Mon, 16 Jun 2014, Doug Anderson wrote:
> From: Bill Richardson
>
> This is some internal structure reorganization / renaming to prepare
> for future patches that will add a userspace API to cros_ec. There
> should be no visible changes.
>
> Signed-off-by: Bill Richardson
> Signed-off-by: D
On Mon, 16 Jun 2014, Doug Anderson wrote:
> From: Bill Richardson
>
> struct cros_ec_device has a superfluous "name" field. We can get all the
> debugging info we need from the existing ec_name and phys_name fields, so
> let's take out the extra field.
>
> Signed-off-by: Bill Richardson
> Sign
> >> diff --git a/drivers/input/keyboard/cros_ec_keyb.c
> >> b/drivers/input/keyboard/cros_ec_keyb.c
> >> index 4083796..dc37b6b 100644
> >> --- a/drivers/input/keyboard/cros_ec_keyb.c
> >> +++ b/drivers/input/keyboard/cros_ec_keyb.c
> >> @@ -191,8 +191,18 @@ static void cros_ec_keyb_close(struct
On Tue, 17 Jun 2014, Doug Anderson wrote:
> Simon,
>
> On Tue, Jun 17, 2014 at 8:43 PM, Simon Glass wrote:
> >> diff --git a/drivers/mfd/cros_ec_spi.c b/drivers/mfd/cros_ec_spi.c
> >> index 09ca789..4d34f1c 100644
> >> --- a/drivers/mfd/cros_ec_spi.c
> >> +++ b/drivers/mfd/cros_ec_spi.c
> >> @@
On Mon, 16 Jun 2014, Doug Anderson wrote:
> From: Bill Richardson
>
> When communicating with the EC, the cmd_xfer() function should return the
> number of bytes it received from the EC, or negative on error.
>
> Signed-off-by: Bill Richardson
> Signed-off-by: Doug Anderson
> ---
> drivers/i
89 matches
Mail list logo
