On Wed, Nov 21, 2012 at 03:51:03PM +0800, Jaegeuk Hanse wrote:
> On 11/20/2012 10:58 PM, Fengguang Wu wrote:
> >On Tue, Nov 20, 2012 at 10:34:11AM -0300, Claudio Freire wrote:
> >>On Tue, Nov 20, 2012 at 5:04 AM, Fengguang Wu
> >>wrote:
> >>>Yes. The kernel readahead code by design will
On Wed, Nov 21, 2012 at 8:42 AM, Viresh Kumar wrote:
> Reviewed-by: Viresh Kumar
>
> This is what i was asking you earlier: "Doesn't gpiochip_add_pin_range
> have any users?" and you said NO and i didn't cross checked :(
Yes I forgot that I refactored the OF code to actually use this
On Tue, 20 Nov 2012 10:46:11 + Grant Likely
wrote:
> On Sat, Nov 17, 2012 at 12:19 AM, Bill Pemberton wrote:
> > CONFIG_HOTPLUG is no longer an optional setting. In order to remove
> > it as on option code paths that check CONFIG_HOTPLUG will removed
> > along with the attributes
On Wed, Nov 21, 2012 at 8:37 AM, Linus Walleij
wrote:
> From: Linus Walleij
>
> In commit c905165f5946f56dca195871641bd4e488eca24a
> "gpiolib: let gpiochip_add_pin_range() specify offset"
> I forgot to update the OF use of the function
> gpiochip_add_pin_range().
>
> It turns out that this
On Tue, Nov 20, 2012 at 06:00:34PM -0800, Darrick J. Wong wrote:
> This creates a per-backing-device counter that tracks the number of users
> which
> require pages to be held immutable during writeout. Eventually it will be
> used
> to waive wait_for_page_writeback() if nobody requires stable
On Tue, Nov 20, 2012 at 6:28 PM, Stephen Warren wrote:
> On 11/20/2012 07:04 AM, Linus Walleij wrote:
>> From: Linus Walleij
>>
>> If we try to create a range for a certain GPIO chip and the
>> target pin controller is not yet available it may return
>> a probe deferral error code, so handle
On Mon, Nov 19, 2012 at 9:15 PM, Ronny Meeus wrote:
> Hello
>
> I have an created an application that measures the cpuload consumed by
> the tasks within a process.
> For this I use the file /proc/stat and /proc//tasks//stat
>
> The cpuload monitor is a very simple application that just executes
On Fri, 16 Nov 2012 09:03:52 -0800 Greg Thelen wrote:
> We ran some netperf comparisons measuring the overhead of enabling
> CONFIG_MEMCG_KMEM with a kmem limit. Short answer: no regression seen.
>
> This is a multiple machine (client,server) netperf test. Both client
> and server machines
From: Linus Walleij
To be crystal clear on what the arguments mean in this
funtion dealing with both GPIO and PIN ranges with confusing
naming, we now have gpio_offset and pin_offset and we are
on the clear that these are offsets into the specific GPIO
and pin controller respectively. The GPIO
On 11/20/2012 10:58 PM, Fengguang Wu wrote:
On Tue, Nov 20, 2012 at 10:34:11AM -0300, Claudio Freire wrote:
On Tue, Nov 20, 2012 at 5:04 AM, Fengguang Wu wrote:
Yes. The kernel readahead code by design will outperform simple
fadvise in the case of clustered random reads. Imagine the access
On Wed, 2012-11-21 at 18:37 +1100, Nathan Williams wrote:
> Hi,
>
> I've come across a problem when loading a module straight after unmounting a
> JFFS2 partition.
> I'm using a Geos ADSL router board with an AMD Geode LX/CS5536 chipset and a
> Hynix H27U1G8F2BTR NAND flash.
>
> I can
On Wed, Nov 21, 2012 at 02:51:41PM +0800, Jaegeuk Hanse wrote:
> On 11/20/2012 11:15 PM, Fengguang Wu wrote:
> >On Tue, Nov 20, 2012 at 10:11:54PM +0800, Jaegeuk Hanse wrote:
> >>On 11/20/2012 04:04 PM, Fengguang Wu wrote:
> >>>Hi Claudio,
> >>>
> >>>Thanks for the detailed problem description!
>
On Fri, 16 Nov 2012 11:30:14 +0100 Philipp Zabel wrote:
> This patch keeps all created pools in a global list and adds two
> functions that allow to retrieve the gen_pool pointer from a known
> physical address and from a device tree node.
>
> ...
>
> +/*
> + * gen_pool_find_by_phys - find a
Hi,
I've come across a problem when loading a module straight after unmounting a
JFFS2 partition.
I'm using a Geos ADSL router board with an AMD Geode LX/CS5536 chipset and a
Hynix H27U1G8F2BTR NAND flash.
I can reproduce my problem with this shell script:
#!/bin/sh
mount -t jffs2 mtd:logs
On 21 November 2012 13:07, Linus Walleij wrote:
> From: Linus Walleij
>
> In commit c905165f5946f56dca195871641bd4e488eca24a
> "gpiolib: let gpiochip_add_pin_range() specify offset"
> I forgot to update the OF use of the function
> gpiochip_add_pin_range().
>
> It turns out that this reveal a
Add support for encoding PWM properties in bit encoded form with
of_pwm_xlate_with_flags() function support. Platforms require platform
specific PWM properties has to populate in 3rd cell of the pwm-specifier
and PWM driver should also set .of_xlate support with this function.
Currently PWM
Dave Jones reported a bug with futex_lock_pi() that his trinity test
exposed. Sometime between queue_me() and taking the q.lock_ptr, the
lock_ptr became NULL, resulting in a crash.
While futex_wake() is careful to not call wake_futex() on futex_q's with
a pi_state or an rt_waiter (which are
On Wed, Nov 21, 2012 at 9:16 AM, Yinghai Lu wrote:
> They are the same, could move them out from head32/64.c to setup.c.
>
> We are using memblock, and it could handle overlapping properly, so
> we don't need to reserve some at first to hold the location, and just
> need to make sure we reserve
On Tue, Nov 20, 2012 at 11:07:25AM -0600, Russ Anderson wrote:
> The issue isn't "ulong" vs "unsigned long". The issue
> is int is 32 bit and long is 64 bit on x86_64. Your
> patch is casting the value as an "unsigned long" (64 bit
> on x86_64) into an int (32 bit). I don't think that
> was
On Tue, Nov 20, 2012 at 6:24 PM, Stephen Warren wrote:
> On 11/20/2012 04:45 AM, Linus Walleij wrote:
>> From: Linus Walleij
>>
>> Like with commit 3c739ad0df5eb41cd7adad879eda6aa09879eb76
>> it is not always enough to specify all the pins of a gpio_chip
>> from offset zero to be added to a pin
From: Linus Walleij
In commit c905165f5946f56dca195871641bd4e488eca24a
"gpiolib: let gpiochip_add_pin_range() specify offset"
I forgot to update the OF use of the function
gpiochip_add_pin_range().
It turns out that this reveal a weakness in the
OF range mappings: ranges cannot currently be
Commit-ID: ee4eb87be2c3f69c2c4d9f1c1d98e363a7ad18ab
Gitweb: http://git.kernel.org/tip/ee4eb87be2c3f69c2c4d9f1c1d98e363a7ad18ab
Author: Jan Beulich
AuthorDate: Fri, 2 Nov 2012 11:18:39 +
Committer: H. Peter Anvin
CommitDate: Tue, 20 Nov 2012 22:23:57 -0800
x86-64: Fix ordering of
Commit-ID: 36c46ca4f322a7bf89aad5462a3a1f61713edce7
Gitweb: http://git.kernel.org/tip/36c46ca4f322a7bf89aad5462a3a1f61713edce7
Author: Boris Ostrovsky
AuthorDate: Thu, 15 Nov 2012 13:41:50 -0500
Committer: H. Peter Anvin
CommitDate: Tue, 20 Nov 2012 22:23:28 -0800
x86, microcode, AMD:
Commit-ID: cb57a2b4cff7edf2a4e32c0163200e9434807e0a
Gitweb: http://git.kernel.org/tip/cb57a2b4cff7edf2a4e32c0163200e9434807e0a
Author: H. Peter Anvin
AuthorDate: Tue, 20 Nov 2012 22:21:02 -0800
Committer: H. Peter Anvin
CommitDate: Tue, 20 Nov 2012 22:23:23 -0800
x86-32: Export
Commit-ID: 1022623842cb72ee4d0dbf02f6937f38c92c3f41
Gitweb: http://git.kernel.org/tip/1022623842cb72ee4d0dbf02f6937f38c92c3f41
Author: Robert Richter
AuthorDate: Mon, 3 Sep 2012 20:54:48 +0200
Committer: H. Peter Anvin
CommitDate: Tue, 20 Nov 2012 22:23:20 -0800
x86-32: Fix invalid
On Tue, Nov 20, 2012 at 02:48:58PM -0800, Doug Anderson wrote:
> From: Olof Johansson
>
> UART3 is used for debugging on exynos5250-snow.
>
> [dianders: cleaned commit message.]
>
> Signed-off-by: Olof Johansson
> Signed-off-by: Doug Anderson
>
> ---
> arch/arm/Kconfig.debug| 11
From: "H. Peter Anvin"
When we write entropy into a non-empty pool, we currently don't
account at all for the fact that we will probabilistically overwrite
some of the entropy in that pool. This means that unless the pool is
fully empty, we are currently *guaranteed* to overestimate the amount
From: "H. Peter Anvin"
Use a macro to statically compute poolbitshift (will be used in a
subsequent patch), poolbytes, and poolbits. On virtually all
architectures the cost of a memory load with an offset is the same as
the one of a memory load.
It is still possible for this to generate worse
From: "H. Peter Anvin"
When we write entropy into a non-empty pool, we currently don't
account at all for the fact that we will probabilistically overwrite
some of the entropy in that pool. This means that unless the pool is
fully empty, we are currently *guaranteed* to overestimate the amount
On Tue, Nov 20, 2012 at 02:27:03PM -0800, Doug Anderson wrote:
> This is similar to a recent commit for exynos5250 titled:
> ARM: EXYNOS: Add aliases for i2c controller
>
> Adding aliases will be useful to prevent warnings in a future
> change. See:
> i2c: s3c2410: Get the i2c bus number
This allows platform_device_add a chance to call insert_resource
on all of the resources from OF. At a minimum this fills in proc/iomem
and presumably makes resource tracking and conflict detection work
better.
Signed-off-by: Jason Gunthorpe
---
drivers/of/device.c |2 +-
1 files changed, 1
On Tue, Nov 20, 2012 at 01:30:58PM +0100, Michal Simek wrote:
> Hi Josh, Arnd and Olof,
>
> 2012/11/19 Josh Cartwright :
> > Michal-
> >
> > Here's an attempt at supporting ARCH_MULTIPLATFORM on Zynq. I've gotten
> > a multiplatform kernel building and booting on the zc702, although I
> >
when nonblock read the condition check (file->f_flags & O_NONBLOCK)
always be true,
signal_pending and device exist checking never get a chance to run, so
the user mode code always
get EAGAIN even if device removed. move nonblock mode checking to the
last can fix this problem.
Signed-off-by:
commit 08da5a2ca
x86_64: Early segment setup for VT
add lldt/ltr to clean more segments.
Those code are put in code64, and it is using gdt that is only
loaded from code32 path.
That breaks booting with 64bit bootloader that does not go through
code32 path, and get at startup_64 directly,
At that stage, it is already in 32bit protected mode or 64bit mode.
so we do not need to check if ptr less 1M.
When go from other boot loader (kexec) instead of boot/ code path.
Move out accessible checking out __cmdline_find_option
So misc.c will parse cmdline and have debug print out.
We are short of space before 0x200 that is entry for startup_64.
And we can not change startup_64 to other value --- ABI ?
We could move function verify_cpu down, and that could avoid extra
code of jmp back and forth.
Signed-off-by: Yinghai Lu
Cc: Matt Fleming
---
later will check ext_cmd_line_ptr at the same time.
Signed-off-by: Yinghai Lu
---
arch/x86/boot/compressed/cmdline.c | 10 --
arch/x86/kernel/head64.c | 13 +++--
2 files changed, 19 insertions(+), 4 deletions(-)
diff --git a/arch/x86/boot/compressed/cmdline.c
They are the same, could move them out from head32/64.c to setup.c.
We are using memblock, and it could handle overlapping properly, so
we don't need to reserve some at first to hold the location, and just
need to make sure we reserve them before we are using memblock to find
free mem to use.
There several places to find ramdisk information early for reserving
and relocating.
Use functions to make code more readable and consistent.
Later will add ext_ramdisk_image/size in those functions to support
loading ramdisk above 4g.
Signed-off-by: Yinghai Lu
---
arch/x86/kernel/setup.c |
boot/compressed/misc.c could be with 64 bit, and cmd_line_ptr could
above 4g.
So change to unsigned long instead. that will be 64bit in 64bit,
and 32bit in 32bit.
Signed-off-by: Yinghai Lu
---
arch/x86/boot/boot.h|8
arch/x86/boot/cmdline.c |4 ++--
2 files changed, 6
When 64bit bootloader put real mode data above 4g, We can not
access real mode data directly.
because in arch/x86/kernel/head_64.S, only set ident mapping
for 0-1g, and kernel code/data/bss.
So need to move early_ioremap_init() calling from setup_arch
to x86_64_start_kernel.
Also use rsi/rdi
Now 64bit kernel supports more than 1T ram and kexec tools
could find buffer above 1T, remove that obsolete limitation.
and use MAXMEM instead.
Tested on system more than 1024g ram.
Signed-off-by: Yinghai Lu
Cc: "Eric W. Biederman"
---
arch/x86/include/asm/kexec.h |6 +++---
1 files
Current kernel is not allowed to be loaded above 512g, it thinks
that address is too big.
We only need to add one extra spare page for needed level3 to
point another 512g range.
Need to check _text range and set level4 pg to point to that spare
level3 page, and set level3 to point to level2 page
Now we have limit kdump reseved under 896M, because kexec has the limitation.
and also bzImage need to stay under 4g.
To make kexec/kdump could use range above 4g, we need to make bzImage and
ramdisk could be loaded above 4g.
During booting bzImage will be unpacked on same postion and stay high.
ext_ramdisk_image/size will record high 32bits for ramdisk info.
xloadflags bit0 will be set if relocatable with 64bit.
Let get_ramdisk_image/size to use ext_ramdisk_image/size to get
right positon for ramdisk.
bootloader will fill value to ext_ramdisk_image/size when it load
ramdisk high.
Current when kernel is loaded above 1G, only [_text, _text+2M]
is set up with extra ident page table.
That is not enough, some variables that could be used early are
out of that range. (like gdt...)
Just set map for [_text, _end] include text/data/bss/brk...
Signed-off-by: Yinghai Lu
Cc: "Eric
The TPM will respond to TPM_GET_CAP with TPM_ERR_INVALID_POSTINIT if
TPM_STARTUP has not been issued. Detect this and automatically
issue TPM_STARTUP.
This is for embedded applications where the kernel is the first thing
to touch the TPM.
Signed-off-by: Jason Gunthorpe
---
On Mon, Nov 19, 2012 at 06:38:24PM +0100, Nicolas Ferre wrote:
> Arnd, Olof,
>
> A very little cleanup single patch for AT91.
>
> The following changes since commit 77b67063bb6bce6d475e910d3b886a606d0d91f7:
>
> Linux 3.7-rc5 (2012-11-11 13:44:33 +0100)
>
> are available in the git repository
On Mon, Nov 19, 2012 at 05:59:04PM +0100, Nicolas Ferre wrote:
> Arnd, Olof,
>
> A little fix that goes on top of the modification of headers made
> by Jean-Christophe. Obviously, I have placed this one on top of your current
> at91/header branch.
>
> The following changes since commit
On Mon, Nov 19, 2012 at 18:13:56, Philip, Avinash wrote:
>
> On Thu, Nov 15, 2012 at 16:52:14, Artem Bityutskiy wrote:
> > On Wed, 2012-10-31 at 12:38 +0530, Philip, Avinash wrote:
> > > Support to use ELM as BCH 4 & 8 bit error correction module. Also
> > > performance
> > > enhancement by
Hi,
On Tue, Nov 20, 2012 at 09:59:27AM +0100, Nicolas Ferre wrote:
> Arnd, Olof,
>
> Just for the record, I do not want to put pressure at a such late time in
> the 3.7-rc process. So, I just reworked that pull-request because the previous
> one was wrong:
> - wrong patch content (DT nodes with
This provides an open firwmare driver binding for tpm_tis. OF
is useful on arches where PNP is not used.
Allow the tpm_tis driver to be selected if PNP or OF are compiled in.
Signed-off-by: Jason Gunthorpe
---
drivers/char/tpm/Kconfig |2 +-
drivers/char/tpm/tpm_tis.c | 76
Hi Aaro,
On Sun, Nov 18, 2012 at 06:36:22PM +0200, Aaro Koskinen wrote:
> Add Retu power button driver.
>
This patch (with minot edits) has been queued to 3.8.
Thanks!
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Documentation/printk-formats.txt says to use %zd for a ssize_t argument
and some drivers do. Unfortunately this prints a positive number for
negative values eg:
tpm_tis 7003.tpm_tis: tpm_transmit: tpm_send: error 4294967234
Add a case to va_args a ssize_t type if the interpretation should be
On 11/20/2012 11:15 PM, Fengguang Wu wrote:
On Tue, Nov 20, 2012 at 10:11:54PM +0800, Jaegeuk Hanse wrote:
On 11/20/2012 04:04 PM, Fengguang Wu wrote:
Hi Claudio,
Thanks for the detailed problem description!
Hi Fengguang,
Another question, thanks in advance.
What's the meaning of
On 2012-11-20 Tuesday at 13:50 -0800 Kees Cook wrote:
> Since devtmpfs is writable, make the default noexec,nosuid as well. This
> protects from the case of a privileged process having an arbitrary file
> write flaw and an argumentless arbitrary execution (i.e. it would lack
> the ability to run
This is introduced by commit 9ab6e988
"gpiolib: return any error code from range creation".
Signed-off-by: Axel Lin
---
This patch is against LinusW's linux-pinctrl tree, for-next branch.
Axel
drivers/gpio/gpiolib.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
Hi Tang,
2012/11/21 14:58, Tang Chen wrote:
> Hi Ishimatsu-san,
>
> Thanks for the comments.
>
> And I also found the some algorithm problems in patch2 ~ patch3.
> I am working on it, and a v2 patchset is coming soon. :)
O.K.
I'm waiting nwe patch-set.
Thanks,
Yasuaki Ishimatsu
>
> Thanks.
Hi Tang,
When I applied the patch, following error occurred.
mm/page_alloc.c: In function ‘insert_movablecore_map’:
mm/page_alloc.c:5061: error: label ‘out’ used but not defined
Thanks,
Yasuaki Ishimatsu
2012/11/19 23:27, Tang Chen wrote:
> This patch adds functions to parse movablecore_map
Hi Ishimatsu-san,
Thanks for the comments.
And I also found the some algorithm problems in patch2 ~ patch3.
I am working on it, and a v2 patchset is coming soon. :)
Thanks.
On 11/21/2012 01:46 PM, Yasuaki Ishimatsu wrote:
> Hi Tang,
>
> 2012/11/19 23:27, Tang Chen wrote:
>> From: Yasuaki
Hi Tang,
2012/11/19 23:27, Tang Chen wrote:
> From: Yasuaki Ishimatsu
>
> If system can create movable node which all memory of the
> node is allocated as ZONE_MOVABLE, setup_node_data() cannot
> allocate memory for the node's pg_data_t.
> So when memblock_alloc_nid() fails, setup_node_data()
Hi Tang,
The patch has two extra whitespaces.
2012/11/19 23:27, Tang Chen wrote:
> This patch adds functions to parse movablecore_map boot option. Since the
> option could be specified more then once, all the maps will be stored in
> the global variable movablecore_map.map array.
>
> And also,
Hi Wei,
Similar patch already submitted:
http://www.spinics.net/lists/kernel/msg1439539.html
Thanks,
Sachin
On 21 November 2012 11:01, Wei Yongjun wrote:
> From: Wei Yongjun
>
> Remove duplicated include.
>
> dpatch engine is used to auto generate this patch.
>
On Tue, Nov 20, 2012 at 20:37:55, Thierry Reding wrote:
> On Mon, Nov 19, 2012 at 11:21:12PM +0530, Philip, Avinash wrote:
> [...]
> > diff --git a/include/linux/pwm.h b/include/linux/pwm.h
> > index 112b314..70756f2 100644
> > --- a/include/linux/pwm.h
> > +++ b/include/linux/pwm.h
> > @@ -78,6
kfree on a NULL pointer is a no-op.
Signed-off-by: Sachin Kamat
---
drivers/tty/vt/consolemap.c |6 ++
1 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/tty/vt/consolemap.c b/drivers/tty/vt/consolemap.c
index 2aaa0c2..248381b 100644
--- a/drivers/tty/vt/consolemap.c
At 11/21/2012 01:03 PM, Jaegeuk Hanse Wrote:
> On 11/21/2012 12:42 PM, Wen Congyang wrote:
>> At 11/21/2012 12:22 PM, Jaegeuk Hanse Wrote:
>>> On 11/21/2012 11:05 AM, Wen Congyang wrote:
At 11/20/2012 07:16 PM, Jaegeuk Hanse Wrote:
> On 11/01/2012 05:44 PM, Wen Congyang wrote:
>>
On Wed, Nov 21, 2012 at 03:27:12AM +0100, Laurent Pinchart wrote:
> Add arch code to register the PFC platform device instead of calling the
> driver directly. Platform device registration in the sh-pfc driver will
> be removed.
I'm not really sure that I understand the motivation for
moving
On Wed, Nov 21, 2012 at 8:37 AM, Andrea Adami wrote:
> * Since 3.3 gpio wakeup is broken on pxa25x (tested on corgi and poodle).
> * Use gpio_set_wake like done for pxa27x with commit id
> * b95ace54a23e2f8ebb032744cebb17c9f43bf651
>
> Signed-off-by: Andrea Adami
> ---
>
'g' is cast to the error return code. Hence gives the following error
which is fixed by this patch.
drivers/devfreq/devfreq.c:645 devfreq_remove_governor() error:
'g' dereferencing possible ERR_PTR()
Signed-off-by: Sachin Kamat
---
drivers/devfreq/devfreq.c |2 +-
1 files changed, 1
Use the value obtained from the function instead of -EINVAL.
Signed-off-by: Sachin Kamat
---
drivers/devfreq/devfreq.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
index 83c2129..2bd9ab0 100644
---
This commit adds debugfs directory and nodes for inspecting internal
state of System MMU.
Change-Id: I4afcdd925609d381e7329ec118ffe52e38dc340e
Signed-off-by: KyongHo Cho
---
drivers/iommu/exynos-iommu.c | 204 +--
1 file changed, 198 insertions(+), 6
On Thu, 8 Nov 2012, Robert Jarzmik wrote:
> --- a/mm/filemap.c
> +++ b/mm/filemap.c
> @@ -467,6 +471,7 @@ int add_to_page_cache_locked(struct page *page, struct
> address_space *mapping,
> } else {
> page->mapping = NULL;
> /* Leave
This commit adds System MMU name to the driver data of each System
MMU. It is used by fault information.
Change-Id: If6720b69609880873ebaf160188f1e726a67b806
Signed-off-by: KyongHo Cho
---
drivers/iommu/exynos-iommu.c | 100 ---
1 file changed, 76
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
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.
Change-Id: Ic04c8f259d8b8af2846175dd7b98dbc4e463c96e
Signed-off-by: KyongHo Cho
---
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 suspend/resume on the device is also
propagated to the System MMU.
If a
At 11/21/2012 01:03 PM, Jaegeuk Hanse Wrote:
> On 11/21/2012 12:42 PM, Wen Congyang wrote:
>> At 11/21/2012 12:22 PM, Jaegeuk Hanse Wrote:
>>> On 11/21/2012 11:05 AM, Wen Congyang wrote:
At 11/20/2012 07:16 PM, Jaegeuk Hanse Wrote:
> On 11/01/2012 05:44 PM, Wen Congyang wrote:
>>
Since acquiring read_lock is not more frequent than write_lock, it is
not beneficial to use rwlock, this commit changes rwlock to spinlock.
Change-Id: Ia3365ccec0744e735b71f0389e5c56a0243bcd2c
Signed-off-by: KyongHo Cho
---
drivers/iommu/exynos-iommu.c | 32
1
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.
Change-Id: Ia25642c7c0143d2c50a8ed5a3d0dd9067f324c4e
Signed-off-by: KyongHo Cho
---
drivers/iommu/exynos-iommu.c | 24
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.
This commit adds device tree support for System MMU.
Change-Id: If695448af4bd7829ad1543814281dfa8ce1e7aae
Signed-off-by: KyongHo Cho
---
drivers/iommu/Kconfig| 2 +-
drivers/iommu/exynos-iommu.c | 289 ++-
2 files changed, 177 insertions(+), 114
This commit adds System MMU nodes to DT of Exynos SoCs.
Change-Id: I30ea7adcc9c0ded876618f372ed1a5c5e935ee20
Signed-off-by: KyongHo Cho
---
.../devicetree/bindings/arm/exynos/system-mmu.txt | 86
arch/arm/boot/dts/exynos4210.dtsi | 96 ++
On 11/21/2012 12:42 PM, Wen Congyang wrote:
At 11/21/2012 12:22 PM, Jaegeuk Hanse Wrote:
On 11/21/2012 11:05 AM, Wen Congyang wrote:
At 11/20/2012 07:16 PM, Jaegeuk Hanse Wrote:
On 11/01/2012 05:44 PM, Wen Congyang wrote:
From: Yasuaki Ishimatsu
Currently __remove_section for
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.
Change-Id:
This removes System MMU initialization from arch/arm/mach-exynos/
to move them to DT and the exynos-iommu driver except gating clock
definitions.
Change-Id: Ie29f587c01c645f28fc0e0b94eb3631a0170ebf5
Signed-off-by: KyongHo Cho
---
arch/arm/mach-exynos/Kconfig | 5 -
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
From: Namhyung Kim
The perf session environment information was saved (so allocated)
during perf_session__open, but was not freed. As free(3) handles NULL
pointer input properly it won't cause a issue for writing modes -
e.g. perf record
Cc: Feng Tang
Signed-off-by: Namhyung Kim
---
On Tue, Nov 20, 2012 at 2:31 AM, Stephen Warren wrote:
> From: Stephen Warren
>
> Now that the only field in struct sys_timer is .init, delete the struct,
> and replace the machine descriptor .timer field with the initialization
> function itself.
>
> This will enable moving timer drivers into
As per kernel coding style, if one branch of conditional statement has braces,
the other one should have too.
Signed-off-by: Sachin Kamat
---
drivers/extcon/extcon-max77693.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/extcon/extcon-max77693.c
Signed-off-by: Sachin Kamat
---
Hi Chanwoo,
Please merge this patch with the previous one titled
"extcon: max77693: Use devm_kzalloc"
---
drivers/extcon/extcon-max77693.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/extcon/extcon-max77693.c
Hi Linus !
Here are small 52xx fixes that Anatolij asked me to pull a while back
and that I completely missed. The stuff is local to that platform code,
and was in next for a while, so it should still go into 3.7.
Thanks,
Ben.
The following changes since commit
At 11/21/2012 12:22 PM, Jaegeuk Hanse Wrote:
> On 11/21/2012 11:05 AM, Wen Congyang wrote:
>> At 11/20/2012 07:16 PM, Jaegeuk Hanse Wrote:
>>> On 11/01/2012 05:44 PM, Wen Congyang wrote:
From: Yasuaki Ishimatsu
Currently __remove_section for SPARSEMEM_VMEMMAP does nothing. But
This patch supports exynos's emulation mode with newly created sysfs node.
Exynos 4x12 (4212, 4412) and 5 series provide emulation mode for thermal
management unit. Thermal emulation mode supports software debug for TMU's
operation. User can set temperature manually with software code and TMU
will
On Wed, Nov 21, 2012 at 03:27:01AM +0100, Laurent Pinchart wrote:
> Hi everybody,
>
> Here's a pretty large patch series that rework pin control and GPIO support
> for SH and ARM SH/Renesas Mobile/Car platforms. The patches are based on top
> of v3.7-rc6. You can get them from my git tree at
>
>
On 11/19/2012 10:45 PM, Viresh Kumar wrote:
> This adds following helper routines:
> - of_property_read_u8_array()
> - of_property_read_u16_array()
> - of_property_read_u8()
> - of_property_read_u16()
>
> This expects arrays from DT to be passed as:
> - u8 array:
> property = /bits/ 8 <0x50
On 11/20/2012 09:37 PM, Michael S. Tsirkin wrote:
> On Tue, Nov 20, 2012 at 02:39:40PM +0800, Asias He wrote:
>> On 11/20/2012 04:26 AM, Michael S. Tsirkin wrote:
>>> On Mon, Nov 19, 2012 at 04:53:42PM +0800, Asias He wrote:
vhost-blk is an in-kernel virito-blk device accelerator.
Hi Grant,
On Wednesday 21 November 2012 05:54:29 Grant Likely wrote:
> > With the advent of the device tree and of ARM kernels that are not
> > board-tied, we cannot rely on these board-specific hooks anymore but
>
> This isn't strictly true. It is still perfectly fine to have board
> specific
On 11/21/2012 11:05 AM, Wen Congyang wrote:
At 11/20/2012 07:16 PM, Jaegeuk Hanse Wrote:
On 11/01/2012 05:44 PM, Wen Congyang wrote:
From: Yasuaki Ishimatsu
Currently __remove_section for SPARSEMEM_VMEMMAP does nothing. But
even if
we use SPARSEMEM_VMEMMAP, we can unregister the
On Tue, Nov 20, 2012 at 03:57:35PM -0800, Andrew Morton wrote:
> On Thu, 8 Nov 2012 20:54:10 +0100
> Robert Jarzmik wrote:
.
> > + __field(dev_t, s_dev)
>
> Perhaps use super_block.s_id here
>
> > + ),
> > +
> > + TP_fast_assign(
> > + __entry->page = page;
> > +
(2012/11/21 11:48), David Rientjes wrote:
Move the check for !mm out of line as suggested by Andrew.
Signed-off-by: David Rientjes
Thank you very much !
Acked-by: KAMEZAWA Hiroyuki
---
include/linux/memcontrol.h |2 +-
mm/memcontrol.c|3 +++
2 files changed, 4
1 - 100 of 1674 matches
Mail list logo
