support at sysfs node.
Acked-by: Kyungmin Park <kyungmin.p...@samsung.com>
>>
>> Signed-off-by: Jin Qian <jinq...@android.com>
>> ---
>> drivers/mmc/core/mmc.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/mmc/cor
On Thu, Mar 23, 2017 at 6:03 PM, Ulf Hansson wrote:
> On 23 March 2017 at 01:18, Jin Qian wrote:
>> Extend sysfs to access ext_csd revision information.
it can be used secure erase feature for each revision. so it's helpful
to support at sysfs node.
Acked-by: Kyungmin Park
>>
> should be scanned.
Here's old discussion to support app-per-memcg reclaim
"[PATCH] memcg: Add force_reclaim to reclaim tasks' memory in memcg."
http://www.spinics.net/lists/cgroups/msg07874.html
unlike existing interface, it can reclaim the memory while process is
still in memcg.
In
discussion to support app-per-memcg reclaim
"[PATCH] memcg: Add force_reclaim to reclaim tasks' memory in memcg."
http://www.spinics.net/lists/cgroups/msg07874.html
unlike existing interface, it can reclaim the memory while process is
still in memcg.
In our case, it's used for reclaim a
On Tue, May 12, 2015 at 11:43 PM, Tejun Heo wrote:
> Hello,
>
> On Mon, May 11, 2015 at 04:47:14PM +0900, Kyungmin Park wrote:
>> > The kernel 3.10 is not working as expected, but right the latest
>> > kernel is working correctly.
>>
>> Please ignore it.
On Tue, May 12, 2015 at 11:43 PM, Tejun Heo t...@kernel.org wrote:
Hello,
On Mon, May 11, 2015 at 04:47:14PM +0900, Kyungmin Park wrote:
The kernel 3.10 is not working as expected, but right the latest
kernel is working correctly.
Please ignore it. test is wrong and it's not working, see
On Mon, May 11, 2015 at 1:28 PM, Kyungmin Park wrote:
> On Sat, May 9, 2015 at 12:25 AM, Tejun Heo wrote:
>> Hello, Kyungmin.
>>
>> On Fri, May 08, 2015 at 09:04:26AM +0900, Kyungmin Park wrote:
>>> > I need to think more about it but as an *optimization* we can
On Mon, May 11, 2015 at 1:28 PM, Kyungmin Park kmp...@infradead.org wrote:
On Sat, May 9, 2015 at 12:25 AM, Tejun Heo t...@kernel.org wrote:
Hello, Kyungmin.
On Fri, May 08, 2015 at 09:04:26AM +0900, Kyungmin Park wrote:
I need to think more about it but as an *optimization* we can add
On Sat, May 9, 2015 at 12:25 AM, Tejun Heo wrote:
> Hello, Kyungmin.
>
> On Fri, May 08, 2015 at 09:04:26AM +0900, Kyungmin Park wrote:
>> > I need to think more about it but as an *optimization* we can add
>> > freezing() test before actually waking tasks up duri
On Sat, May 9, 2015 at 12:25 AM, Tejun Heo t...@kernel.org wrote:
Hello, Kyungmin.
On Fri, May 08, 2015 at 09:04:26AM +0900, Kyungmin Park wrote:
I need to think more about it but as an *optimization* we can add
freezing() test before actually waking tasks up during resume, but can
you
On Fri, May 8, 2015 at 12:42 AM, Tejun Heo wrote:
> Hello,
>
> On Thu, May 07, 2015 at 03:45:57PM +0900, Kyungmin Park wrote:
>> From: Kyungmin Park
>>
>> Some platform uses freezer cgroup for speicial purpose to schedule out some
>> applications. but after
From: Kyungmin Park
Some platform uses freezer cgroup for speicial purpose to schedule out some
applications. but after suspend & resume, these processes are thawed and
running.
but it's inteneded and don't need to thaw it.
To avoid it, does it possible to modify resume code and don't
From: Kyungmin Park kyungmin.p...@samsung.com
Some platform uses freezer cgroup for speicial purpose to schedule out some
applications. but after suspend resume, these processes are thawed and
running.
but it's inteneded and don't need to thaw it.
To avoid it, does it possible to modify
On Fri, May 8, 2015 at 12:42 AM, Tejun Heo t...@kernel.org wrote:
Hello,
On Thu, May 07, 2015 at 03:45:57PM +0900, Kyungmin Park wrote:
From: Kyungmin Park kyungmin.p...@samsung.com
Some platform uses freezer cgroup for speicial purpose to schedule out some
applications. but after suspend
On Tue, Mar 10, 2015 at 11:22 PM, Jan Kara wrote:
> On Tue 10-03-15 06:03:23, Christoph Hellwig wrote:
>> On Tue, Mar 10, 2015 at 10:51:41AM +0900, Kyungmin Park wrote:
>> > Any updates?
>>
>> Please just add disk quota support to tmpfs so thast the standard quot
On Tue, Mar 10, 2015 at 11:22 PM, Jan Kara j...@suse.cz wrote:
On Tue 10-03-15 06:03:23, Christoph Hellwig wrote:
On Tue, Mar 10, 2015 at 10:51:41AM +0900, Kyungmin Park wrote:
Any updates?
Please just add disk quota support to tmpfs so thast the standard quota
netlink notifications can
Any updates?
Thank you,
Kyungmin Park
On Wed, Feb 11, 2015 at 11:50 PM, Krzysztof Kozlowski
wrote:
> Allow notifying user space when used space of tmpfs exceeds specified
> level.
>
> The utilization level is passed as mount option 'warn_used'. The kernel
> will notify use
Any updates?
Thank you,
Kyungmin Park
On Wed, Feb 11, 2015 at 11:50 PM, Krzysztof Kozlowski
k.kozlow...@samsung.com wrote:
Allow notifying user space when used space of tmpfs exceeds specified
level.
The utilization level is passed as mount option 'warn_used'. The kernel
will notify user
om OOM killer, so that the frozen process will recover itself
> and then be killed finally.
Similar patch is posted and discussed but no conclusion.
http://marc.info/?t=13769976944=1=1
Adding Bart,
Thank you,
Kyungmin Park
>
> Cc: David Rientjes
> Cc: Michal Hocko
> Cc: "Rafae
itself
and then be killed finally.
Similar patch is posted and discussed but no conclusion.
http://marc.info/?t=13769976944r=1w=1
Adding Bart,
Thank you,
Kyungmin Park
Cc: David Rientjes rient...@google.com
Cc: Michal Hocko mho...@suse.cz
Cc: Rafael J. Wysocki r...@rjwysocki.net
Cc
that sb buffer isn't movable?
>> We
>> seem to be locking the buffers before moving the underlying page but we
>> don't do any reference or state checks on the buffers... That seems to be
>> assuming that noone looks at bh->b_data without holding buffer lock. That
>> is
at bh-b_data without holding buffer lock. That
is likely true for ordinary data but definitely not true for metadata
buffers (i.e., buffers for pages from block device mappings).
we got similar issues and add similar work-around codes.
Thank you,
Kyungmin Park
The sb buffer is not movable
On Sat, Mar 15, 2014 at 2:35 AM, Tomasz Figa wrote:
> Hi Chanwoo, Mark,
>
>
> On 14.03.2014 11:56, Chanwoo Choi wrote:
>>
>> Hi Mark,
>>
>> On 03/14/2014 07:35 PM, Mark Rutland wrote:
>>>
>>> On Fri, Mar 14, 2014 at 07:14:37AM +, Chanwoo Choi wrote:
Hi Mark,
On 03/14/2014
On Sat, Mar 15, 2014 at 2:35 AM, Tomasz Figa t.f...@samsung.com wrote:
Hi Chanwoo, Mark,
On 14.03.2014 11:56, Chanwoo Choi wrote:
Hi Mark,
On 03/14/2014 07:35 PM, Mark Rutland wrote:
On Fri, Mar 14, 2014 at 07:14:37AM +, Chanwoo Choi wrote:
Hi Mark,
On 03/14/2014 02:53 AM, Mark
ge Bits parameter, used as
> + scaling parameter in Custom Model algorithm;
> + - maxim,model_data: ModelGauge ModelData data,
> + Custom Model calibration data.
Dose it open to vendor? we're using this
it at all. most of property except rcomp doesn't used.
Thank you,
Kyungmin Park
+
+Example:
+
+modelgauge@36 {
+ compatible = maxim,max17058;
+ reg = 0x36;
+ interrupt-parent = msmgpio;
+ interrupts = 107 0x2;
+
+ maxim,empty_alert_threshold = /bits/ 8 15
On Mon, Jan 6, 2014 at 7:46 PM, Lee Jones wrote:
>> Add document describing device tree bindings for MAX14577 MFD driver.
>>
>> Signed-off-by: Krzysztof Kozlowski
>> Signed-off-by: Kyungmin Park
>> ---
>> Documentation/devicetree/bindings/mfd/max14577.txt |
On Mon, Jan 6, 2014 at 7:46 PM, Lee Jones lee.jo...@linaro.org wrote:
Add document describing device tree bindings for MAX14577 MFD driver.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
Documentation/devicetree/bindings
> -Original Message-
> From: Peter Zijlstra [mailto:pet...@infradead.org]
> Sent: Thursday, December 12, 2013 8:35 PM
> To: Andrzej Pietrasiewicz
> Cc: linux-kernel@vger.kernel.org; Kyungmin Park; Marek Szyprowski; Ingo
> Molnar
> Subject: Re: [PATCH v2] kernel/loc
-Original Message-
From: Peter Zijlstra [mailto:pet...@infradead.org]
Sent: Thursday, December 12, 2013 8:35 PM
To: Andrzej Pietrasiewicz
Cc: linux-kernel@vger.kernel.org; Kyungmin Park; Marek Szyprowski; Ingo
Molnar
Subject: Re: [PATCH v2] kernel/locking: mutex: simplify access
If we set the pinmux up as "output" then there's a chance that the
>> line will glitch at bootup since the pinmux happens (changing the pin
>> to output) before the driver has a chance to run.
>
> I think that last point should be addressed by having a driver that o
of
Some pins are not connected (NC). At that cases, there's no drivers to
handle it. To reduce power leakage, it sets proper configuration with
values instead of reset values.
Thank you,
Kyungmin Park
the SoC's GPIO driver communicate with the pinctrl driver (which might
be the same driver
t; *dev)
>> +{
>
> There's no DT binding document?
>
>> +const struct dev_pm_ops max14577_pm = {
>> + .suspend = max14577_suspend,
>> + .resume = max14577_resume,
>> +};
>
> SET_SYSTEM_SLEEP_PM_OPS().
>
>> +static int __init max145
d most of the time, disabling the overvoltage protection all the time
> seems like an uncertain tradeoff.
It's hard to do at runtime. right it's rare case. but some condition
(as above) is meet, and no code as workaround. it's mal-function.
that's the guide to avoid this mal-functions.
Thank you
the overvoltage protection all the time
seems like an uncertain tradeoff.
It's hard to do at runtime. right it's rare case. but some condition
(as above) is meet, and no code as workaround. it's mal-function.
that's the guide to avoid this mal-functions.
Thank you,
Kyungmin Park
--
To unsubscribe from
(max14577_i2c_driver);
+}
+subsys_initcall(max14577_i2c_init);
Why not module_i2c_driver?
there's ordering issue, it should provide regulator which is used
others before USB probe. if not, it failed to use USB.
Other PMICs use also subsys_initcall for this reason.
Thank you,
Kyungmin Park
From: Kyungmin Park
The most mobile phones have Ambient Light Sensors and it changes brightness
according lux.
It means it changes backlight brightness frequently by just writing sysfs node,
so it generates uevent.
Usually there's no user to use this backlight changes. But it forks udev
On Tue, Nov 12, 2013 at 10:19 AM, Kay Sievers wrote:
> On Tue, Nov 12, 2013 at 1:56 AM, Henrique de Moraes Holschuh
> wrote:
>> On Tue, 12 Nov 2013, Jingoo Han wrote:
>>> On Tuesday, November 12, 2013 8:57 AM, Kyungmin Park wrote:
>>> > From: Kyungmin Park
&
On Tue, Nov 12, 2013 at 9:56 AM, Henrique de Moraes Holschuh
wrote:
> On Tue, 12 Nov 2013, Jingoo Han wrote:
>> On Tuesday, November 12, 2013 8:57 AM, Kyungmin Park wrote:
>> > From: Kyungmin Park
>> >
>> > The most mobile phones have Ambient Light Sen
Please ignore it. strange mail system.
After feedback from previous mail, I'll re-send it.
Thank you,
Kyungmin Park
On Tue, Nov 12, 2013 at 9:44 AM, Kyungmin Park wrote:
> From: Kyungmin Park
>
> The most mobile phones have Ambient Light Sensors and it changes brightness
> a
From: Kyungmin Park
The most mobile phones have Ambient Light Sensors and it changes brightness
according lux.
It means it changes backlight brightness frequently by just writing sysfs node,
so it generates uevent.
Usually there's no user to use this backlight changes. But it forks udev
From: Kyungmin Park
The most mobile phones have Ambient Light Sensors and it changes brightness
according lux.
It means it changes backlight brightness frequently by just writing sysfs node,
so it generates uevent.
Usually there's no user to use this backlight changes. But it forks udev
From: Kyungmin Park kyungmin.p...@samsung.com
The most mobile phones have Ambient Light Sensors and it changes brightness
according lux.
It means it changes backlight brightness frequently by just writing sysfs node,
so it generates uevent.
Usually there's no user to use this backlight
From: Kyungmin Park kyungmin.p...@samsung.com
The most mobile phones have Ambient Light Sensors and it changes brightness
according lux.
It means it changes backlight brightness frequently by just writing sysfs node,
so it generates uevent.
Usually there's no user to use this backlight
Please ignore it. strange mail system.
After feedback from previous mail, I'll re-send it.
Thank you,
Kyungmin Park
On Tue, Nov 12, 2013 at 9:44 AM, Kyungmin Park kmp...@infradead.org wrote:
From: Kyungmin Park kyungmin.p...@samsung.com
The most mobile phones have Ambient Light Sensors
On Tue, Nov 12, 2013 at 9:56 AM, Henrique de Moraes Holschuh
h...@hmh.eng.br wrote:
On Tue, 12 Nov 2013, Jingoo Han wrote:
On Tuesday, November 12, 2013 8:57 AM, Kyungmin Park wrote:
From: Kyungmin Park kyungmin.p...@samsung.com
The most mobile phones have Ambient Light Sensors
On Tue, Nov 12, 2013 at 10:19 AM, Kay Sievers k...@vrfy.org wrote:
On Tue, Nov 12, 2013 at 1:56 AM, Henrique de Moraes Holschuh
h...@hmh.eng.br wrote:
On Tue, 12 Nov 2013, Jingoo Han wrote:
On Tuesday, November 12, 2013 8:57 AM, Kyungmin Park wrote:
From: Kyungmin Park kyungmin.p
From: Kyungmin Park kyungmin.p...@samsung.com
The most mobile phones have Ambient Light Sensors and it changes brightness
according lux.
It means it changes backlight brightness frequently by just writing sysfs node,
so it generates uevent.
Usually there's no user to use this backlight
On Tue, Nov 5, 2013 at 5:04 PM, Tushar Behera wrote:
> On 5 November 2013 13:27, Kyungmin Park wrote:
>> On Tue, Nov 5, 2013 at 3:29 PM, Tushar Behera
>> wrote:
>>> On 31 October 2013 21:46, Lee Jones wrote:
>>>> On Thu, 31 Oct 2013, Tushar Behera wrote:
&
On Tue, Nov 5, 2013 at 5:04 PM, Tushar Behera tushar.beh...@linaro.org wrote:
On 5 November 2013 13:27, Kyungmin Park kmp...@infradead.org wrote:
On Tue, Nov 5, 2013 at 3:29 PM, Tushar Behera tushar.beh...@linaro.org
wrote:
On 31 October 2013 21:46, Lee Jones lee.jo...@linaro.org wrote
.name = "s5m-rtc",
>>> - },
>>> + }, {
>>> + .name = "s5m8767-clk",
Do you want to handle these as "clock"? previous time, it's
implemented at regulator. please see drivers/regulator/max* series.
Thank you,
Kyungmin P
at regulator. please see drivers/regulator/max* series.
Thank you,
Kyungmin Park
+ }
};
static struct mfd_cell s2mps11_devs[] = {
Acked-by: Lee Jones lee.jo...@linaro.org
Thanks.
I'd prefer to take this patch in via the MFD tree once you have
support from the other maintainers
ery wasteful.
>
> This patch modifes the code such that, i2c bus registers to
> cpu_freq_transition only if CONFIG_CPU_FREQ_S3C24XX is enabled.
>
> This change should save a bunch of cpufreq transitions calls
> which does not apply to exynos SoCs.
>
> Signed-off-by: Naveen K
...@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
Changes since v1:
Use CONFIG_CPU_FREQ_S3C24XX instead of (CONFIG_CPU_FREQ !CONFIG_EXYNOS)
As commented by Tomasz
drivers/i2c/busses/i2c-s3c2410.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers
f it's running off
>> a userland task except from well-defined spots.
>
> Which might be worth doing anyway to be sure we know what's going on.
>
>> Anyways, we need to ensure that userland task doesn't get stuck deep in the
>> kernel before allowing this.
>
> Agr
to kill frozen app easily.
Don't need to thaw app to kill.
Thank you,
Kyungmin Park
--
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
proto = -EINVAL;
> @@ -3181,7 +3179,7 @@ static int smack_socket_sock_rcv_skb(struct sock *sk,
> struct sk_buff *skb)
> struct netlbl_lsm_secattr secattr;
> struct socket_smack *ssp = sk->sk_security;
> struct smack_known *skp;
> - struct sockaddr sa
)
struct netlbl_lsm_secattr secattr;
struct socket_smack *ssp = sk-sk_security;
struct smack_known *skp;
- struct sockaddr sadd;
+ struct sockaddr_in6 sadd;
'sadd' is used for struct sockaddr_in6.
Thank you,
Kyungmin Park
int rc = 0;
struct
On Mon, Jul 22, 2013 at 9:15 AM, Joe Perches wrote:
> ommit ca9143501c30 ("ARM: EXYNOS: Remove unused board files")
> removed the files, remove the patterns too.
>
> Signed-off-by: Joe Perches
> cc: Tomasz Figa
> cc: Kyungmin Park
Acked-by: Kyungmin Park
> cc: K
On Mon, Jul 22, 2013 at 9:15 AM, Joe Perches j...@perches.com wrote:
ommit ca9143501c30 (ARM: EXYNOS: Remove unused board files)
removed the files, remove the patterns too.
Signed-off-by: Joe Perches j...@perches.com
cc: Tomasz Figa t.f...@samsung.com
cc: Kyungmin Park kyungmin.p
+ cpufreq maintainers
On Fri, Jul 5, 2013 at 12:17 AM, Konstantin Krivyakin
wrote:
> Signed-off-by: Konstantin Krivyakin
> ---
> drivers/cpufreq/exynos-cpufreq.c |2 ++
> drivers/cpufreq/exynos-cpufreq.h |1 +
> drivers/cpufreq/exynos4x12-cpufreq.c | 19 ++-
>
+ scheduler maintainers
On Fri, Jul 5, 2013 at 12:17 AM, Konstantin Krivyakin
wrote:
> Signed-off-by: Konstantin Krivyakin
> ---
> include/linux/sched.h |2 ++
> include/uapi/linux/taskstats.h |2 ++
> kernel/fork.c |1 +
> kernel/sched/core.c|
+ cpufreq maintainers
On Fri, Jul 5, 2013 at 12:17 AM, Konstantin Krivyakin
wrote:
> Signed-off-by: Konstantin Krivyakin
> ---
> drivers/cpufreq/cpufreq.c | 17 +
> include/linux/cpufreq.h |6 ++
> 2 files changed, 23 insertions(+)
>
> diff --git
Hi Krivyakin,
Please use "./scripts/get_maintainer.pl" and send proper maintainers.
I added them.
Thank you,
Kyungmin Park
On Fri, Jul 5, 2013 at 12:17 AM, Konstantin Krivyakin
wrote:
> This patchset adds per-process power consumption measurement facility.
> Power con
Hi Krivyakin,
Please use ./scripts/get_maintainer.pl and send proper maintainers.
I added them.
Thank you,
Kyungmin Park
On Fri, Jul 5, 2013 at 12:17 AM, Konstantin Krivyakin
k.krivya...@samsung.com wrote:
This patchset adds per-process power consumption measurement facility.
Power
+ cpufreq maintainers
On Fri, Jul 5, 2013 at 12:17 AM, Konstantin Krivyakin
k.krivya...@samsung.com wrote:
Signed-off-by: Konstantin Krivyakin k.krivya...@samsung.com
---
drivers/cpufreq/cpufreq.c | 17 +
include/linux/cpufreq.h |6 ++
2 files changed, 23
+ scheduler maintainers
On Fri, Jul 5, 2013 at 12:17 AM, Konstantin Krivyakin
k.krivya...@samsung.com wrote:
Signed-off-by: Konstantin Krivyakin k.krivya...@samsung.com
---
include/linux/sched.h |2 ++
include/uapi/linux/taskstats.h |2 ++
kernel/fork.c |
+ cpufreq maintainers
On Fri, Jul 5, 2013 at 12:17 AM, Konstantin Krivyakin
k.krivya...@samsung.com wrote:
Signed-off-by: Konstantin Krivyakin k.krivya...@samsung.com
---
drivers/cpufreq/exynos-cpufreq.c |2 ++
drivers/cpufreq/exynos-cpufreq.h |1 +
+ Ms. Kim,
she already raised this issue at another mail thread.
Thank you,
Kyungmin Park
On Wed, Jun 26, 2013 at 6:51 AM, Luiz Capitulino wrote:
> Currently, applications are notified for the level they registered for
> _plus_ higher levels.
>
> This is a problem if the appli
+ Ms. Kim,
she already raised this issue at another mail thread.
Thank you,
Kyungmin Park
On Wed, Jun 26, 2013 at 6:51 AM, Luiz Capitulino lcapitul...@redhat.com wrote:
Currently, applications are notified for the level they registered for
_plus_ higher levels.
This is a problem
madvise and only
allow this feature at linux only?
As you know it's just hint and it doesn't break existing memory behaviors.
>
> Any comments as I start implementing it? Is there any reason to allow
> naming a file-backed mapping and showing it alongside the file name in
> /proc/pid/m
.
Any comments as I start implementing it? Is there any reason to allow
naming a file-backed mapping and showing it alongside the file name in
/proc/pid/maps?
Thank you,
Kyungmin Park
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord
On Mon, Jun 17, 2013 at 7:17 AM, Doug Anderson wrote:
> It's convenient if get_maintainer suggests sending samsung/exynos
> pinctrl changes to linux-samsung-soc and to Tomasz and Thomas.
>
> Signed-off-by: Doug Anderson
Acked-by: Kyungmin Park
> ---
> Changes in v2:
>
On Mon, Jun 17, 2013 at 7:17 AM, Doug Anderson diand...@chromium.org wrote:
It's convenient if get_maintainer suggests sending samsung/exynos
pinctrl changes to linux-samsung-soc and to Tomasz and Thomas.
Signed-off-by: Doug Anderson diand...@chromium.org
Acked-by: Kyungmin Park kyungmin.p
aging/android/lowmemorykiller.c:lowmem_shrink() does do this,
> and it looks like the function will be pretty quick in this case.
>
> In other words, the behaviour of lowmem_shrink(nr_to_scan == 0) does
> not match Heesub's description. What's up with that?
>
Right, bu
. What's up with that?
Right, but real use case is differnet at mainline kernel. and he found it.
there are two approaches,
1. Reduce do_shinker_slab call by this patch
2. Optimize shinker function itself as like this.
Thank you,
Kyungmin Park
Also, there is an obvious optimisation which we could
igned-off-by: Arnd Bergmann
> Cc: linux-...@lists.infradead.org
> Cc: Kyungmin Park
Acked-by: Kyungmin Park
> Cc: David Woodhouse
> ---
> drivers/mtd/onenand/samsung.c | 4
> ++--
> .../include/plat/regs-onenand.h => drivers/mtd/onenan
header file explicitly.
It's really wanted feature.
>
> Signed-off-by: Arnd Bergmann
Acked-by: Kyungmin Park
> ---
> arch/arm/mach-exynos/dev-uart.c | 1 +
> arch/arm/mach-exynos/include/mach/irqs.h | 5 -
> arch/arm/mach-exynos/mach-armlex4210.c | 2 ++
> arch/arm/ma
explicitly.
It's really wanted feature.
Signed-off-by: Arnd Bergmann a...@arndb.de
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
arch/arm/mach-exynos/dev-uart.c | 1 +
arch/arm/mach-exynos/include/mach/irqs.h | 5 -
arch/arm/mach-exynos/mach-armlex4210.c | 2 ++
arch
-by: Arnd Bergmann a...@arndb.de
Cc: linux-...@lists.infradead.org
Cc: Kyungmin Park kyungmin.p...@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
Cc: David Woodhouse dw...@infradead.org
---
drivers/mtd/onenand/samsung.c | 4
++--
.../include
y is different characteristics.
and if new type is added, it doesn't need to modify lots of codes.
Do you have any data for it? do you get meaningful performance gain or
efficiency of z* family? If yes, please share it.
Thank you,
Kyungmin Park
>
> Other problem is zram is block device so
.
and if new type is added, it doesn't need to modify lots of codes.
Do you have any data for it? do you get meaningful performance gain or
efficiency of z* family? If yes, please share it.
Thank you,
Kyungmin Park
Other problem is zram is block device so that it can set SWP_INMEMORY
or SWP_SOLIDSTATE
power when usb is connected only.
In our case, micro IC detects the usb connection and enable usb power
at that time.
Thank you,
Kyungmin Park
>
> Signed-off-by: Tushar Behera
> ---
>
> Based on v3.8.
>
> arch/arm/mach-exynos/mach-origen.c |2 ++
> 1 files changed, 2 inser
when usb is connected only.
In our case, micro IC detects the usb connection and enable usb power
at that time.
Thank you,
Kyungmin Park
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
---
Based on v3.8.
arch/arm/mach-exynos/mach-origen.c |2 ++
1 files changed, 2 insertions
o use lowmem, so just CMA can support highmem and no need to adjust
address used at reserved memory.
> CMA is for dma buffer, correct? Then how can old dma device access highmem?
What's the "old dma device"? To support it, we also modify
arch/arm/mm/dma-mapping.c for handl
#ifdef/endif. we don't know hisotrical reason.
Thank you,
Kyungmin Park
+if (PageHighMem(page))
+totalhigh_pages += pageblock_nr_pages;
+#endif
}
#endif
Best regards
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majord...@kvack.org
er uses 4210 and
>> 4212 to differentiate between different register addresses and
>> features, but most things are just exynos4-hdmi compatible.
I would like to distinguish between 4210 and 4x12. since it has
different features. e.g., HDMI v1.3 and v1.4.
and I also want to use
like to distinguish between 4210 and 4x12. since it has
different features. e.g., HDMI v1.3 and v1.4.
and I also want to use 4412 instead of 4212. there's no board to use
4212 at mainline until this time.
Thank you,
Kyungmin Park
The DT nodes should include only the compatible values that the HW
Hi,
Can split patch into two parts?
One for USB tree, another for samsung tree.
Thank you,
Kyungmin Park
On Tue, Feb 5, 2013 at 9:37 AM, Dongjin Kim wrote:
> This patch adds host phy support for Samsung's Exynos4412 SoC to
> samsung-usbphy driver and its device node.
>
> Cc: Pr
Hi,
On Tue, Feb 5, 2013 at 8:43 AM, Minchan Kim wrote:
> Hello,
>
> On Tue, Feb 05, 2013 at 08:29:26AM +0900, Kyungmin Park wrote:
>> On Tue, Feb 5, 2013 at 8:06 AM, Andrew Morton
>> wrote:
>> > On Mon, 04 Feb 2013 11:27:05 +0100
>> > Marek Szyprowski wr
t; eclk:
> kfree(i2c);
> emalloc:
> - release_mem_region(res->start, resource_size(res));
> + if (!res)
if (res)?
It's not match with description. and it seems wrong.
Thank you,
Kyungmin Park
> + release_mem_region(res->start, r
is needed so that others can make patch-scheduling
> decisions and should be included in all bugfix changelogs unless it is
> obvious).
CMA Highmem support is new feature. so don't need to go stable tree.
Thank you,
Kyungmin Park
>
> --
> To unsubscribe, send a message with 'unsubscribe lin
so that others can make patch-scheduling
decisions and should be included in all bugfix changelogs unless it is
obvious).
CMA Highmem support is new feature. so don't need to go stable tree.
Thank you,
Kyungmin Park
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body
);
emalloc:
- release_mem_region(res-start, resource_size(res));
+ if (!res)
if (res)?
It's not match with description. and it seems wrong.
Thank you,
Kyungmin Park
+ release_mem_region(res-start, resource_size(res));
return ret;
}
--
1.7.9.5
Hi,
On Tue, Feb 5, 2013 at 8:43 AM, Minchan Kim minc...@kernel.org wrote:
Hello,
On Tue, Feb 05, 2013 at 08:29:26AM +0900, Kyungmin Park wrote:
On Tue, Feb 5, 2013 at 8:06 AM, Andrew Morton a...@linux-foundation.org
wrote:
On Mon, 04 Feb 2013 11:27:05 +0100
Marek Szyprowski m.szyprow
Hi,
Can split patch into two parts?
One for USB tree, another for samsung tree.
Thank you,
Kyungmin Park
On Tue, Feb 5, 2013 at 9:37 AM, Dongjin Kim tobet...@gmail.com wrote:
This patch adds host phy support for Samsung's Exynos4412 SoC to
samsung-usbphy driver and its device node.
Cc
is for master; and 1 is for slave */
> + unsigned inti2c_mode;
If it's used for master or not, doesn't better to use 'is_master' or
'is_slave'? what's the meaning of 'i2c_mode'?
and
#define is_master(i2c) (i2c->is_master)
Thank you,
Kyungmin Park
> };
>
> static struct plat
;
If it's used for master or not, doesn't better to use 'is_master' or
'is_slave'? what's the meaning of 'i2c_mode'?
and
#define is_master(i2c) (i2c-is_master)
Thank you,
Kyungmin Park
};
static struct platform_device_id s3c24xx_driver_ids[] = {
@@ -202,11 +207,21 @@ static void
Acked-by: Kyungmin Park
On Thu, Nov 29, 2012 at 2:05 PM, Naveen Krishna Chatradhi
wrote:
> From: Simon Glass
>
> There is a rather odd feature of the exynos i2c controller that if it
> is left enabled, it can lock itself up with the clk line held low.
> This makes t
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
On Thu, Nov 29, 2012 at 2:05 PM, Naveen Krishna Chatradhi
ch.nav...@samsung.com wrote:
From: Simon Glass s...@chromium.org
There is a rather odd feature of the exynos i2c controller that if it
is left enabled, it can lock itself up
1 - 100 of 190 matches
Mail list logo
