Hello,
We are working on board based on Freescale MPC8313ERDB. We have ported linux
3.0.46 kernel on it. In one of device driver written by us, we need to take
some action upon asserting IRQ0 interrupt. For this we have written interrupt
handler which takes care of this. We are able register in
The DSCR (aka Data Stream Control Register) is supported on some
server PowerPC chips and allow some control over the prefetch
of data streams.
The kernel already supports DSCR value per thread but there is also
a need in a ability to change it from an external process for
the specific pid.
The p
Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> arch/powerpc/kernel/kgdb.c: In function 'kgdb_arch_exit':
> arch/powerpc/kernel/kgdb.c:492:2: error: '__debugger_breakx_match' undeclared
> (first use in
> -Original Message-
> From: Wood Scott-B07421
> Sent: Friday, January 11, 2013 1:19 AM
> To: Singh Sandeep-B37400
> Cc: Wood Scott-B07421; devicetree-disc...@lists.ozlabs.org; linuxppc-
> d...@ozlabs.org; Aggrwal Poonam-B10812
> Subject: Re: [PATCH] Added device tree binding for TDM and TD
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
arch/powerpc/kernel/kgdb.c: In function 'kgdb_arch_exit':
arch/powerpc/kernel/kgdb.c:492:2: error: '__debugger_breakx_match' undeclared
(first use in this function)
Caused by commit 9422de3e9
The DSCR (aka Data Stream Control Register) is supported on some
server PowerPC chips and allow some control over the prefetch
of data streams.
The kernel already supports DSCR value per thread but there is also
a need in a ability to change it from an external process for
the specific pid.
The p
> > >
> > > Some recent patch has caused fsl_mxc_udc.c driver to fail compilation
> > > because it can't find anymore.
> > >
> > > I would like this to be fixed still during this -rc cycle.
> >
> > Me too, who's sending a patch? :)
>
> Hi Peter,
>
> Who is currently working on the i.mx USB?
>
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, January 10, 2013 10:30 PM
> To: Felipe Balbi
> Cc: Li Yang-R58472; linux-...@vger.kernel.org; linuxppc-
> d...@lists.ozlabs.org
> Subject: Re: [BUILD BREAK] usb: gadget: fsl_mxc_udc can't compile on
>
Currently we are getting:
arch/powerpc/kernel/kgdb.c: In function 'kgdb_arch_exit':
arch/powerpc/kernel/kgdb.c:492:2: error: '__debugger_breakx_match' undeclared
(first use in this function)
arch/powerpc/kernel/kgdb.c:492:2: note: each undeclared identifier is reported
only once for each func
On Thu, Jan 10, 2013 at 06:30:06AM -0800, Greg KH wrote:
> On Thu, Jan 10, 2013 at 12:08:35PM +0200, Felipe Balbi wrote:
> > Hi,
> >
> > Some recent patch has caused fsl_mxc_udc.c driver to fail compilation
> > because it can't find anymore.
> >
> > I would like this to be fixed still during thi
With allmodconfig we are getting:
drivers/tty/synclink_gt.c:160:12: error: conflicting types for 'set_break'
arch/powerpc/include/asm/debug.h:49:5: note: previous declaration of
'set_break' was here
drivers/tty/synclinkmp.c:526:12: error: conflicting types for 'set_break'
arch/powerpc/inc
Added memory hotplug handlers. mm_add_execute() onlines requested
memory ranges for hot-add & online operations, and mm_del_execute()
offlines them for hot-delete & offline operations. They are also
used for rollback as well.
mm_del_validate() fails a hot-delete request if a requested memory
ran
This patchset is a prototype of proposed system device hot-plug framework
for design review. Unlike other hot-plug environments, such as USB and
PCI, there is no common framework for system device hot-plug [1].
Therefore, this patchset is designed to provide a common framework for
hot-plugging and
Changed store_online() to request a cpu online or offline
operation by calling shp_submit_req(). It sets a target cpu
device information with shp_add_dev_info() for the request.
Signed-off-by: Toshi Kani
---
drivers/base/cpu.c | 40
1 file changed, 28
Added cpu hotplug handlers. cpu_add_execute() onlines requested
cpus for hot-add & online operations, and cpu_del_execute()
offlines them for hot-delete & offline operations. They are
also used for rollback as well.
cpu_del_validate() fails a request if cpu0 is requested to delete.
Signed-off-b
Added sys_hotplug.c, which is the system device hotplug framework code.
shp_register_handler() allows modules to register their hotplug handlers
to the framework. shp_submit_req() provides the interface to submit
a hotplug or online/offline request of system devices. The request is
then put into
Added ACPI resource handler for hotplug operations. The handler,
acpi_set_shp_device(), sets device resource information to a hotplug
request, which is consumed by the CPU and memory handlers.
For setting the device resource information, acpi_scan_shp_devices()
walks the acpi_device tree from a ta
Added ACPI bus hotplug handlers. acpi_add_execute() calls
acpi_bus_add() to construct new acpi_device objects for hot-add
operation, and acpi_del_execute() calls acpi_bus_trim() to destruct
them for hot-delete operation. They are also used for rollback
as well.
acpi_del_commit() calls _EJ0 to ej
Added include/linux/sys_hotplug.h, which defines the system device
hotplug framework interfaces used by the framework itself and
handlers.
The order values define the calling sequence of handlers. For add
execute, the ordering is ACPI->MEM->CPU. Memory is onlined before
CPU so that threads on ne
Added acpi_processor_resource() for the .resource() interface,
which sets CPU information to a hotplug request.
Changed acpi_processor_hotplug_notify() to request a hotplug
operation by calling shp_submit_req(). It no longer initiates
hot-add or hot-delete operation by calling acpi_bus_add() or
a
Added include/acpi/sys_hotplug.h, which is ACPI-specific system
device hotplug header and defines the order values of ACPI-specific
handlers.
Signed-off-by: Toshi Kani
---
include/acpi/sys_hotplug.h | 48
1 file changed, 48 insertions(+)
create mod
Changed container_notify_cb() to request a hotplug operation by
calling shp_submit_req(). It no longer initiates hot-add by calling
acpi_bus_add(). Also, it no longer sets device->flags.eject_pending
and generates KOBJ_OFFLINE event for hot-delete.
Signed-off-by: Toshi Kani
---
drivers/acpi/co
Changed acpi_eject_store() to request a hot-delete operation by
calling shp_submit_req(). It no longer initiates a hot-delete
operation by calling acpi_bus_hot_remove_device().
Deleted acpi_bus_hot_remove_device() since it no longer has any
caller and should not be called for hot-delete.
Deleted
Changed acpi_memory_device_notify() to request a hotplug operation
by calling shp_submit_req(). It no longer initiates hot-add or
hot-delete operation by calling add_memory() or remove_memory()
directly. Removed the enabled and failed flags from acpi_memory_info
since they are no longer used.
Ch
On Thu, 2013-01-10 at 13:07 +0100, Thomas Waldecker wrote:
> ppc -> powerpc
I think I already applied something like that in powerpc -next, can you
dbl check ?
Cheers,
Ben.
> Signed-off-by: Thomas Waldecker
> ---
> Documentation/powerpc/cpu_features.txt | 10 +-
> 1 file changed, 5 ins
On 01/10/2013 03:24:21 AM, Singh Sandeep-B37400 wrote:
> > > +- compatible
> > > +Value type:
> > > +Definition: Should contain generic compatibility like
> > "tdm-phy-slic"
> > > or
> > > +"tdm-phy-e1" or "tdm-phy-t1".
>
> Does this "generic" string (plus the other properties) tell
Signed-off-by: Thadeu Lima de Souza Cascardo
---
v2:
Remove the unneeded extra variable i, which caused build failure.
---
arch/powerpc/kernel/iommu.c |9 ++---
1 files changed, 2 insertions(+), 7 deletions(-)
diff --git a/arch/powerpc/kernel/iommu.c b/arch/powerpc/kernel/iommu.c
index 6
On Thu, 2013-01-10 at 16:48 +1100, Benjamin Herrenschmidt wrote:
> On Thu, 2012-12-13 at 11:58 +, Arnd Bergmann wrote:
> > On Wednesday 12 December 2012, Joe Perches wrote:
> > > Use the new vsprintf extension to avoid any possible
> > > message interleaving.
> > >
> > > Convert the #ifdef DEB
On Thu, Jan 10, 2013 at 12:08:35PM +0200, Felipe Balbi wrote:
> Hi,
>
> Some recent patch has caused fsl_mxc_udc.c driver to fail compilation
> because it can't find anymore.
>
> I would like this to be fixed still during this -rc cycle.
Me too, who's sending a patch? :)
_
ppc -> powerpc
Signed-off-by: Thomas Waldecker
---
Documentation/powerpc/cpu_features.txt | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/powerpc/cpu_features.txt
b/Documentation/powerpc/cpu_features.txt
index ffa4183..ae09df8 100644
--- a/Documentat
Hi Benjamin,
FYI, kernel build failed on
tree: git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc.git next
head: 61383407677aef05928541a00678591abea2d84c
config: make ARCH=powerpc allmodconfig
All error/warnings:
WARNING: arch/powerpc/mm/built-in.o(.cpuinit.text+0x292): Section mis
Hi,
Some recent patch has caused fsl_mxc_udc.c driver to fail compilation
because it can't find anymore.
I would like this to be fixed still during this -rc cycle.
Thank you
--
balbi
signature.asc
Description: Digital signature
___
Linuxppc-dev ma
> -Original Message-
> From: Wood Scott-B07421
> Sent: Thursday, January 10, 2013 5:37 AM
> To: Singh Sandeep-B37400
> Cc: devicetree-disc...@lists.ozlabs.org; linuxppc-...@ozlabs.org; Aggrwal
> Poonam-B10812
> Subject: Re: [PATCH] Added device tree binding for TDM and TDM phy
>
> On 01/09
Use local_paca directly in arch_spin_unlock_wait(), as all processors have the
same value for the field shared_proc, so we don't need care racy here.
Reported-by: Paul E. McKenney
Signed-off-by: Li Zhong
---
arch/powerpc/lib/locks.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
(2013/01/10 17:36), Glauber Costa wrote:
BTW, shrink_slab() is now node/zone aware ? If not, fixing that first will
be better direction I guess.
It is not upstream, but there are patches for this that I am already
using in my private tree.
Oh, I see. If it's merged, it's worth add "shrink_
> If it's configure as ZONE_NORMAL, you need to pray for offlining memory.
>
> AFAIK, IBM's ppc? has 16MB section size. So, some of sections can be
> offlined
> even if they are configured as ZONE_NORMAL. For them, placement of offlined
> memory is not important because it's virtualized by LPAR,
(2013/01/10 16:55), Glauber Costa wrote:
On 01/10/2013 11:31 AM, Kamezawa Hiroyuki wrote:
(2013/01/10 16:14), Glauber Costa wrote:
On 01/10/2013 06:17 AM, Tang Chen wrote:
Note: if the memory provided by the memory device is used by the
kernel, it
can't be offlined. It is not a bug.
Right.
37 matches
Mail list logo
