> From: Stefan Roese
>
> The Allwinner A10 has an ethernet controller that is advertised as
> coming from Davicom.
>
> The exact feature set of this controller is unknown, since there is no
> public documentation for this IP, and this driver is mostly the one
> published by Allwinner that has
On Wednesday 13 March 2013 01:25 AM, Mark Brown wrote:
* PGP Signed by an unknown key
On Thu, Mar 07, 2013 at 10:03:17PM +0530, Laxman Dewangan wrote:
/**
+ * The Regmap IRQ type Index
+ * REGMAP_IRQ_TYPE_NONE is used for setting inital value for clearing type.
+ */
+enum {
+
Hello Maxime, Stefan,
Please find below some comments regarding your PHY implementation in the driver
as well as the transmit and transmit completion routines.
Le vendredi 15 mars 2013 21:50:00, Maxime Ripard a écrit :
> From: Stefan Roese
>
> The Allwinner A10 has an ethernet controller that
On 03/16/2013 01:37 AM, Doug Anderson wrote:
> On Fri, Mar 15, 2013 at 2:53 PM, Lars-Peter Clausen wrote:
>> What exactly is the spinlock protecting against here? Concurrent runs of
>> exynos_adc_isr? This is probably not issue in the first place.
>>
>> What you want to protect against is that
On Sat, Mar 16, 2013 at 08:41:30AM -0400, Eduardo Valentin wrote:
> On 16-03-2013 04:59, Dan Carpenter wrote:
> >On Fri, Mar 15, 2013 at 09:00:35AM -0400, Eduardo Valentin wrote:
> >>@@ -502,9 +504,9 @@ int _omap_bandgap_write_threshold(struct omap_bandgap
> >>*bg_ptr, int id, int val,
> >>if
On 03/15/2013 10:34 AM, Wanpeng Li wrote:
> Compression of zero-filled pages can unneccessarily cause internal
> fragmentation, and thus waste memory. This special case can be
> optimized.
>
> This patch captures zero-filled pages, and marks their corresponding
> zcache backing page entry as
On 03/06/2013 11:52 PM, Seth Jennings wrote:
> =
> DO NOT MERGE, FOR REVIEW ONLY
> This patch introduces zsmalloc as new code, however, it already
> exists in drivers/staging. In order to build successfully, you
> must select EITHER to driver/staging version OR this version.
> Once
On Sat, Mar 16, 2013 at 08:36:51AM -0400, Eduardo Valentin wrote:
> >But that said, I don't care for the RMW_BITS() very much as a long
> >term thing. If we just used pointers instead of passing the offset
> >into the bg_ptr->conf->sensors[] array then everything would be a
> >lot cleaner.
> >
>
On Sat, Mar 16, 2013 at 08:49:20AM -0400, Eduardo Valentin wrote:
> On 16-03-2013 04:39, Dan Carpenter wrote:
> >On Fri, Mar 15, 2013 at 09:00:21AM -0400, Eduardo Valentin wrote:
> >>if (ret) {
> >>dev_err(bg_ptr->dev, "failed to read thot\n");
> >>- return -EIO;
> >>+
Linus Torvalds:
> Yes. That would be lovely. And trivial for most filesystems to support.
>
> Sure, you could have an inode if you need to (not all filesystems may
> have a flag in the directory entry), so it would look like "mknod()"
> for the filesystem. But the filesystem might decide to never
On Sat, Mar 16, 2013 at 08:39:11AM -0400, Eduardo Valentin wrote:
> Hey Dan,
>
> On 15-03-2013 17:22, Dan Carpenter wrote:
> >On Fri, Mar 15, 2013 at 08:59:57AM -0400, Eduardo Valentin wrote:
> >>Change the way the omap_bandgap_power is written so that it has only
> >>one exit entry
Al Viro:
> Sure - btrfs happens to have an interesting limit on the number of
> links to the same object located in one directory.
It doesn't matter.
On every filesystem, the link count has its upper limit eventually. When
vfs_link() for whiteout returns EMLINK, aufs removes the whiteout-src
Instead of converting the 800 or so uses of seq_printf with
a constant format (without a % substitution) to seq_puts,
maybe there's another way to slightly speed up these outputs.
Taking a similar approach to commit abd84d60eb
("tracing: Optimize trace_printk() with one arg to use trace_puts()")
On Sat, Mar 16, 2013 at 04:15:24AM +, Ben Hutchings wrote:
> On Tue, 2013-03-12 at 15:44 -0700, Greg Kroah-Hartman wrote:
> > 3.0-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Mark Brown
> >
> > commit
Two of them (zcache DebugFS cleanup) and the module loading
capability are now in linux-next for v3.10.
Also Bob Liu is full-time going to help on knocking these items
off the list.
CC: bob@oracle.com
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/staging/zcache/TODO | 6 +-
1 file
On Sat, Mar 16, 2013 at 8:39 PM, Hillf Danton wrote:
> init rb node before use due to empty node checked by rb_next().
>
> --- a/fs/sysfs/dir.cSat Mar 16 20:12:16 2013
> +++ b/fs/sysfs/dir.cSat Mar 16 20:37:10 2013
> @@ -396,6 +396,7 @@ struct sysfs_dirent *sysfs_new_dirent(co
>
>
On Fri, Mar 15, 2013 at 10:34:18AM +0800, Wanpeng Li wrote:
> Increment/decrement zcache_[eph|pers]_zpages for zero-filled pages,
> the main point of the counters for zpages and pageframes is to be
> able to calculate density == zpages/pageframes. A zero-filled page
> becomes a zpage that
The old IEEE 1394 driver stack was removed in v2.6.37. That made the
checks for two Kconfig (module) macros unneeded, since they will now
always evaluate to true. Remove these two checks.
Signed-off-by: Paul Bolle
---
Perhaps these alias can be dropped entirely. Bat that's not my call.
On Thu, Mar 14, 2013 at 06:08:15PM +0800, Wanpeng Li wrote:
> Compression of zero-filled pages can unneccessarily cause internal
> fragmentation, and thus waste memory. This special case can be
> optimized.
>
> This patch captures zero-filled pages, and marks their corresponding
> zcache backing
On Thu, Mar 14, 2013 at 06:08:16PM +0800, Wanpeng Li wrote:
> Introduce zero-filled page statistics to monitor the number of
> zero-filled pages.
Hm, you must be using an older version of the driver. Please
rebase it against Greg KH's staging tree. This is where most if not
all of the DebugFS
On Thu, Mar 14, 2013 at 06:08:14PM +0800, Wanpeng Li wrote:
> Introduce zero-filled pages handler to capture and handle zero pages.
>
> Acked-by: Dan Magenheimer
> Signed-off-by: Wanpeng Li
> ---
> drivers/staging/zcache/zcache-main.c | 26 ++
> 1 files changed, 26
Applied.
johannes
--
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 at http://www.tux.org/lkml/
I have an Acer Aspire One netbook with a built in card reader, and I
have two cards, one with 32 MB and one with 4 GB. The card reader used
to work with the staging driver in 3.7.10, but the new 3.8.3 driver
does not work with the larger card. The old driver was removed in
commit cd211222.
Now,
On 16-03-2013 04:39, Dan Carpenter wrote:
On Fri, Mar 15, 2013 at 09:00:21AM -0400, Eduardo Valentin wrote:
if (ret) {
dev_err(bg_ptr->dev, "failed to read thot\n");
- return -EIO;
+ ret = -EIO;
+ goto exit;
}
-
Hello Dan,
On 16-03-2013 05:05, Dan Carpenter wrote:
I've reviewed this set.
I hate to make people redo whole patchset sets, and I hate
re-reviewing code. Obviously, I don't really like the bunny hop
patches and I'm trying to discourage that going forward. ;P But
I wouldn't say it's a "Redo
On 16-03-2013 04:59, Dan Carpenter wrote:
On Fri, Mar 15, 2013 at 09:00:35AM -0400, Eduardo Valentin wrote:
Because there is a need to lock inside IRQ handler, this patch
changes the locking mechanism inside the omap-bandgap.[c,h] to
spinlocks. Now this lock is used to protect omap_bandgap
Hey Dan,
On 15-03-2013 17:22, Dan Carpenter wrote:
On Fri, Mar 15, 2013 at 08:59:57AM -0400, Eduardo Valentin wrote:
Change the way the omap_bandgap_power is written so that it has only
one exit entry (Documentation/CodingStyle).
It's only if there is an unlock or something that you should
On Fri, Mar 15, 2013 at 1:04 PM, Sasha Levin wrote:
> On 03/15/2013 12:03 AM, Sasha Levin wrote:
>> On 03/07/2013 01:26 AM, Dave Jones wrote:
>>> On Thu, Mar 07, 2013 at 02:02:30PM +0800, Greg Kroah-Hartman wrote:
>>> > On Thu, Mar 07, 2013 at 12:28:54AM -0500, Dave Jones wrote:
>>> > > general
Hello Dan,
On 15-03-2013 17:09, Dan Carpenter wrote:
On Fri, Mar 15, 2013 at 08:59:55AM -0400, Eduardo Valentin wrote:
This patch introduce a macro to read, update, write bitfields.
It will be specific to bandgap data structures.
Signed-off-by: Eduardo Valentin
---
I have an Acer Aspire One netbook, and on it I get the following
warning when closing and opening the lid. I think this warning first
appeared in 3.7.
Does this need fixing? If so, who can do it?
Thanks,
Richard
** close lid
Mar 16 11:32:03 netboy kernel: [ 287.429404]
The objects allocated by devm_* APIs are managed by devres and are freed
when the device is detached. There is no need to use kfree() explicitly.
Signed-off-by: Silviu-Mihai Popescu
---
drivers/staging/imx-drm/ipu-v3/ipu-dp.c |1 -
1 file changed, 1 deletion(-)
diff --git
Correct spelling typos
Signed-off-by: Masanari Iida
---
arch/arc/plat-arcfpga/Kconfig | 2 +-
arch/blackfin/include/asm/bfin_sport3.h | 2 +-
arch/s390/kernel/irq.c | 2 +-
arch/s390/kvm/trace.h | 2 +-
drivers/crypto/caam/ctrl.c |
The objects allocated by devm_* APIs are managed by devres and are freed when
the device is detached. Hence there is no need to use kfree() explicitly.
Signed-off-by: Silviu-Mihai Popescu
---
sound/soc/soc-core.c |2 --
1 file changed, 2 deletions(-)
diff --git a/sound/soc/soc-core.c
Add functions to parse movablemem_map boot option. Since the option
could be specified more then once, all the maps will be stored in the
global array movablemem_map.map[].
And also, we keep the array in monotonic increasing order by start_pfn.
And merge all overlapped ranges.
Signed-off-by:
On Sat, Mar 16, 2013 at 02:33:23AM -0700, Raymond Jennings wrote:
> On Sat, Mar 16, 2013 at 2:25 AM, Hillf Danton wrote:
> >> Some system specifications:
> >> - CPU: i7 860 at 2.8 GHz
> >> - Mainboard: Advantech AIMB-780
> >> - RAM: 4 GB
> >> - Kernel: 2.6.35.11 SMP, 32 bit (kernel.org kernel, no
The Hot Pluggable field in SRAT points out if the memory could be
hotplugged while the system is running. It is useful to print out
this info when parsing SRAT.
Signed-off-by: Tang Chen
---
arch/x86/mm/srat.c |9 ++---
1 files changed, 6 insertions(+), 3 deletions(-)
diff --git
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, use memblock_alloc_try_nid() instead of memblock_alloc_nid()
to retry when the first allocation fails.
Ensure memblock will not allocate memory from areas that may be
ZONE_MOVABLE. The map info is from movablemem_map boot option.
The following problem was reported by Stephen Rothwell:
The definition of struct movablecore_map is protected by
CONFIG_HAVE_MEMBLOCK_NODE_MAP but its use in
Hi Yinghai, all,
As Yinghai have implemented parsing numa info early more considerately,
I think we can introduce the movablemem_map boot option again.
This patch-set is based on Linux 3.9 rc-2, but need to apply Yinghai's
"x86, ACPI, numa: Parse numa info early" patch-set first.
Please refer
Since node info in SRAT may not be in increasing order, we may meet
a lower range after we handled a higher range. So we need to keep
the lowest movable pfn each time we parse a SRAT memory entry, and
update it when we get a lower one.
This patch introduces a new array zone_movable_limit[], which
If kernelcore or movablecore is specified at the same time with
movablemem_map, movablemem_map will have higher priority to be
satisfied. This patch will make find_zone_movable_pfns_for_nodes()
calculate zone_movable_pfn[] with the limit from zone_movable_limit[].
Signed-off-by: Tang Chen
As mentioned by Liu Jiang and Wu Jiangguo, users could specify DMA,
DMA32, and HIGHMEM as movable. In order to ensure the kernel will
work correctly, we should exclude these memory ranges out from
zone_movable_limit[].
NOTE: Do find_usable_zone_for_movable() to initialize movable_zone
so
We now provide an option for users who don't want to specify physical
memory address in kernel commandline.
/*
* For movablemem_map=acpi:
*
* SRAT:|_| |_| |_| |_| ..
* node id:0 1
When implementing movablemem_map boot option, we introduced an array
movablemem_map.map[] to store the memory ranges to be set as ZONE_MOVABLE.
Since ZONE_MOVABLE is the latst zone of a node, if user didn't specify
the whole node memory range, we need to extend it to the node end so that
we can
Hi Javier,
On Sat, Mar 16, 2013 at 2:53 PM, Javier Martinez Canillas
wrote:
> On Sat, Mar 16, 2013 at 5:44 AM, Anil Kumar wrote:
>> Hi,
>>
>> I am getting kernel uImage build issue on omap2+ log[1]
>>
>> Taken kernel branch "for_3.10/dts" from
>>
On Thursday 14 of March 2013, Arkadiusz Miskiewicz wrote:
> Hello.
>
> After upgrading from 3.8.2 to 3.8.3 I'm getting regression :
More people hits this:
https://bugzilla.redhat.com/show_bug.cgi?id=922304
https://bugs.archlinux.org/task/34327
(seems always GM45 gpu in these reports)
archlinux
On Fri, 4 Jan 2013 21:31:07 +0200, Pantelis Antoniou
wrote:
> There are other users for the proc DT functions.
> Export them.
>
> Signed-off-by: Pantelis Antoniou
Actually, I cannot find the user of this patch. Why is it needed?
g.
--
To unsubscribe from this list: send the line
On Wed, 23 Jan 2013 12:58:02 +0200, Pantelis Antoniou
wrote:
> Hi David,
>
> On Jan 23, 2013, at 6:40 AM, David Gibson wrote:
> > Ok. Nonetheless it's not hard to avoid a recursive approach here.
>
> How can I find the maximum phandle value of a subtree without using recursion.
> Note that
On Fri, 4 Jan 2013 21:31:07 +0200, Pantelis Antoniou
wrote:
> There are other users for the proc DT functions.
> Export them.
>
> Signed-off-by: Pantelis Antoniou
Hi Pantelis.
Patches 1 & 2 look good. No comments there.
This patch bothers me. The manipulation of the proc entries is part
From: Lad, Prabhakar
add support for V4L2 video display to DM355 EVM.
Support for SD modes is provided, along with Composite
output
Signed-off-by: Lad, Prabhakar
---
arch/arm/mach-davinci/board-dm355-evm.c | 69 ++-
1 files changed, 68 insertions(+), 1
On Fri, Mar 15, 2013 at 04:49:42PM -0700, Ben Widawsky wrote:
> On Fri, Mar 15, 2013 at 10:06:19PM +, Chris Wilson wrote:
> > On Fri, Mar 15, 2013 at 09:36:07AM -0700, Ben Widawsky wrote:
> > > On Fri, Mar 15, 2013 at 08:24:03AM +, Chris Wilson wrote:
> > > > That's what I thought too.
From: Lad, Prabhakar
Create platform devices for various video modules like venc,osd,
vpbe and v4l2 driver for dm355.
Signed-off-by: Lad, Prabhakar
---
arch/arm/mach-davinci/board-dm355-evm.c |4 +-
arch/arm/mach-davinci/davinci.h |2 +-
arch/arm/mach-davinci/dm355.c
From: Lad, Prabhakar
This patch series enables VPBE display driver on DM355.
Changes for v5:
1: Rebased on 3.9, fix review comments pointed by Sekhar for DM365 series.
Changes for v4:
1: pass different platform names to handle different ip's.
Changes for v3:
1: Replaced obsolete preset API by
Prarit Bhargava wrote:
> The CONFIG_HPET_MMAP Kconfig option exposes the memory map of the HPET
> registers to userspace. The Kconfig help points out that in some cases this
> can be a security risk as some systems may erroneously configure the map such
> that additional data is exposed to
On Sat, Mar 16, 2013 at 5:44 AM, Anil Kumar wrote:
> Hi,
>
> I am getting kernel uImage build issue on omap2+ log[1]
>
> Taken kernel branch "for_3.10/dts" from
> https://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git
>
> Taking reference from
>
I've reviewed this set.
I hate to make people redo whole patchset sets, and I hate
re-reviewing code. Obviously, I don't really like the bunny hop
patches and I'm trying to discourage that going forward. ;P But
I wouldn't say it's a "Redo the whole thing" kind of problem.
Could just resend
On Fri, Mar 15, 2013 at 09:00:35AM -0400, Eduardo Valentin wrote:
> Because there is a need to lock inside IRQ handler, this patch
> changes the locking mechanism inside the omap-bandgap.[c,h] to
> spinlocks. Now this lock is used to protect omap_bandgap struct
> during APIs exposed (possibly used
On Thu, Mar 14, 2013 at 02:13:52PM +0100, Laurent Pinchart wrote:
> Hi Magnus,
>
> On Thursday 14 March 2013 13:23:46 Magnus Damm wrote:
> > On Wed, Mar 13, 2013 at 9:58 PM, Laurent Pinchart wrote:
> > > On Wednesday 13 March 2013 20:32:03 Magnus Damm wrote:
> > >> gpio: Renesas R-Car GPIO driver
On Fri, Mar 15, 2013 at 09:00:21AM -0400, Eduardo Valentin wrote:
> if (ret) {
> dev_err(bg_ptr->dev, "failed to read thot\n");
> - return -EIO;
> + ret = -EIO;
> + goto exit;
> }
>
> - *thot = temp;
> + *val = temp;
>
>
On Fri, Mar 15, 2013 at 09:00:13AM -0400, Eduardo Valentin wrote:
> Follow Documentation/CodingStyle while doing omap_bandgap_mcelsius_to_adc
>
I have the same response for all these bunny hop patches.
When you're reading the code and you see a goto then you assume that
it's there for a reason
On Fri, Mar 15, 2013 at 09:00:10AM -0400, Eduardo Valentin wrote:
> Follow Documentation/CodingStyle while doing omap_bandgap_adc_to_mcelsius.
Someone should probably fix CodingStyle to be more clear. That's
not what was intended at all... :/
regards,
dan carpenter
--
To unsubscribe from
Add "lowmemorykiller:" prefix to the debug print so it's easier to
analyse LMK's debug output:
dmesg | grep lowmemorykiller
Signed-off-by: Dmitry Voytik
---
drivers/staging/android/lowmemorykiller.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
On Fri, Mar 15 2013, Philip J. Kelleher wrote:
> From: Philip J Kelleher
>
> Adding in EEH support to the IBM FlashSystem 70/80 device driver.
>
> Signed-off-by: Philip J Kelleher
> ---
> Changes in v2 include:
> o
On Fri, Mar 15, 2013 at 03:08:52PM -0700, David Rientjes wrote:
> > Ick, no, please use the proper interface for this (i.e. pr_fmt).
> >
>
> And I'm sure that mysterious new "lmk:" messages appearing in the kernel
> log will be understood by about 0.1% of people.
David, Greg,
Thank you
Il 15/03/2013 18:13, Rafael J. Wysocki ha scritto:
Here's the new suspect:
f95988de06ea62ef5bd861f06e9ef56cea405ed1 is the first bad commit
commit f95988de06ea62ef5bd861f06e9ef56cea405ed1
Author: Rafael J. Wysocki
Date: Mon Jan 7 21:17:02 2013 +0100
ACPI / scan: Treat power resources
This patch allow using syscon driver from the platform data, i.e.
possibility using driver on systems without oftree support.
For search syscon device from the client drivers,
"syscon_regmap_lookup_by_pdevname" function was added.
Signed-off-by: Alexander Shiyan
Acked-by: Dong Aisheng
Acked-by:
Signed-off-by: Alexander Shiyan
Acked-by: Dong Aisheng
Acked-by: Arnd Bergmann
---
drivers/mfd/syscon.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/mfd/syscon.c b/drivers/mfd/syscon.c
index 61aea63..674af14 100644
--- a/drivers/mfd/syscon.c
+++
> On Friday 15 March 2013, Alexander Shiyan wrote:
> > > On 14 March 2013 01:34, Alexander Shiyan wrote:
> > > > This patch allow using syscon driver from the platform data, i.e.
> > > > possibility using driver on systems without oftree support.
> > > > For search syscon device from the client
From: Nishanth Menon
As per JESD209-2E specification for LPDDR2,
http://www.jedec.org/standards-documents/results/jesd209-2E
Table 73, LPDDR2 memories come in two flavors - Standard and
Extended. The Standard types can operate from -25C to +85C
However, beyond that and upto +105C can only
From: Ambresh K
Program the power management shadow register on freq update
Else the concept of threshold frequencies dont really matter
as the system always uses the performance mode timing for LP
which is programmed in at init time.
Signed-off-by: Nishanth Menon
Signed-off-by: Ambresh K
From: Nishanth Menon
Some machine or kernel variants might have missed implementation
of power off handlers. We DONOT want to let the system be in
"out of spec" state in this condition. So, WARN and attempt
a machine restart in the hopes of clearing the out-of-spec
temperature condition.
NOTE:
of_get_property returns value in Big Endian format.
Before using this value it should be converted to little endian
using be32_to_cpup().
Custom configs of emif are read from dt using of_get_property,
but these are not converted to litte endian format.
Correcting the same here.
Signed-off-by:
From: Oleksandr Dmytryshyn
The issue was that only the first timings table was added to the
emif platform data at the emif driver registration. All other
timings tables was filled with zeros. Now all emif timings table
are added to the platform data.
Signed-off-by: Oleksandr Dmytryshyn
From: Nishanth Menon
In case the custom timings provide values which overflow
the maximum possible field value, warn and use maximum
permissible value.
Signed-off-by: Nishanth Menon
Signed-off-by: Lokesh Vutla
Acked-by: Santosh Shilimkar
---
Changes since V1: No changes
From: Grygorii Strashko
ERRATA DESCRIPTION :
The EMIF supports power-down state for low power. The EMIF
automatically puts the SDRAM into power-down after the memory is
not accessed for a defined number of cycles and the
EMIF_PWR_MGMT_CTRL[10:8] REG_LP_MODE bit field is set to 0x4.
As the EMIF
The driver tries to round up the specified timeout cycles to
the next power of 2 value. This should be done defore updating
timeout variable.
Correcting this here.
Reported-by: Nishanth Menon
Signed-off-by: Lokesh Vutla
Acked-by: Santosh Shilimkar
---
Changes since V1:
Updated
This series resolves a few minor issues for EMIF driver.
Tested all patches on OMAP4430-sdp.
Patch : "memory: emif: setup LP settings on freq update"
is tested on a local tree, since freq update cannot be
tested on mainline.
Ambresh K (1):
memory: emif: setup LP settings on freq update
On Friday 15 March 2013 11:38 PM, Greg KH wrote:
On Mon, Mar 11, 2013 at 10:35:57AM +0530, Lokesh Vutla wrote:
This series resolves a few minor issues for EMIF driver.
Tested all patches on OMAP4430-sdp.
Patch : "memory: emif: setup LP settings on freq update"
is tested on a local tree, since
On Friday 15 March 2013 11:38 PM, Greg KH wrote:
On Mon, Mar 11, 2013 at 10:35:57AM +0530, Lokesh Vutla wrote:
This series resolves a few minor issues for EMIF driver.
Tested all patches on OMAP4430-sdp.
Patch : memory: emif: setup LP settings on freq update
is tested on a local tree, since
This series resolves a few minor issues for EMIF driver.
Tested all patches on OMAP4430-sdp.
Patch : memory: emif: setup LP settings on freq update
is tested on a local tree, since freq update cannot be
tested on mainline.
Ambresh K (1):
memory: emif: setup LP settings on freq update
Grygorii
The driver tries to round up the specified timeout cycles to
the next power of 2 value. This should be done defore updating
timeout variable.
Correcting this here.
Reported-by: Nishanth Menon n...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
Acked-by: Santosh Shilimkar
From: Grygorii Strashko grygorii.stras...@ti.com
ERRATA DESCRIPTION :
The EMIF supports power-down state for low power. The EMIF
automatically puts the SDRAM into power-down after the memory is
not accessed for a defined number of cycles and the
EMIF_PWR_MGMT_CTRL[10:8] REG_LP_MODE bit field is
From: Nishanth Menon n...@ti.com
In case the custom timings provide values which overflow
the maximum possible field value, warn and use maximum
permissible value.
Signed-off-by: Nishanth Menon n...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
Acked-by: Santosh Shilimkar
From: Oleksandr Dmytryshyn oleksandr.dmytrys...@ti.com
The issue was that only the first timings table was added to the
emif platform data at the emif driver registration. All other
timings tables was filled with zeros. Now all emif timings table
are added to the platform data.
Signed-off-by:
of_get_property returns value in Big Endian format.
Before using this value it should be converted to little endian
using be32_to_cpup().
Custom configs of emif are read from dt using of_get_property,
but these are not converted to litte endian format.
Correcting the same here.
Signed-off-by:
From: Nishanth Menon n...@ti.com
Some machine or kernel variants might have missed implementation
of power off handlers. We DONOT want to let the system be in
out of spec state in this condition. So, WARN and attempt
a machine restart in the hopes of clearing the out-of-spec
temperature
From: Nishanth Menon n...@ti.com
As per JESD209-2E specification for LPDDR2,
http://www.jedec.org/standards-documents/results/jesd209-2E
Table 73, LPDDR2 memories come in two flavors - Standard and
Extended. The Standard types can operate from -25C to +85C
However, beyond that and upto
From: Ambresh K ambr...@ti.com
Program the power management shadow register on freq update
Else the concept of threshold frequencies dont really matter
as the system always uses the performance mode timing for LP
which is programmed in at init time.
Signed-off-by: Nishanth Menon n...@ti.com
On Friday 15 March 2013, Alexander Shiyan wrote:
On 14 March 2013 01:34, Alexander Shiyan shc_w...@mail.ru wrote:
This patch allow using syscon driver from the platform data, i.e.
possibility using driver on systems without oftree support.
For search syscon device from the client
This patch allow using syscon driver from the platform data, i.e.
possibility using driver on systems without oftree support.
For search syscon device from the client drivers,
syscon_regmap_lookup_by_pdevname function was added.
Signed-off-by: Alexander Shiyan shc_w...@mail.ru
Acked-by: Dong
Signed-off-by: Alexander Shiyan shc_w...@mail.ru
Acked-by: Dong Aisheng dong.aish...@linaro.org
Acked-by: Arnd Bergmann a...@arndb.de
---
drivers/mfd/syscon.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/mfd/syscon.c b/drivers/mfd/syscon.c
index
Il 15/03/2013 18:13, Rafael J. Wysocki ha scritto:
Here's the new suspect:
f95988de06ea62ef5bd861f06e9ef56cea405ed1 is the first bad commit
commit f95988de06ea62ef5bd861f06e9ef56cea405ed1
Author: Rafael J. Wysocki rafael.j.wyso...@intel.com
Date: Mon Jan 7 21:17:02 2013 +0100
ACPI /
On Fri, Mar 15, 2013 at 03:08:52PM -0700, David Rientjes wrote:
Ick, no, please use the proper interface for this (i.e. pr_fmt).
And I'm sure that mysterious new lmk: messages appearing in the kernel
log will be understood by about 0.1% of people.
David, Greg,
Thank you for fair
On Fri, Mar 15 2013, Philip J. Kelleher wrote:
From: Philip J Kelleher pjk1...@linux.vnet.ibm.com
Adding in EEH support to the IBM FlashSystem 70/80 device driver.
Signed-off-by: Philip J Kelleher pjk1...@linux.vnet.ibm.com
Add lowmemorykiller: prefix to the debug print so it's easier to
analyse LMK's debug output:
dmesg | grep lowmemorykiller
Signed-off-by: Dmitry Voytik dvv.ker...@gmail.com
---
drivers/staging/android/lowmemorykiller.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
On Fri, Mar 15, 2013 at 09:00:10AM -0400, Eduardo Valentin wrote:
Follow Documentation/CodingStyle while doing omap_bandgap_adc_to_mcelsius.
Someone should probably fix CodingStyle to be more clear. That's
not what was intended at all... :/
regards,
dan carpenter
--
To unsubscribe from this
On Fri, Mar 15, 2013 at 09:00:13AM -0400, Eduardo Valentin wrote:
Follow Documentation/CodingStyle while doing omap_bandgap_mcelsius_to_adc
I have the same response for all these bunny hop patches.
When you're reading the code and you see a goto then you assume that
it's there for a reason so
On Fri, Mar 15, 2013 at 09:00:21AM -0400, Eduardo Valentin wrote:
if (ret) {
dev_err(bg_ptr-dev, failed to read thot\n);
- return -EIO;
+ ret = -EIO;
+ goto exit;
}
- *thot = temp;
+ *val = temp;
+exit:
On Thu, Mar 14, 2013 at 02:13:52PM +0100, Laurent Pinchart wrote:
Hi Magnus,
On Thursday 14 March 2013 13:23:46 Magnus Damm wrote:
On Wed, Mar 13, 2013 at 9:58 PM, Laurent Pinchart wrote:
On Wednesday 13 March 2013 20:32:03 Magnus Damm wrote:
gpio: Renesas R-Car GPIO driver update
On Fri, Mar 15, 2013 at 09:00:35AM -0400, Eduardo Valentin wrote:
Because there is a need to lock inside IRQ handler, this patch
changes the locking mechanism inside the omap-bandgap.[c,h] to
spinlocks. Now this lock is used to protect omap_bandgap struct
during APIs exposed (possibly used in
101 - 200 of 356 matches
Mail list logo
