On Mon, Aug 2, 2010 at 1:52 AM, Mingkai Hu wrote:
> Signed-off-by: Mingkai Hu
> ---
>
> v2:
> - Move the flash partition function from of_spi.c to MTD driver
>
> drivers/mtd/devices/m25p80.c | 29 +
> 1 files changed, 29 insertions(+), 0 deletions(-)
>
> diff --git
On Mon, Aug 2, 2010 at 1:52 AM, Mingkai Hu wrote:
> Add eSPI controller support based on the library code spi_fsl_lib.c.
>
> The eSPI controller is newer controller 85xx/Pxxx devices supported.
> There're some differences comparing to the SPI controller:
>
> 1. Has different register map and diffe
On Mon, Aug 2, 2010 at 1:51 AM, Mingkai Hu wrote:
> Refactor the common code in file spi_mpc8xxx.c to spi_fsl_lib.c
> used by SPI/eSPI controller driver as a library, move the SPI
> controller driver to a new file spi_fsl_spi.c, and leave the
> QE/CPM SPI controller code in this file.
>
> Because
>>> I've avoided requiring clock nodes to have a separate sub node for
>>> each output because it is more verbose and it prevents clock
>>> providers from having child nodes for other purposes. Are you
>>> concerned that
>>
>> I don't see why there should be child nodes for other purposes under
>c
On Mon, Aug 9, 2010 at 10:56 PM, Li Yang-R58472 wrote:
I've avoided requiring clock nodes to have a separate sub node for
each output because it is more verbose and it prevents clock
providers from having child nodes for other purposes. Are you
concerned that
>>>
>>> I don't s
On Tue, 2010-08-10 at 10:39 +0800, Terren Chow wrote:
> Hi Ben:
> I'm not quite clearly know about the powerpc kernel tree histroy.
> why the tags in the powerpc kernel tree are only update to 2.6.26-rc9
> at about 2 years ago?
Not sure what you're looking at but your shouldn't need to use t
Hi Ben:
I'm not quite clearly know about the powerpc kernel tree histroy. why
the tags in the powerpc kernel tree are only update to 2.6.26-rc9 at about 2
years ago?
--
Terren Chow
College of informatics, SCAU
Graduate student
Lab of Embedded System and Wireless Sensor Network
MSN: terren.c..
>> Reading the fsl i2c bindings in the documentation, I found an example
>> as follows.
>> 27 ...@860 {
>> 28 compatible = "fsl,mpc823-i2c",
>> 29 "fsl,cpm1-i2c";
>> 30 reg = <0x860 0x20 0x3c80 0x30>;
>> 31 inte
On Monday, August 09, 2010 01:44:37 pm Nishanth Aravamudan wrote:
> On Monday, August 09, 2010 11:43:46 am Nathan Fontenot wrote:
> > Update the memory hotplug documentation to reflect the new behaviors of
> > memory blocks reflected in sysfs.
>
>
>
> > Index: linux-2.6/Documentation/memory-hotp
On Monday, August 09, 2010 11:43:46 am Nathan Fontenot wrote:
> Update the memory hotplug documentation to reflect the new behaviors of
> memory blocks reflected in sysfs.
> Index: linux-2.6/Documentation/memory-hotplug.txt
> ===
>
Update the memory hotplug documentation to reflect the new behaviors of
memory blocks reflected in sysfs.
Signed-off-by: Nathan Fontent
---
Documentation/memory-hotplug.txt | 46 +--
1 file changed, 30 insertions(+), 16 deletions(-)
Index: linux-2.6/Docume
Define a version of memory_block_size_bytes() for powerpc/pseries such that
a memory block spans an entire lmb.
Signed-off-by: Nathan Fontenot
---
arch/powerpc/platforms/pseries/hotplug-memory.c | 66 +++-
1 file changed, 53 insertions(+), 13 deletions(-)
Index: linux-2.6
Update the node sysfs code to be aware of the new capability for a memory
block to contain multiple memory sections. This requires an additional
parameter to unregister_mem_sect_under_nodes so that we know which memory
section of the memory block to unregister.
Signed-off-by: Nathan Fontenot
--
Update the memory sysfs code that each sysfs memory directory is now
considered a memory block that can contain multiple memory sections per
memory block. The default size of each memory block is SECTION_SIZE_BITS
to maintain the current behavior of having a single memory section per
memory block
Add a new mutex for use in adding and removing of memory blocks. This
is needed to avoid any race conditions in which the same memory block could
be added and removed at the same time.
Signed-off-by: Nathan Fontenot
---
drivers/base/memory.c |7 +++
1 file changed, 7 insertions(+)
Ind
2010/8/3 Roy Zang :
[...]
> @@ -240,6 +240,8 @@ struct sdhci_host {
> #define SDHCI_QUIRK_CAP_CLOCK_BASE_BROKEN (1<<25)
> /* Controller cannot support End Attribute in NOP ADMA descriptor */
> #define SDHCI_QUIRK_NO_ENDATTR_IN_NOPDESC (1<<26)
> +/* Controller uses Auto
Add a section count property to the memory_block struct to track the number
of memory sections that have been added/removed from a memory block. This
alolws us to know when the lasat memory section of a memory block has been
removed so we can remove the memory block.
Signed-off-by: Nathan Fontenot
Update the 'phys_index' properties of a memory block to include a
'start_phys_index' which is the same as the current 'phys_index' property.
The property still appears as 'phys_index' in sysfs but the memory_block
struct name is updated to indicate the start and end values.
This also adds an 'end_p
Move the find_me mory_block() routine up to avoid needing a forward
declaration in subsequent patches.
Signed-off-by: Nathan Fontenot
---
drivers/base/memory.c | 62 +-
1 file changed, 31 insertions(+), 31 deletions(-)
Index: linux-2.6/drivers/
This set of patches de-couples the idea that there is a single
directory in sysfs for each memory section. The intent of the
patches is to reduce the number of sysfs directories created to
resolve a boot-time performance issue. On very large systems
boot time are getting very long (as seen on pow
On Wed, Aug 04, 2010 at 07:02:56PM -0600, Grant Likely wrote:
> On Mon, Aug 2, 2010 at 9:11 PM, Roy Zang wrote:
> > From: Jerry Huang
> >
> > Add auto CMD12 command support for eSDHC driver.
> > This is needed by P4080 and P1022 for block read/write.
> > Manual asynchronous CMD12 abort operation
On Tue, Aug 03, 2010 at 11:11:11AM +0800, Roy Zang wrote:
> Signed-off-by: Roy Zang
> ---
> Documentation/powerpc/dts-bindings/fsl/esdhc.txt |2 ++
> arch/powerpc/boot/dts/p4080ds.dts|1 +
> 2 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/p
On Tue, Aug 03, 2010 at 11:11:12AM +0800, Roy Zang wrote:
> P4080 ESDHC controller does not support 1.8V and 3.0V voltage. but the
> host controller capabilities register wrongly set the bits.
> This patch adds the workaround to correct the weird voltage setting bits.
> Only 3.3V voltage is support
On Sun, 8 Aug 2010 23:37:00 -0700
Shawn Jin wrote:
> Reading the fsl i2c bindings in the documentation, I found an example
> as follows.
> 27 i...@860 {
> 28compatible = "fsl,mpc823-i2c",
> 29 "fsl,cpm1-i2c";
> 30reg = <0x86
On Mon, Aug 02, 2010 at 02:22:12PM +0530, Subrata Modak wrote:
> Hi,
>
> The following suspicious rcu_dereference_check() usage is detected
> during 2.6.35-stable boot on my ppc64/p7 machine:
>
> ==
> [ INFO: suspicious rcu_dereference_check() usage
On 08/04/2010 11:59 PM, KAMEZAWA Hiroyuki wrote:
> On Tue, 03 Aug 2010 08:41:45 -0500
> Nathan Fontenot wrote:
>
>> Update the find_memory_block declaration to to take a struct mem_section *
>> so that it matches the definition.
>>
>> Signed-off-by: Nathan Fontenot
>
> Acked-by: KAMEZAWA Hiroyu
On 08/04/2010 11:53 PM, KAMEZAWA Hiroyuki wrote:
> On Tue, 03 Aug 2010 08:39:50 -0500
> Nathan Fontenot wrote:
>
>> Add a new mutex for use in adding and removing of memory blocks. This
>> is needed to avoid any race conditions in which the same memory block could
>> be added and removed at the
Hi Kumar,
05.08.2010 12:02, Kumar Gala wrote:
The following commit broke 83xx because it assumed the 83xx platforms
exposed the "IMMR" address in BAR0 like the 85xx/86xx/QoriQ devices do:
commit 3da34aae03d498ee62f75aa7467de93cce3030fd
Author: Kumar Gala
Date: Tue May 12 15:51:56 2009 -0500
Hi Kumar,
05.08.2010 12:02, Kumar Gala wrote:
The following commit broke 83xx because it assumed the 83xx platforms
exposed the "IMMR" address in BAR0 like the 85xx/86xx/QoriQ devices do:
commit 3da34aae03d498ee62f75aa7467de93cce3030fd
Author: Kumar Gala
Date: Tue May 12 15:51:56 2009 -0500
On Sun, 2010-08-08 at 23:18 -0600, Grant Likely wrote:
> And how is anyone else to make it into the kernel statistics top
> contributors by lines changed list with stuff like this going in? :-)
lindent ? :-)
Cheers,
Ben.
___
Linuxppc-dev mailing list
> -Original Message-
> From: Zang Roy-R61911
> Sent: Friday, August 06, 2010 10:52 AM
> To: linux-...@lists.infradead.org
> Cc: linuxppc-...@ozlabs.org; a...@linux-foundation.org; Gala
> Kumar-B11780; Lan Chunhe-B25806
> Subject: [PATCH 1/3][MTD] P4080/eLBC: Make Freescale elbc
> inte
>>>*-clock is named for the signal name for the ''clock input''
>>>of the device. it should describe the function of the signal for that
>>>device, rather than the name of the system-wide clock line. For
>>>example, a UART with two clocks - one for baud-rate clocking, and the
>>>other for register
On Mon, Aug 9, 2010 at 1:05 AM, Li Yang-R58472 wrote:
*-clock is named for the signal name for the ''clock input''
of the device. it should describe the function of the signal for that
device, rather than the name of the system-wide clock line. For
example, a UART with two clocks -
33 matches
Mail list logo
