Commit-ID: bc7c36eedb0c7004aa06c2afc3c5385adada8fa3
Gitweb: http://git.kernel.org/tip/bc7c36eedb0c7004aa06c2afc3c5385adada8fa3
Author: Joonyoung Shim
AuthorDate: Tue, 17 Jan 2017 13:54:36 +0900
Committer: Thomas Gleixner
CommitDate: Tue, 17 Jan 2017 10:08:38 +0100
clocksource
)
[ 51.499057] ---[ end trace 995703fe1bede0b4 ]---
Fixes: 56a94f13919c ("clocksource: exynos_mct: Avoid blocking calls in the cpu
hotplug notifier")
Cc: sta...@vger.kernel.org #v4.2+ #v4.1.4+ #3.18.18+ #v3.16.18+ #v3.12.46+
Reported-by: Seung-Woo Kim
Signed-off-by: Joonyoung Shim
Signed-off
On 11/30/2016 05:05 PM, Viresh Kumar wrote:
> On 30-11-16, 15:19, Joonyoung Shim wrote:
>> Hi Viresh,
>>
>> On 11/30/2016 12:59 PM, Viresh Kumar wrote:
>>> From: Stephen Boyd
>>>
>>> Joonyoung Shim reported an interesting problem on his ARM o
Hi Viresh,
On 11/30/2016 12:59 PM, Viresh Kumar wrote:
> From: Stephen Boyd
>
> Joonyoung Shim reported an interesting problem on his ARM octa-core
> Odoroid-XU3 platform. During system suspend, dev_pm_opp_put_regulator()
> was failing for a struct device for which dev_pm_opp_set
Hi Viresh,
On 11/25/2016 03:57 PM, Viresh Kumar wrote:
> On 25-11-16, 10:54, Joonyoung Shim wrote:
>> I found this problem during system suspend/resume of Odroid-XU3 board.
>>
>> # rtcwake -m mem -s 3
>> wakeup from "mem" at Wed Apr 4 05:54:44 2001
>
On 11/25/2016 03:53 PM, Viresh Kumar wrote:
> Joonyoung Shim reported an interesting problem on his ARM octa-core
> Odoroid-XU3 platform. During system suspend, dev_pm_opp_put_regulator()
> was failing for a struct device for which dev_pm_opp_set_regulator() is
> called earlier.
>
Hi Viresh.
On 11/24/2016 05:34 PM, Viresh Kumar wrote:
> Ho Joonyoung,
>
> On 24-11-16, 16:49, Joonyoung Shim wrote:
>> The device that creates OPP table first should be removed from dev_list
>> of OPP table in last because it can be used by other resources
>> (support
CPU devices.
This patch makes that the CPU device that creates OPP table is removed
last.
Signed-off-by: Joonyoung Shim
---
drivers/base/power/opp/cpu.c | 39 +++
1 file changed, 39 insertions(+)
diff --git a/drivers/base/power/opp/cpu.c b/drivers/base/power
r (div = variant->div_base; div < 4; ++div)
> + if ((rate >> (variant->bits + div)) < freq)
> + break;
> + }
>
Reviewed-by: Joonyoung Shim
Thanks.
ender kernel.
Signed-off-by: Joonyoung Shim
Cc: # v3.16
---
Changelog for v2:
- update commit description and code to fix time keeping problem
- update the stable tag with the kernel version
drivers/rtc/rtc-s5m.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/rtc/rtc-s5m.c b
On 08/21/2015 04:25 PM, Krzysztof Kozlowski wrote:
> On 21.08.2015 15:58, Joonyoung Shim wrote:
>> On 08/21/2015 10:21 AM, Krzysztof Kozlowski wrote:
>>> On 21.08.2015 10:00, Joonyoung Shim wrote:
>>>> On 08/21/2015 09:44 AM, Krzysztof Kozlowski wrote:
>>>&g
On 08/21/2015 10:21 AM, Krzysztof Kozlowski wrote:
> On 21.08.2015 10:00, Joonyoung Shim wrote:
>> On 08/21/2015 09:44 AM, Krzysztof Kozlowski wrote:
>>> On 21.08.2015 08:15, Alexandre Belloni wrote:
>>>> Hi,
>>>>
>>>> On 13/08/2015 at 17:
On 08/21/2015 09:44 AM, Krzysztof Kozlowski wrote:
> On 21.08.2015 08:15, Alexandre Belloni wrote:
>> Hi,
>>
>> On 13/08/2015 at 17:49:24 +0900, Joonyoung Shim wrote :
>>> According to datasheet, the S2MPS13X and S2MPS14X should update write
>>> buffer
On 08/17/2015 11:00 AM, Krzysztof Kozlowski wrote:
> On 17.08.2015 10:47, Joonyoung Shim wrote:
>> Hi,
>>
>> On 08/13/2015 07:02 PM, Krzysztof Kozlowski wrote:
>>> W dniu 13.08.2015 o 17:49, Joonyoung Shim pisze:
>>>> According to datasheet, the
Hi,
On 08/13/2015 07:02 PM, Krzysztof Kozlowski wrote:
> W dniu 13.08.2015 o 17:49, Joonyoung Shim pisze:
>> According to datasheet, the S2MPS13X and S2MPS14X should update write
>> buffer via setting WUDR bit to high after ctrl register is updated.
>
> Hi,
>
> I cann
On 08/13/2015 07:42 PM, Krzysztof Kozlowski wrote:
> W dniu 13.08.2015 o 19:02, Krzysztof Kozlowski pisze:
>> W dniu 13.08.2015 o 17:49, Joonyoung Shim pisze:
>>> According to datasheet, the S2MPS13X and S2MPS14X should update write
>>> buffer via setting WUDR bit to
to 12 hour mode in Odroid-XU3 board.
Signed-off-by: Joonyoung Shim
Cc:
---
drivers/rtc/rtc-s5m.c | 12
1 file changed, 12 insertions(+)
diff --git a/drivers/rtc/rtc-s5m.c b/drivers/rtc/rtc-s5m.c
index 8c70d78..03828bb 100644
--- a/drivers/rtc/rtc-s5m.c
+++ b/drivers/rtc/rtc-s5m.c
@@ -
On 08/12/2015 09:10 AM, Krzysztof Kozlowski wrote:
> On 11.08.2015 20:28, Joonyoung Shim wrote:
>> The driver uses clk_prepare_enable()/clk_disable_unprepare() only in
>> probe only, elsewhere, use the unified functions for enable/disable of
>> clk, e.g. s3c_rtc_enable_clk()
s with 'enabled'
argument having same value, so it needs to check whether clocks are
enabled or not.
Signed-off-by: Joonyoung Shim
Cc: # v4.1
---
This is v2 of prior patch "[PATCH 4/4] rtc: s3c: enable/disable clocks
for alarm".
Changelog for v2:
- commit messages is modifie
On 08/12/2015 09:28 AM, Krzysztof Kozlowski wrote:
> On 11.08.2015 20:28, Joonyoung Shim wrote:
>> The clock enable/disable codes for alarm have removed from
>
> What do you mean in this paragraph? The clock code was removing something?
>
>> 'commit 24e1455493da (&
l times with that
enabled argument has same value, so it needs to check whether clocks is
enabled or not.
Signed-off-by: Joonyoung Shim
---
drivers/rtc/rtc-s3c.c | 24 ++--
1 file changed, 18 insertions(+), 6 deletions(-)
diff --git a/drivers/rtc/rtc-s3c.c b/drivers/rt
It's missed to call clk_unprepare() about info->rtc_src_clk in
s3c_rtc_remove and to call clk_disable_unprepare about info->rtc_clk in
error routine of s3c_rtc_probe.
Signed-off-by: Joonyoung Shim
---
drivers/rtc/rtc-s3c.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/driv
It's unnecessary the code that assigns info->rtc_clk to NULL in
s3c_rtc_remove.
Signed-off-by: Joonyoung Shim
---
drivers/rtc/rtc-s3c.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/rtc/rtc-s3c.c b/drivers/rtc/rtc-s3c.c
index d1866a4..44b2921 100644
--- a/drivers/rtc/r
Hi,
This patchset modifies clock codes of rtc-s3c driver. Main change is to
fix the problem that alarm interrupt can't happen. Also there are some
fixes incluing cleanup.
Thanks.
Joonyoung Shim (4):
rtc: s3c: add missin
The driver uses clk_prepare_enable()/clk_disable_unprepare() only in
probe only, elsewhere, use the unified functions for enable/disable of
clk, e.g. s3c_rtc_enable_clk() / s3c_rtc_disable_clk(), so it's better
to use them for consistency of code.
Signed-off-by: Joonyoung Shim
---
driver
On 07/22/2015 05:22 PM, Inki Dae wrote:
> On 2015년 07월 22일 17:12, Joonyoung Shim wrote:
>> On 07/22/2015 01:55 PM, Inki Dae wrote:
>>> On 2015년 07월 22일 11:02, Joonyoung Shim wrote:
>>>> On 07/21/2015 10:19 PM, Krzysztof Kozlowski wrote:
>>>>> Hi,
On 07/22/2015 01:55 PM, Inki Dae wrote:
> On 2015년 07월 22일 11:02, Joonyoung Shim wrote:
>> On 07/21/2015 10:19 PM, Krzysztof Kozlowski wrote:
>>> Hi,
>>>
>>> Today's linux-next (next-20150721) encounters boot failures on Exynos
>>> Octa (Exynos5422
rst bad commit
> commit d80167b85024982c5f18d0481a5c248100360118
> Author: Joonyoung Shim
> Date: Thu Jul 2 21:49:39 2015 +0900
>
> drm/exynos: remove drm_iommu_attach_device_if_possible
>
> Already drm_iommu_attach_device checks whether support iommu internally.
> It should
* clear interrupts */
> - if (~val & MXR_INT_EN_VSYNC) {
> - /* vsync interrupt use different bit for read and clear */
> - val &= ~MXR_INT_EN_VSYNC;
> - val |= MXR_INT_CLEAR_VSYNC;
> - }
> mixer_reg_write(res, MXR_INT_STAT
ertions(+), 51 deletions(-)
>
Looks good to me except one comment of "drm/exynos/mixer: fix interrupt
clearing" patch. Also below my patch can be dropped by this patchset.
http://www.spinics.net/lists/dri-devel/msg85322.html
Reviewed-by: Joonyoung Shim
--
To unsubscribe from this lis
On 07/09/2015 03:25 PM, Andrzej Hajda wrote:
> The driver used incorrect flags to clear interrupt status.
> The patch fixes it.
>
> Signed-off-by: Andrzej Hajda
> ---
> drivers/gpu/drm/exynos/exynos_mixer.c | 8 +++-
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/drivers
Hi Michael,
On 05/13/2015 08:57 AM, Stephen Boyd wrote:
> On 05/12, Michael Turquette wrote:
>> Quoting Joonyoung Shim (2015-04-07 00:46:46)
>>> The round_rate callback function will returns alway same parent clk rate
>>> of divider with CLK_DIVIDER
Hi Stephen,
On 05/13/2015 08:59 AM, Stephen Boyd wrote:
> On 04/07, Joonyoung Shim wrote:
>> Even if use CLK_DIVIDER_READ_ONLY flag, divider setting can be changed
>> by set_rate callback. Don't change divider setting from set_rate
>> callback of divider with
ate.
Signed-off-by: Joonyoung Shim
---
drivers/clk/clk-divider.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/clk/clk-divider.c b/drivers/clk/clk-divider.c
index ce34d29a..37e285e 100644
--- a/drivers/clk/clk-divider.c
+++ b/drivers/clk/clk-divider.c
@@ -352,6 +352,11 @@ static l
Even if use CLK_DIVIDER_READ_ONLY flag, divider setting can be changed
by set_rate callback. Don't change divider setting from set_rate
callback of divider with CLK_DIVIDER_READ_ONLY flag.
Signed-off-by: Joonyoung Shim
---
drivers/clk/clk-divider.c | 3 +++
1 file changed, 3 insertions(+)
Hi,
On 02/05/2015 11:45 PM, Javier Martinez Canillas wrote:
> Hello Andrzej,
>
> Thanks a lot for finally finding what was causing the HDMI issue.
>
> On 02/05/2015 01:35 PM, Andrzej Hajda wrote:
>> Hi,
>>
>> Exynos chipsets since 542x have asynchronous bridges connecting different
>> IPs.
>> T
exynos_fbd->exynos_gem_obj;
> struct drm_framebuffer *fb;
>
> - if (is_drm_iommu_supported(dev) && exynos_gem_obj->buffer->kvaddr)
> + if (is_drm_iommu_supported(dev))
> vunmap(exynos_gem_obj->buffer->kvaddr);
>
>
Hi Kevin,
On 01/15/2015 10:08 AM, Kevin Hilman wrote:
> From: Kevin Hilman
>
> The odroid-xu3 has 4 INA231 current sensors on board which can be
> accessed from the Linux via the hwmon interface.
>
> There is one sensor for each of these power rails:
>
> - A15 cluster: VDD_ARM
> - A7 cluster:
patch?
>From 6de01473746af225c688ee430123001d57d9af2a Mon Sep 17 00:00:00 2001
From: Joonyoung Shim
Date: Thu, 2 Oct 2014 17:48:27 +0900
Subject: [PATCH] drm/exynos: use drm_vblank_on()
We need to use drm_vblank_on() as a counterpart to drm_vblank_off()
after the commit 7ffd7a68511c ("drm: Always reject
Hi,
On 09/19/2014 08:11 PM, Joonyoung Shim wrote:
> Hi,
>
> On 09/19/2014 07:54 PM, Andrzej Hajda wrote:
>> On 09/19/2014 03:02 AM, Joonyoung Shim wrote:
>>> Hi Andrzej,
>>>
>>> On 09/18/2014 10:17 PM, Andrzej Hajda wrote:
>>>> T
Hi,
On 09/19/2014 07:54 PM, Andrzej Hajda wrote:
> On 09/19/2014 03:02 AM, Joonyoung Shim wrote:
>> Hi Andrzej,
>>
>> On 09/18/2014 10:17 PM, Andrzej Hajda wrote:
>>> The patch replaces legacy functions
>>> drm_plane_init() / drm_crtc_init()
Hi Andrzej,
On 09/18/2014 10:17 PM, Andrzej Hajda wrote:
> The patch replaces legacy functions
> drm_plane_init() / drm_crtc_init() with
> drm_universal_plane_init() and drm_crtc_init_with_planes().
> It allows to replace fake primary plane with the real one.
>
> Signed-off-by: Andrzej Hajda
> -
xynos/exynos_drm_ipp.c | 12 +---
> 1 file changed, 5 insertions(+), 7 deletions(-)
>
About both patch 16 and 17
Reviewed-by: Joonyoung Shim
Thanks.
> diff --git a/drivers/gpu/drm/exynos/exynos_drm_ipp.c
> b/drivers/gpu/drm/exynos/exynos_drm_ipp.c
> index 05f0f4e..9e9714a 100644
>
Hi Andrzej,
On 08/28/2014 06:07 PM, Andrzej Hajda wrote:
> Process should not have access to ipp nodes created by another
> process. The patch adds necessary checks.
>
> Signed-off-by: Andrzej Hajda
> ---
> drivers/gpu/drm/exynos/exynos_drm_ipp.c | 15 ++-
> 1 file changed, 10 inser
Hi Andrzej,
On 08/28/2014 06:07 PM, Andrzej Hajda wrote:
> Since file pointer is preserved in c_node passing it
> as argument in node functions is redundant.
>
> Signed-off-by: Andrzej Hajda
> ---
> drivers/gpu/drm/exynos/exynos_drm_ipp.c | 14 ++
> 1 file changed, 6 insertions(+),
Hi,
On 08/27/2014 07:27 PM, Andrzej Hajda wrote:
> On 08/26/2014 07:00 AM, Joonyoung Shim wrote:
>> Hi Andrzej,
>>
>> On 08/22/2014 04:52 PM, Andrzej Hajda wrote:
>>> In case of allocation errors some already allocated buffers
>>> were not freed. The patch f
> drm/exynos/fimc: fix source buffer registers
With some minor comments,
Reviewed-by: Joonyoung Shim
Thanks.
>
> drivers/gpu/drm/exynos/exynos_drm_fimc.c| 90 ++-
> drivers/gpu/drm/exynos/exynos_drm_gsc.c | 3 +-
> drivers/gpu/drm/exynos/exynos_drm_ipp.c
On 08/26/2014 03:35 PM, Andrzej Hajda wrote:
> On 08/26/2014 07:57 AM, Joonyoung Shim wrote:
>> Hi Andrzej,
>>
>> On 08/22/2014 04:52 PM, Andrzej Hajda wrote:
>>> FIMC in default mode of operation uses only one input buffer,
>>> but the driver used a
Hi Andrzej,
On 08/22/2014 04:52 PM, Andrzej Hajda wrote:
> FIMC in default mode of operation uses only one input buffer,
> but the driver used also second buffer, as a result only the
> first frame was processed correctly. The patch fixes it.
I can't understand well, then we don't need to disting
Hi Andrzej,
On 08/22/2014 04:52 PM, Andrzej Hajda wrote:
> The patch removes redundant checks, redundant HW reads
> and simplifies code.
>
> Signed-off-by: Andrzej Hajda
> ---
> drivers/gpu/drm/exynos/exynos_drm_fimc.c | 64
>
> 1 file changed, 15 insertions(+)
Hi Andrzej,
On 08/22/2014 04:52 PM, Andrzej Hajda wrote:
> In case of allocation errors some already allocated buffers
> were not freed. The patch fixes it.
>
> Signed-off-by: Andrzej Hajda
> ---
> drivers/gpu/drm/exynos/exynos_drm_ipp.c | 68
> -
> 1 file chang
On 08/26/2014 11:55 AM, Joonyoung Shim wrote:
> Hi Andrzej,
>
> On 08/22/2014 04:52 PM, Andrzej Hajda wrote:
>> Command node should contain file reference to distinguish commands
>> created by different processes.
>>
>> Signed-off-by: Andrzej Hajda
Hi Andrzej,
On 08/22/2014 04:52 PM, Andrzej Hajda wrote:
> Command node should contain file reference to distinguish commands
> created by different processes.
>
> Signed-off-by: Andrzej Hajda
> ---
> drivers/gpu/drm/exynos/exynos_drm_ipp.c | 5 ++---
> drivers/gpu/drm/exynos/exynos_drm_ipp.h |
The usb3503 needs to switch to standby mode while suspending and should
switch to hub mode when resumed. Also we can control clock on PM
function.
Signed-off-by: Joonyoung Shim
---
drivers/usb/misc/usb3503.c | 34 --
1 file changed, 32 insertions(+), 2 deletions
3 using exynos-ehci
[9.784601] usb 1-3: device not accepting address 3, error -71
[9.784838] usb usb1-port3: device 1-3 not suspended yet
Signed-off-by: Joonyoung Shim
---
drivers/usb/core/quirks.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/usb/core/quirks.c b/drivers
On 07/10/2014 02:05 PM, Greg Kroah-Hartman wrote:
> On Thu, Jul 10, 2014 at 10:22:46AM +0530, Sachin Kamat wrote:
>> Hi Joonyoung,
>>
>> On Thu, Jul 10, 2014 at 9:53 AM, Joonyoung Shim
>> wrote:
>>> This fixes below build warning.
>>>
>>>
The usb3503 needs to switch to standby mode while suspending and should
switch to hub mode when resumed. Also we can control clock on PM
function.
Signed-off-by: Joonyoung Shim
---
drivers/usb/misc/usb3503.c | 34 --
1 file changed, 32 insertions(+), 2 deletions
ned-off-by: Joonyoung Shim
---
drivers/usb/misc/usb3503.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/misc/usb3503.c b/drivers/usb/misc/usb3503.c
index f43c619..652855b 100644
--- a/drivers/usb/misc/usb3503.c
+++ b/drivers/usb/misc/usb3503.c
@@ -192,7 +192,8 @@
Hello,
This patchset is simple just to fix and support PM for usb3503. They was
tested on odroid U3 board.
Thanks.
Joonyoung Shim (3):
usb: usb3503: fix build warning
usb: usb3503: add PM functions
USB: add reset resume quirk for usb3503
drivers/usb/core/quirks.c | 3
3 using exynos-ehci
[9.784601] usb 1-3: device not accepting address 3, error -71
[9.784838] usb usb1-port3: device 1-3 not suspended yet
Signed-off-by: Joonyoung Shim
---
drivers/usb/core/quirks.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/usb/core/quirks.c b/drivers
may have been dropped
[ 13.480846] smsc95xx 1-2:1.0 eth0: kevent 2 may have been dropped
[ 13.481361] smsc95xx 1-2:1.0 eth0: kevent 2 may have been dropped
...
Signed-off-by: Joonyoung Shim
---
drivers/net/usb/smsc95xx.c | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff
+++--
1 file changed, 21 insertions(+), 15 deletions(-)
Acked-by: Joonyoung Shim
Thanks.
--
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.
On 07/31/2013 08:48 PM, Bartlomiej Zolnierkiewicz wrote:
On Wednesday, July 31, 2013 01:17:46 PM Bartlomiej Zolnierkiewicz wrote:
Hi,
On Wednesday, July 31, 2013 05:50:02 PM Joonyoung Shim wrote:
This reverts commit cea27eb2a202959783f81254c48c250ddd80e129.
Could you please also include
hances memory_hotplug.c to adjust totalhigh_pages when hot-removing
memory, for details please refer to:
http://marc.info/?l=linux-mm&m=136957578620221&w=2
So, if not revert commit cea27eb, currently causes duplicated decreasing
of totalhigh_pages.
Signed-off-by: Joonyoung Shim
Reviewed
to use memory chunk including last address of memory map, e.g.
when starting address is 0xFFF0 and size is 0x10 on 32bit
machine, ending address will be 0x1.
Use correct ending address like starting address + size - 1.
Signed-off-by: Joonyoung Shim
---
lib/genalloc.c | 19
This reverts commit cea27eb2a202959783f81254c48c250ddd80e129.
Fixed to adjust totalhigh_pages when hot-removing memory by commit
3dcc0571cd64816309765b7c7e4691a4cadf2ee7, so that commit occurs
duplicated decreasing of totalhigh_pages.
Signed-off-by: Joonyoung Shim
---
The commit
Hi Benson,
On 03/06/2013 04:41 PM, Benson Leung wrote:
From: Daniel Kurtz
This same driver can be used by atmel based touchscreens and touchpads
(buttonpads) by instantiating the i2c device as a "atmel_mxt_tp".
This will cause the driver to perform some touchpad specific
initializations, such
On 02/06/2013 09:56 AM, Sean Paul wrote:
On Tue, Feb 5, 2013 at 4:42 PM, Stephen Warren wrote:
On 02/05/2013 05:37 PM, Sean Paul wrote:
On Tue, Feb 5, 2013 at 4:22 PM, Stephen Warren wrote:
n 02/05/2013 04:42 PM, Sean Paul wrote:
Use the compatible string in the device tree to determine whi
Check whether host->sdio_irq_thread is NULL before wake_up_process() is
called about host->sdio_irq_thread.
Signed-off-by: Joonyoung Shim
---
Currently the kernel panic to refer NULL pointer about
host->sdio_irq_thread are occuring at the trats board using Samsung
SDHCI driver.
incl
Hi Grant,
On 12/20/2012 07:22 AM, Grant Likely wrote:
On Fri, 14 Dec 2012 19:44:01 +0900, Joonyoung Shim
wrote:
The exynos_gpio_cfg can be substituted to samsung_gpio_cfgs[8].
Signed-off-by: Joonyoung Shim
Hi Joonyoung,
I need some help here. I don't understand what this patch is f
ialized to &samsung_gpio_cfgs[8] in declaration ahead.
Signed-off-by: Joonyoung Shim
---
drivers/gpio/gpio-samsung.c | 25 +
1 file changed, 25 insertions(+)
diff --git a/drivers/gpio/gpio-samsung.c b/drivers/gpio/gpio-samsung.c
index e30cd60..a462f2c 100644
--- a/dri
The exynos_gpio_cfg can be substituted to samsung_gpio_cfgs[8].
Signed-off-by: Joonyoung Shim
---
drivers/gpio/gpio-samsung.c | 25 -
1 file changed, 8 insertions(+), 17 deletions(-)
diff --git a/drivers/gpio/gpio-samsung.c b/drivers/gpio/gpio-samsung.c
index 6f93d36
On 12/14/2012 04:34 PM, Thierry Reding wrote:
On Fri, Dec 14, 2012 at 03:58:58PM +0900, Joonyoung Shim wrote:
The s3c->pwm_id is used to calculate offset of related register.
Signed-off-by: Joonyoung Shim
I've modified the subject a bit to make it clear the assignment of
s3c->
The s3c->pwm_id is used to calculate offset of related register.
Signed-off-by: Joonyoung Shim
---
Changelog from v1:
- move the assignment code to below.
drivers/pwm/pwm-samsung.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/pwm/pwm-samsung.c b/drivers/pwm/pwm-samsun
The s3c->pwm_id is used to calculate offset of related register.
Signed-off-by: Joonyoung Shim
---
drivers/pwm/pwm-samsung.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/pwm/pwm-samsung.c b/drivers/pwm/pwm-samsung.c
index 023a3be..b415102 100644
--- a/drivers/pwm/
e and can't
make to module.
Signed-off-by: Joonyoung Shim
---
This is based on for-next branch of git://gitorious.org/linux-pwm/linux-pwm.git
drivers/pwm/Kconfig |9 ++
drivers/pwm/Makefile |1 +
drivers/pwm/pwm-exynos.c | 234 +
On 08/29/2012 02:16 AM, Mark Brown wrote:
On Tue, Aug 28, 2012 at 08:25:30PM +0900, Joonyoung Shim wrote:
Consumer nodes can reference regulators using -supply from dts
file with this patch.
Signed-off-by: Joonyoung Shim
Signed-off-by: Kyungmin Park
This doesn't apply against current
Consumer nodes can reference regulators using -supply from dts
file with this patch.
Signed-off-by: Joonyoung Shim
Signed-off-by: Kyungmin Park
---
drivers/regulator/max77686.c |2 ++
include/linux/mfd/max77686.h |1 +
2 files changed, 3 insertions(+)
diff --git a/drivers/regulator
0_subdev_info *subdevs;
}
This is platform data struct for tps65090 mfd driver, but num_subdevs
and subdevs are not used in the mfd driver. How do you handle platform
data of tps65090 mfd driver and regulator driver?
Thanks.
>
> Thanks,
> Venu
>
>
>> -Original Message
},
};
...
I know tps65090 and tps65910 have each different regulator driver.
drivers/regulator/tps65090-regulator.c
drivers/regulator/tps65910-regulator.c
So, i wonder whether it is right that tps65090 mfd driver has tps65910-xxx.
Thanks.
--
- Joonyoung Shim
--
To unsubscribe from this
80 matches
Mail list logo
