I also want to point, that irq resource in arch/arm/plat-samsung/devs.c
for s3c2410-spi driver on S3C2443 points to wrong IRQ (SPI0 instead of
SPI1). I've solved it with board specific code, but it is not most
correct way, i think.
20.11.2012 15:46, Kukjin Kim пишет:
Alexander Varnin wrote:
On 22 November 2012 06:52, Zhang Rui wrote:
> On Thu, 2012-11-08 at 09:56 +0530, Amit Daniel Kachhap wrote:
>> This modification adds 2 new thermal trend type THERMAL_TREND_RAISE_FULL
>> and THERMAL_TREND_DROP_FULL. This thermal trend can be used to quickly
>> jump to the upper or lower cooling le
On Thu, 2012-11-22 at 10:11 +0530, Amit Kachhap wrote:
> On 22 November 2012 06:52, Zhang Rui wrote:
> > On Thu, 2012-11-08 at 09:56 +0530, Amit Daniel Kachhap wrote:
> >> This modification adds 2 new thermal trend type THERMAL_TREND_RAISE_FULL
> >> and THERMAL_TREND_DROP_FULL. This thermal trend
S3C2443 CPU has a problem with incorrect reading from EXTINTn
registers. So s3c_irqext_type function wrongly modifies them.
So add special function for s3c2443, to handle this case.
Signed-off-by: Alexander Varnin
---
arch/arm/mach-s3c24xx/s3c2443.c |8
arch/arm/plat-s3c24xx/irq.c |
22.11.2012 12:22, Kukjin Kim пишет:
SPI1). I've solved it with board specific code, but it is not most
correct way, i think.
Hmm, if provided platform_device is in plat-samsung/devs.c cannot support, we
can do as you said temporarily but we know it's wrong way because the value
depends on SoC
Hi Rafael,
On Wednesday 21 of November 2012 21:47:42 Rafael J. Wysocki wrote:
> On Wednesday, November 21, 2012 02:52:26 PM Tomasz Figa wrote:
> > On Tuesday 13 of November 2012 10:26:12 Tomasz Figa wrote:
> > > On Exynos SoCs all cores share the same frequency setting, so
> > > changing
> > > fre
Doug Anderson wrote:
>
> From: Olof Johansson
>
> Add support for using UART3 for DEBUG_LL on exynos.
>
> [dianders: added depend on ARCH_EXYNOS.]
>
> Signed-off-by: Olof Johansson
> Signed-off-by: Doug Anderson
>
> ---
> Changes in v2:
> - Matched Olof's commit message.
> - Added ARCH_EXYN
Sylwester Nawrocki wrote:
>
> This patch adds default helper functions for the camera port
> pin configuration. Whenever pinctrl support for s3c24xx/s3c64xx
> SoCs is available these code should be removed and proper pinctrl
> API should be used in the CAMIF driver.
>
> Signed-off-by: Sylwester N
Sylwester Nawrocki wrote:
>
> The s3c-camif driver uses "camera" clock conn_id for the "camif-upll"
> (s3c244x) and "camera" (s3c64xx) platform clock. By adding this new
> clkdev entry the platform differences are isolated from the driver.
>
> Signed-off-by: Sylwester Nawrocki
> ---
> arch/arm/
Dear Mr. Ham,
Thanks for your comments.
On 21 November 2012 20:01, MyungJoo Ham wrote:
> On Wed, Nov 21, 2012 at 11:23 PM, Thomas Abraham
> wrote:
>> If gpio based voltage selection for buck 1/2/5 are not used, then the
>> execution
>> of gpio dvs setup code during probe can be skipped complet
Doug Anderson wrote:
>
> On Tue, Nov 20, 2012 at 8:09 PM, Mark Brown
> wrote:
> > On Tue, Nov 20, 2012 at 02:27:04PM -0800, Doug Anderson wrote:
> >> From: Padmavathi Venna
> >>
> >> Get the i2c bus number that the device is connected to using the alias
> >> id. This makes debugging / grokking
Touching some System MMU needs its master devices' clock to be enabled
before. This commit adds clk_ops.set_parent of gating clocks of System
MMU to ensure gating clocks of System MMU's mater devices are enabled
when enabling gating clocks of System MMU.
Signed-off-by: KyongHo Cho
---
arch/arm/m
Since kmalloc() does not guarantee the alignment of 1KB when it
allocates 1KB, it is required to allocate lv2 page table from
own slab that guarantees alignment of 1KB.
Signed-off-by: KyongHo Cho
---
drivers/iommu/exynos-iommu.c | 24
1 file changed, 20 insertions(+), 4
Hi Kgene,
On Thursday 22 of November 2012 15:52:14 Kukjin Kim wrote:
> Tomasz Figa wrote:
> > On Monday 12 of November 2012 09:55:30 Russell King - ARM Linux wrote:
> > > On Mon, Nov 12, 2012 at 04:39:28PM +0900, Kukjin Kim wrote:
> > > > (+ Russell King)
> > >
> > > I think there's still an amou
This commit adds device tree support for System MMU.
Signed-off-by: KyongHo Cho
---
drivers/iommu/Kconfig| 2 +-
drivers/iommu/exynos-iommu.c | 289 ++-
2 files changed, 177 insertions(+), 114 deletions(-)
diff --git a/drivers/iommu/Kconfig b/dr
[PATCH v4 08/12] iommu/exynos: set System MMU as the parent of client device
This commit sets System MM as the parent of the client device for
power management. If System MMU is the parent of a device, it is
guaranteed that System MMU is suspended later than the device and
resumed earlier. Runtime
Since acquiring read_lock is not more frequent than write_lock, it is
not beneficial to use rwlock, this commit changes rwlock to spinlock.
Signed-off-by: KyongHo Cho
---
drivers/iommu/exynos-iommu.c | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff -
This commit adds System MMU name to the driver data of each System
MMU. It is used by fault information.
Signed-off-by: KyongHo Cho
---
drivers/iommu/exynos-iommu.c | 100 ---
1 file changed, 76 insertions(+), 24 deletions(-)
diff --git a/drivers/iommu/ex
This commit adds debugfs directory and nodes for inspecting internal
state of System MMU.
Signed-off-by: KyongHo Cho
---
drivers/iommu/exynos-iommu.c | 204 +--
1 file changed, 198 insertions(+), 6 deletions(-)
diff --git a/drivers/iommu/exynos-iommu.c b/
On Wednesday, November 21, 2012 10:23:02 PM Tomasz Figa wrote:
> Hi Rafael,
>
> On Wednesday 21 of November 2012 21:47:42 Rafael J. Wysocki wrote:
> > On Wednesday, November 21, 2012 02:52:26 PM Tomasz Figa wrote:
> > > On Tuesday 13 of November 2012 10:26:12 Tomasz Figa wrote:
> > > > On Exynos S
This commit adds System MMU nodes to DT of Exynos SoCs.
Signed-off-by: KyongHo Cho
---
.../devicetree/bindings/arm/exynos/system-mmu.txt | 86
arch/arm/boot/dts/exynos4210.dtsi | 96 ++
arch/arm/boot/dts/exynos4x12.dtsi | 124
This removes System MMU initialization from arch/arm/mach-exynos/
to move them to DT and the exynos-iommu driver except gating clock
definitions.
Signed-off-by: KyongHo Cho
---
arch/arm/mach-exynos/Kconfig | 5 -
arch/arm/mach-exynos/Makefile | 1 -
arch/arm/mach-e
Hi,
wp-gpios has been implemented in dw_mmc-exynos.c
It can be reused for EXYNOS platform? We need to modify some though.
Thanks,
Seungwon Jeon
On Thursday, November 22, 2012, Doug Anderson wrote:
> On some SoCs (like exynos5250) you need to use an external GPIO for
> write protect. Add suppor
On Thursday, November 22, 2012, Doug Anderson wrote:
> On Wed, Nov 21, 2012 at 5:42 PM, Seungwon Jeon wrote:
> > Hi,
> >
> > wp-gpios has been implemented in dw_mmc-exynos.c
> > It can be reused for EXYNOS platform? We need to modify some though.
>
> Yup, I've seen that. Patch 1/2 ("mmc: dw_mmc
Exynos4412 uses different information register for each core. This patch
adjusts the bring-up code to take that into account.
Signed-off-by: Tomasz Figa
Reviewed-by: Kyungmin Park
---
arch/arm/mach-exynos/platsmp.c | 30 --
1 file changed, 24 insertions(+), 6 deletio
Some boards are running with secure firmware running in TrustZone secure
world, which changes the way some things have to be initialized.
This patch adds an interface for platforms to specify available firmware
operations and call them.
A wrapper macro, call_firmware_op(), checks if the operation
On some SoCs (like exynos5250) you need to use an external GPIO for
write protect. Add support for wp-gpios to the core dw_mmc driver
since it could be useful across multiple SoCs.
With this change I am able to make use of the write protect for the
external SD slot on exynos5250-snow.
Signed-off
On TrustZone-enabled boards the non-secure SYSRAM is used for secondary
CPU bring-up, so add a mapping for it.
Signed-off-by: Kyungmin Park
Signed-off-by: Tomasz Figa
---
arch/arm/mach-exynos/common.c| 35
arch/arm/mach-exynos/include/mach/map.h
Some Exynos-based boards are running with secure firmware running in
TrustZone secure world, which changes the way some things have to be
initialized.
This series adds support for specifying firmware operations, implements
some firmware operations for Exynos secure firmware and adds a method of
en
Boards using secure firmware must use different CPU boot registers and
call secure firmware to boot the CPU.
Signed-off-by: Kyungmin Park
Signed-off-by: Tomasz Figa
---
arch/arm/mach-exynos/platsmp.c | 32 +++-
1 file changed, 27 insertions(+), 5 deletions(-)
diff -
Some boards use secure monitor calls to communicate with secure
firmware.
This patch adds exynos_smc function which uses smc assembly instruction
to do secure monitor calls.
Signed-off-by: Kyungmin Park
Signed-off-by: Tomasz Figa
---
arch/arm/mach-exynos/Makefile | 5 +
arch/arm/mach-
Some Exynos-based boards contain secure firmware and must use firmware
operations to set up some hardware.
This patch adds firmware operations for Exynos secure firmware and a way
for board code and device tree to specify that they must be used.
Example of use:
In board code:
...MACHINE
On 11/22/2012 07:03 AM, Doug Anderson wrote:
> On some SoCs (like exynos5250) you need to use an external GPIO for
> write protect. Add support for wp-gpios to the core dw_mmc driver
> since it could be useful across multiple SoCs.
>
> With this change I am able to make use of the write protect f
Certain tty line discipline implementations such slip and bluetooth hci invoke
the serial core uart_write() api in their write_wakeup callback. This leads to
a soft lockup with samsung serial driver since the uart port lock is taken in
the driver's interrupt handler and uart_write() attempts to tak
Since System MMU 3.2 and 3.3 have more prefetch buffers than 2, the
existing function to set prefetch buffers, exynos_sysmmu_set_prefbuf()
is not able to support them.
This commit removes exynos_sysmmu_set_prefbuf() and introduces new
interface, exynos_sysmmu_set_pbuf() that can pass information of
This change enables the client device drivers not to care about
the state of System MMU since the internal state of System MMU
is controlled by the runtime PM and suspend/resume callback functions.
Signed-off-by: KyongHo Cho
---
drivers/iommu/exynos-iommu.c | 175 ++--
System MMUs in some implementation of Exynos core does not include
correct version information in the System MMU. If the version
information is not correct, exynos-iommu driver cannot take advantages
of feature of higher versions of System MMu like prefetching page
table entries prior to TLB miss.
The current exynos-iommu(System MMU) driver does not work autonomously
since it is lack of support for power management of peripheral blocks.
For example, MFC device driver must ensure that its System MMU is disabled
before MFC block is power-down not to invalidate IOTLB in the System MMU
when I/O
On Wed, Nov 21, 2012 at 5:42 PM, Seungwon Jeon wrote:
> Hi,
>
> wp-gpios has been implemented in dw_mmc-exynos.c
> It can be reused for EXYNOS platform? We need to modify some though.
Yup, I've seen that. Patch 1/2 ("mmc: dw_mmc: exynos: Stop claiming
wp-gpio") addressed that. For some reason I
Tomasz Figa wrote:
>
> On Monday 12 of November 2012 09:55:30 Russell King - ARM Linux wrote:
> > On Mon, Nov 12, 2012 at 04:39:28PM +0900, Kukjin Kim wrote:
> > > (+ Russell King)
> >
> > I think there's still an amount of work to do here; it's not a generic
> > interface at the moment because it
Hi Kukjin,
Could you also apply this patch?
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung Poland R&D Center
From: Bartlomiej Zolnierkiewicz
Subject: [PATCH v2] ARM: dts: exynos4: add node for PL330 MDMA1 controller
Add missing PL330 MDMA1 controller node to the device tree (DT).
[ Curr
On Thu, 2012-11-08 at 09:56 +0530, Amit Daniel Kachhap wrote:
> This modification adds 2 new thermal trend type THERMAL_TREND_RAISE_FULL
> and THERMAL_TREND_DROP_FULL. This thermal trend can be used to quickly
> jump to the upper or lower cooling level instead of incremental increase
> or decrease.
Jaehoon,
Thanks for the review. See below for comments. I'll plan on a new
patch either Monday or Tuesday when I have a chance to spin and
re-test.
On Wed, Nov 21, 2012 at 5:55 PM, Jaehoon Chung wrote:
> On 11/22/2012 07:03 AM, Doug Anderson wrote:
>> On some SoCs (like exynos5250) you need t
Alexander Varnin
>
> I also want to point, that irq resource in arch/arm/plat-samsung/devs.c
> for s3c2410-spi driver on S3C2443 points to wrong IRQ (SPI0 instead of
Sounds that you cannot use platform_device in plat-samsung/devs.c for SPI on
S3C2443. Yes, could be...
> SPI1). I've solved it wi
The exynos code claimed wp-gpio with devm_gpio_request() but never did
anything with it. That meant that anyone using a write protect GPIO
would effectively be write protected all the time.
A future change will move the wp-gpio support to the core dw_mmc.c
file. Now the exynos-specific code won'
On some SoCs (like exynos5250) you need to use an external GPIO for
write protect. Add support for wp-gpios to the core dw_mmc driver
since it could be useful across multiple SoCs.
With this change I am able to make use of the write protect for the
external SD slot on exynos5250-snow.
Signed-off
Hi Alexander,
first of all could you elaborate a bit more on the error you experience,
because I currently have problems to understand it from the code alone :-) .
More inline.
Am Donnerstag, 22. November 2012, 14:00:01 schrieb Alexander Varnin:
> S3C2443 CPU has a problem with incorrect readi
The exynos code claimed wp-gpio with devm_gpio_request() but never did
anything with it. That meant that anyone using a write protect GPIO
would effectively be write protected all the time.
A future change will move the wp-gpio support to the core dw_mmc.c
file. Now the exynos-specific code won'
Arnd, Olof,
This is adding support for exynos5440, including Quad ARM Cortex-A15 cores
and its reference board SSDK5440.
Note, at this moment, just enabled minimal system part for initial kernel
boot and pinctrl driver.
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-
Arnd, Olof,
Here is second Samsung DT stuff for v3.8.
This is including power domain DT support for exynos and Google ARM
Chromebook, Snow board and exynos4210-origen updates.
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
next/dt-samsung-2
Note that thi
Hi Arnd, Olof
Here is second Samsung development patches for v3.8.
This includes properly enabling PM support and UART3 DEBUG_LL for exynos5
and CAMIF for s3c24xx/s3c64xx.
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
next/devel-samsung-2
Thanks.
Best
Kukjin Kim wrote:
>
> Hi Arnd, Olof
>
> Here is Samsung fixes for v3.7 and it is for fixing of mdma1 address for
> exynos4210 rev0 SoC.
>
> Please pull from:
> git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> v3.7-samsung-fixes-3
>
Probably, missed?
Thanks.
Best regard
Bartlomiej Zolnierkiewicz wrote:
>
>
> Hi Kukjin,
>
Hi Bart,
> Could you also apply this patch?
>
Yeah, looks good to me :-)
Will apply, thanks.
Best regards,
Kgene.
--
Kukjin Kim , Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
>
>
> From: Bartlomiej Zolnierk
From: Byungho An
This patch adds node for GMAC for exynos5440.
Signed-off-by: Byungho An
Signed-off-by: Kukjin Kim
---
arch/arm/boot/dts/exynos5440.dtsi |9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5440.dtsi
b/arch/arm/boot/dts/exynos5440.dtsi
index
Tomasz Figa wrote:
>
> Exynos4412 uses different information register for each core. This patch
> adjusts the bring-up code to take that into account.
>
> Signed-off-by: Tomasz Figa
> Reviewed-by: Kyungmin Park
> ---
> arch/arm/mach-exynos/platsmp.c | 30 --
> 1 fil
On Mon, Nov 19, 2012 at 7:22 PM, Bill Pemberton wrote:
> CONFIG_HOTPLUG is going away as an option so __devinit is no longer
> needed.
>
> drivers/input/touchscreen/cyttsp_i2c.c | 2 +-
> drivers/input/touchscreen/cyttsp_spi.c | 2 +-
For these two,
Acked-by: Javier Martinez Canilla
On 22 November 2012 13:42, Zhang Rui wrote:
> On Thu, 2012-11-22 at 10:11 +0530, Amit Kachhap wrote:
>> On 22 November 2012 06:52, Zhang Rui wrote:
>> > On Thu, 2012-11-08 at 09:56 +0530, Amit Daniel Kachhap wrote:
>> >> This modification adds 2 new thermal trend type THERMAL_TREND_RAISE_FULL
>>
On Thu, Nov 22, 2012 at 1:41 AM, Tomasz Figa wrote:
> Hi Praveen,
>
> On Wednesday 14 of November 2012 15:57:16 Praveen Paneri wrote:
>> Adding the transceiver to hsotg driver. Keeping the platform data
>> for continuing the smooth operation for boards which still uses it
>>
>> Signed-off-by: Prav
Hi Tomasz,
On Thu, Nov 22, 2012 at 1:36 AM, Tomasz Figa wrote:
> Hi Praveen,
>
> See some minor comments inline.
Thanks for your comments
>
> On Wednesday 14 of November 2012 15:57:15 Praveen Paneri wrote:
>> This driver uses usb_phy interface to interact with s3c-hsotg. Supports
>> phy_init and
On Thu, Nov 22, 2012 at 1:44 AM, Tomasz Figa wrote:
> Hi Praveen,
>
> On Wednesday 14 of November 2012 16:15:36 Praveen Paneri wrote:
>> This patch removes old phy code from platform side. 'setup-usb-phy.c'
>> will be used for providing transceiver platform data in next
>> patch. Not all of the pl
On Thu, Nov 22, 2012 at 5:51 PM, Kukjin Kim wrote:
> Kukjin Kim wrote:
>>
>> Hi Arnd, Olof
>>
>> Here is Samsung fixes for v3.7 and it is for fixing of mdma1 address for
>> exynos4210 rev0 SoC.
>>
>> Please pull from:
>> git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
>> v3.7
On Thu, Nov 22, 2012 at 1:16 AM, Tomasz Figa wrote:
> Hi Praveen,
>
> On Wednesday 14 of November 2012 16:15:38 Praveen Paneri wrote:
>> Adding usbphy node for Exynos4210 along with the platform data.
>>
>> Signed-off-by: Praveen Paneri
>> ---
>> arch/arm/boot/dts/exynos4210-smdkv310.dts |5
Olof Johansson wrote:
[...]
> > Probably, missed?
>
> Yes, thanks for the reminder. By the way, I didn't know you supported
> rev0 silicon?
>
Yeah, only for exynos4210.
Note that there were discussions about that in mailing list and actually
there are many exynos4210 rev0 board for test and d
On Thu, Nov 22, 2012 at 1:54 AM, Tomasz Figa wrote:
> Hi Praveen,
>
> On Wednesday 14 of November 2012 16:15:37 Praveen Paneri wrote:
>> Adding platform device for samsung-usbphy driver. Enabling it for
>> s3c64xx based machines using s3c-hsotg.
>>
>> Signed-off-by: Praveen Paneri
>> ---
>> arch
This patchset cleans up the probe function of i2c-s3c2410 driver.
These have been tested on Exynos4210 based Origen board.
Tushar Behera (7):
i2c: s3c2410: Remove unnecessary label err_noclk
i2c: s3c2410: Convert to use devm_clk_get()
i2c: s3c2410: Convert to use devm_request_mem_region()
err_noclk label redirects to a simple return statement. Move the
return statement to the caller location and remove the label.
Signed-off-by: Tushar Behera
---
drivers/i2c/busses/i2c-s3c2410.c |9 +++--
1 files changed, 3 insertions(+), 6 deletions(-)
diff --git a/drivers/i2c/busses/i2c
Signed-off-by: Tushar Behera
---
drivers/i2c/busses/i2c-s3c2410.c |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/drivers/i2c/busses/i2c-s3c2410.c b/drivers/i2c/busses/i2c-s3c2410.c
index 7522f40..019c3d7 100644
--- a/drivers/i2c/busses/i2c-s3c2410.c
+++ b/drivers/i2c/
Signed-off-by: Tushar Behera
---
drivers/i2c/busses/i2c-s3c2410.c | 12 +++-
1 files changed, 3 insertions(+), 9 deletions(-)
diff --git a/drivers/i2c/busses/i2c-s3c2410.c b/drivers/i2c/busses/i2c-s3c2410.c
index 019c3d7..a274ef7 100644
--- a/drivers/i2c/busses/i2c-s3c2410.c
+++ b/driv
Signed-off-by: Tushar Behera
---
drivers/i2c/busses/i2c-s3c2410.c | 13 -
1 files changed, 4 insertions(+), 9 deletions(-)
diff --git a/drivers/i2c/busses/i2c-s3c2410.c b/drivers/i2c/busses/i2c-s3c2410.c
index a274ef7..3446af2 100644
--- a/drivers/i2c/busses/i2c-s3c2410.c
+++ b/dri
Signed-off-by: Tushar Behera
---
drivers/i2c/busses/i2c-s3c2410.c | 10 +++---
1 files changed, 3 insertions(+), 7 deletions(-)
diff --git a/drivers/i2c/busses/i2c-s3c2410.c b/drivers/i2c/busses/i2c-s3c2410.c
index 3446af2..3e4143c 100644
--- a/drivers/i2c/busses/i2c-s3c2410.c
+++ b/driver
In probe call, only s3c24xx_i2c_init() needs the I2C clock to be enabled.
Moving clk_prepare_enable() and clk_disable_unprepare() calls to around
this function simplifies the return path of probe call.
Signed-off-by: Tushar Behera
---
drivers/i2c/busses/i2c-s3c2410.c | 29 -
err_cpufreq label is now used only once. It can be removed and related
code can be moved to the caller location.
Signed-off-by: Tushar Behera
---
drivers/i2c/busses/i2c-s3c2410.c |7 ++-
1 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/i2c/busses/i2c-s3c2410.c b/dri
Hi Tushar,
On 23 November 2012 11:29, Tushar Behera wrote:
> Signed-off-by: Tushar Behera
> ---
> drivers/i2c/busses/i2c-s3c2410.c | 13 -
> 1 files changed, 4 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-s3c2410.c
> b/drivers/i2c/busses/i2c-s3c2410.c
> i
On Fri, Nov 23, 2012 at 11:29 AM, Tushar Behera
wrote:
> This patchset cleans up the probe function of i2c-s3c2410 driver.
> These have been tested on Exynos4210 based Origen board.
>
> Tushar Behera (7):
> i2c: s3c2410: Remove unnecessary label err_noclk
> i2c: s3c2410: Convert to use devm_cl
On Fri, 2012-11-23 at 09:35 +0530, Amit Kachhap wrote:
> On 22 November 2012 13:42, Zhang Rui wrote:
> > On Thu, 2012-11-22 at 10:11 +0530, Amit Kachhap wrote:
> >> On 22 November 2012 06:52, Zhang Rui wrote:
> >> > On Thu, 2012-11-08 at 09:56 +0530, Amit Daniel Kachhap wrote:
> >> >> This modifi
On 11/23/2012 11:44 AM, Sachin Kamat wrote:
> Hi Tushar,
>
> On 23 November 2012 11:29, Tushar Behera wrote:
>> Signed-off-by: Tushar Behera
>> ---
>> drivers/i2c/busses/i2c-s3c2410.c | 13 -
>> 1 files changed, 4 insertions(+), 9 deletions(-)
>>
>> diff --git a/drivers/i2c/busses
On 11/23/2012 11:45 AM, Shubhrajyoti Datta wrote:
> On Fri, Nov 23, 2012 at 11:29 AM, Tushar Behera
> wrote:
>> This patchset cleans up the probe function of i2c-s3c2410 driver.
>> These have been tested on Exynos4210 based Origen board.
>>
>> Tushar Behera (7):
>> i2c: s3c2410: Remove unnecessa
This patch series includes two minor updates to the gpio dvs code in max8997
regulator driver and adds device tree support for the same driver.
Thomas Abraham (3):
regulator: max8997: reorder buck1/2/5 dvs setup code
regulator: max8997: limit the number of dvs registers programmed in non-dvs
The BUCKxDVSx register programming is now moved prior to setting up of the
gpio based dvs mode. This will ensure that all the BUCKxDVSx registers
are programmed with appropriate voltage values before the gpio based dvs
mode is selected for buck1/2/5.
Cc: MyungJoo Ham
Signed-off-by: Thomas Abraham
In case the gpio based volatage selection mode is not used for either of
buck 1/2/5, then only the BUCKxDVS1 register need to be programmed. So
determine whether dvs mode is used and limit the loop count appropriately.
Cc: MyungJoo Ham
Signed-off-by: Thomas Abraham
---
drivers/regulator/max8997
Add device tree based discovery support for max8997.
Cc: Karol Lewandowski
Cc: Rajendra Nayak
Cc: Rob Herring
Cc: Grant Likely
Signed-off-by: Thomas Abraham
Acked-by: MyungJoo Ham
---
This is the sixth version of this patch. The link to v5 version of this patch
is http://www.mail-archive.com
81 matches
Mail list logo