Hi,
I have been facing problem with ibm_newemac driver (v3.54).
The board gets disconnected and can not be pinged in between
some heavy network traffic. In my case I am running IOmeter
"All-in-One" 8 threads on the iSCSI target. MTU is 4088.
I found that after executing emac_full_tx_reset(), the b
Hi Linus !
Here are a few fixes remaining for powerpc in 3.2. Some tiny build
breakage, a couple of nasty ps3 bugs fixes, other very small and
quite obvious fixes and and a long standing issue with atomics &
ordering for which we have to use stronger barriers than we do to
be correct.
Cheers,
Ben
Ok and I want to add another patch before 3/3.
-LiuShuo
On Tue, 2011-11-15 at 17:29 +0800, b35...@freescale.com wrote:
From: Liu Shuo
If we use the Nand flash chip whose number of pages in a block is greater
than 64(for large page), we must treat the low bit of FBAR as being the
high bit of th
On 17.11.11 22:27:46, Joakim Tjernlund wrote:
> > >> For my e300c2 cpu both if's are false and I don't get support for
> > >> callgraph/backtrace
> > >> support. Moving the ops->backtrace = op_powerpc_backtrace; to the top
> > >> enables backtrace for me.
> It sure seems to work :)
Backtrace sup
On Thu, Nov 17, 2011 at 04:28:48PM -0600, Timur Tabi wrote:
> Scott Wood wrote:
>
> > As we discussed earlier, you could have a kernel boot parameter that
> > indicates what mode you'd like the localbus to run in. Then, platform
> > code could update the device tree before any drivers bind.
>
>
Scott Wood wrote:
> As we discussed earlier, you could have a kernel boot parameter that
> indicates what mode you'd like the localbus to run in. Then, platform
> code could update the device tree before any drivers bind.
How do I update the device tree from platform code?
> Or, have U-boot set
On Thu, Nov 17, 2011 at 04:12:02PM -0600, Timur Tabi wrote:
> Scott Wood wrote:
>
> >> This has the side-effect of no longer requiring U-Boot to enable the DIU.
> >> Now Linux can enable the DIU all by itself.
> >
> > Under what circumstances does Linux do this?
>
> p1022ds_set_monitor_port()
On Tue, 2011-11-15 at 17:29 +0800, b35...@freescale.com wrote:
> From: Liu Shuo
>
> If we use the Nand flash chip whose number of pages in a block is greater
> than 64(for large page), we must treat the low bit of FBAR as being the
> high bit of the page address due to the limitation of FCM, it s
Scott Wood wrote:
>> This has the side-effect of no longer requiring U-Boot to enable the DIU.
>> Now Linux can enable the DIU all by itself.
>
> Under what circumstances does Linux do this?
p1022ds_set_monitor_port() is called by the DIU driver when it enables the DIU.
This happens on boot,
Stephen Rothwell wrote:
>> static void p1022ds_set_monitor_port(enum fsl_diu_monitor_port port)
>> {
>> -struct device_node *np;
>> -void __iomem *pixis;
>> -u8 __iomem *brdcfg1;
>> +struct device_node *guts_node = NULL;
>
> There is no point in initialising this as it is assign
On Tue, 2011-11-15 at 17:29 +0800, b35...@freescale.com wrote:
> From: Liu Shuo
>
> fix whitespaces,tabs coding style issue and use #include instead
> of
> in drivers/mtd/nand/fsl_elbc.c.
>
> Signed-off-by: Liu Shuo
> Signed-off-by: Li Yang
Hi, It is really matter of taste whether to use o
From: Wolfgang Grandegger
Date: Thu, 17 Nov 2011 14:06:44 +0100
> The re-binding (unbind..bind) of an EMAC device fails because the
> static variable "busy_phy_map" is not updated when the device is
> removed.
>
> Signed-off-by: Wolfgang Grandegger
Applied, thanks.
On Thu, Nov 17, 2011 at 12:57:38PM -0600, Timur Tabi wrote:
> The Freescale P1022 has a unique pin muxing "feature" where the DIU video
> controller's video signals are muxed with 24 of the local bus address signals.
> When the DIU is enabled, the bulk of the local bus is disabled, preventing
> acc
On Thu, Nov 17, 2011 at 12:57:39PM -0600, Timur Tabi wrote:
> When the P1022's DIU video controller is active, the pixis must be accessed
> in "indirect" mode, which uses localbus chip select addresses.
>
> Switching between the DVI and LVDS monitor ports is handled by the pixis,
> so that switchi
On Thu, Nov 17, 2011 at 09:56:18PM +0400, Dmitry Eremin-Solenikov wrote:
> All mpc85xx boards deal with MPIC initialization in more or less the
> same way. The only difrerences are some flags (WANTS_RESET,
> BROKEN_FRR_NIRQS, SINGLE_DEST_CPU), and some bugs like leaking device
> node counter, etc.
Hi Timur,
On Thu, 17 Nov 2011 12:57:39 -0600 Timur Tabi wrote:
>
> @@ -129,44 +144,117 @@ static void p1022ds_set_gamma_table(enum
> fsl_diu_monitor_port port,
> */
> static void p1022ds_set_monitor_port(enum fsl_diu_monitor_port port)
> {
> - struct device_node *np;
> - void __iomem
Andy Fleming wrote on 2011/11/17 18:51:52:
>
>
> On Nov 17, 2011, at 11:30 AM, Maynard Johnson wrote:
>
> >>
> >> Notice the first
> >>if (!cur_cpu_spec->oprofile_cpu_type)
> >> return -ENODEV;
> >>
> >>if (firmware_has_feature(FW_FEATURE_ISERIES))
> >>
Hi Dmitry,
On Thu, 17 Nov 2011 21:56:21 +0400 Dmitry Eremin-Solenikov
wrote:
>
> Drop lots of unused headers after board files merge/splitup
Again, I am concerned that you may have removed too many includes (though
I didn't explicitly check this time).
In general, these clean ups look great.
Hi Dmitry,
On Thu, 17 Nov 2011 22:43:35 +0400 Dmitry Eremin-Solenikov
wrote:
>
> On 11/17/2011 10:30 PM, Lee Nipper wrote:
> > On Thu, Nov 17, 2011 at 11:56 AM, Dmitry Eremin-Solenikov
> > wrote:
> >> All mpc85xx boards deal with MPIC initialization in more or less the
> >> same way. The only
Hi Dmitry,
On Thu, 17 Nov 2011 18:48:49 +0400 Dmitry Eremin-Solenikov
wrote:
>
> Drop lots of unused headers after board files merge/splitup
Please inly drop include files if nothing in them is actually used. You
need to do this by inspection, not by compilation testing. The problem
is that i
On Thu, Nov 17, 2011 at 01:16:00AM -0600, Kumar Gala wrote:
> Utilize new split between board & SoC, and new SoC device trees split
> into pre & post utilizing 'template' includes for SoC IP blocks.
>
> Other changes include:
> * Moved to specifying interrupt-parent for mpic at root
> * Moved to 4
On 11/17/2011 2:38 AM, Joakim Tjernlund wrote:
arch/powerpc/oprofile/common.c has this init code:
int __init oprofile_arch_init(struct oprofile_operations *ops)
{
if (!cur_cpu_spec->oprofile_cpu_type)
return -ENODEV;
if (firmwa
On Thu, Nov 17, 2011 at 07:53:22PM +0800, Zhao Chenhui wrote:
> On Wed, Nov 16, 2011 at 06:17:56PM -0600, Scott Wood wrote:
> > On 11/16/2011 03:55 AM, Zhao Chenhui wrote:
> > > + local_irq_save(flags);
> > > + /*
> > > + * A Jog request can not be asserted when any core is in a low power
> > > +
On Thu, Nov 17, 2011 at 05:16:09AM -0600, Li Yang-R58472 wrote:
>
>
> >Cc: linuxppc-dev@lists.ozlabs.org; Li Yang-R58472
> >Subject: Re: [PATCH v2 2/7] powerpc/85xx: add HOTPLUG_CPU support
> >
> >On 11/16/2011 03:55 AM, Zhao Chenhui wrote:
> >> +static void __cpuinit smp_85xx_mach_cpu_die(void)
On (Fri) 11 Nov 2011 [14:57:20], Rusty Russell wrote:
> On Tue, 08 Nov 2011 13:44:58 -0800, Miche Baker-Harvey
> wrote:
> > Some modifications of vtermno were not done under the spinlock.
> >
> > Moved assignment from vtermno and increment of vtermno together,
> > putting both under the spinlock
When the P1022's DIU video controller is active, the pixis must be accessed
in "indirect" mode, which uses localbus chip select addresses.
Switching between the DVI and LVDS monitor ports is handled by the pixis,
so that switching needs to be done via indirect mode.
This has the side-effect of no
The Freescale P1022 has a unique pin muxing "feature" where the DIU video
controller's video signals are muxed with 24 of the local bus address signals.
When the DIU is enabled, the bulk of the local bus is disabled, preventing
access to memory-mapped devices like NOR flash and the pixis FPGA.
In
Rusty, Michael, Stephen, et al,
Thanks for your comments on these patches.
For what I'm trying to do, all three patches are necessary, but maybe
I'm going about it the wrong way. Your input would be appreciated.
I'm in no way claiming that these patches are "right", just that it's
working for me,
On 11/17/2011 10:30 PM, Lee Nipper wrote:
On Thu, Nov 17, 2011 at 11:56 AM, Dmitry Eremin-Solenikov
wrote:
All mpc85xx boards deal with MPIC initialization in more or less the
same way. The only difrerences are some flags (WANTS_RESET,
BROKEN_FRR_NIRQS, SINGLE_DEST_CPU), and some bugs like lea
On Thu, Nov 17, 2011 at 11:56 AM, Dmitry Eremin-Solenikov
wrote:
> All mpc85xx boards deal with MPIC initialization in more or less the
> same way. The only difrerences are some flags (WANTS_RESET,
> BROKEN_FRR_NIRQS, SINGLE_DEST_CPU), and some bugs like leaking device
> node counter, etc. To mini
Signed-off-by: Dmitry Eremin-Solenikov
---
arch/powerpc/platforms/85xx/mpc85xx.h|4 +++
arch/powerpc/platforms/85xx/mpc85xx_cds.c| 25 +-
arch/powerpc/platforms/85xx/mpc85xx_common.c | 36 ++
arch/powerpc/platforms/85xx/mpc85xx_ds.c
Drop lots of unused headers after board files merge/splitup
Signed-off-by: Dmitry Eremin-Solenikov
---
arch/powerpc/platforms/85xx/corenet_ds.c | 17 ---
arch/powerpc/platforms/85xx/ksi8560.c | 16 ---
arch/powerpc/platforms/85xx/mpc8536_ds.c | 13
All mpc85xx boards deal with MPIC initialization in more or less the
same way. The only difrerences are some flags (WANTS_RESET,
BROKEN_FRR_NIRQS, SINGLE_DEST_CPU), and some bugs like leaking device
node counter, etc. To minimize problems, switch all boards to use one
single instance of code.
Sign
Refactor PCI, SWIOTLB and SMP handling out of board-specific setup_arch
functions. These tasks are more or less common to all boards and thus
can be moved to common place.
Signed-off-by: Dmitry Eremin-Solenikov
---
arch/powerpc/platforms/85xx/corenet_ds.c | 37 +--
arch/pow
85xx board files have a lot of duplication in *_publish_devices()/
*_declare_of_platform_devices() functions. Merge that into a single
function common to most of the boards.
Signed-off-by: Dmitry Eremin-Solenikov
---
arch/powerpc/platforms/85xx/ksi8560.c| 17 +-
arch/powerpc/pl
Separate handling of CPM2 PIC initialization to mpc85xx_cpm2_pic_init()
function.
Signed-off-by: Dmitry Eremin-Solenikov
---
arch/powerpc/platforms/85xx/Makefile |2 +
arch/powerpc/platforms/85xx/ksi8560.c| 29 +--
arch/powerpc/platforms/85xx/mpc8536_ds.c |
On Nov 17, 2011, at 11:30 AM, Maynard Johnson wrote:
>>
>> Notice the first
>> if (!cur_cpu_spec->oprofile_cpu_type)
>> return -ENODEV;
>>
>> if (firmware_has_feature(FW_FEATURE_ISERIES))
>> return -ENODEV;
Kumar Gala wrote:
>> > Acked-by: Timur Tabi
> How about a Tested-by:
I did test it.
Tested-by: Timur Tabi
--
Timur Tabi
Linux kernel developer at Freescale
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listin
On Nov 17, 2011, at 10:04 AM, Tabi Timur-B04825 wrote:
> On Thu, Nov 17, 2011 at 8:32 AM, Kumar Gala wrote:
>> Utilize new split between board & SoC, and new SoC device trees split
>> into pre & post utilizing 'template' includes for SoC IP blocks.
>>
>> Other changes include:
>>
>> * Reworked
On Thu, Nov 17, 2011 at 8:32 AM, Kumar Gala wrote:
> Utilize new split between board & SoC, and new SoC device trees split
> into pre & post utilizing 'template' includes for SoC IP blocks.
>
> Other changes include:
>
> * Reworked PCIe nodes to allow supportin IRQs for controller (errors)
> and
Traditionally mpc830x_rdb board file searched for mpc8308-pcie devices.
However both in-kernel dts from the beginning declared those pcie units
as compatible with mpc8314-pci, which is handled by mpc83xx_setup_pci().
Drop special handling for mpc8308 and use common function instead.
Signed-off-by
Drop lots of unused headers after board files merge/splitup
Signed-off-by: Dmitry Eremin-Solenikov
---
arch/powerpc/platforms/83xx/asp834x.c |2 -
arch/powerpc/platforms/83xx/km83xx.c | 26 --
arch/powerpc/platforms/83xx/mcu_mpc8349emitx.c |5 ---
arc
Nearly all mpc83xx-based boards have a common piece of code - one that
loops over all pci/pcie bridges and registers them. Merge that code into
a special function common to all boards.
Signed-off-by: Dmitry Eremin-Solenikov
---
arch/powerpc/platforms/83xx/km83xx.c |7 +++
arch/power
83xx board files have a lot of duplication in
*_declare_of_platform_devices() functions. Merge that into a single
function common to most of the boards.
The only leftover is mpc834x_itx.c board file which explicitly asks for
fsl,pq2pro-localbus, as corresponding bindings don't provide
"simple-bus"
On Nov 17, 2011, at 8:01 AM, Tabi Timur-B04825 wrote:
> On Thu, Nov 17, 2011 at 1:16 AM, Kumar Gala wrote:
>
>> - localbus@fffe05000 {
>> - #address-cells = <2>;
>> - #size-cells = <1>;
>> - compatible = "fsl,p1022-elbc", "fsl,elbc", "simple-bus";
Utilize new split between board & SoC, and new SoC device trees split
into pre & post utilizing 'template' includes for SoC IP blocks.
Other changes include:
* Adding of MPIC timer blocks
* Dropping "fsl,p2041-IP..." from compatibles for standard blocks
* Removed mpic interrupt-parent from dcsr-ep
Utilize new split between board & SoC, and new SoC device trees split
into pre & post utilizing 'template' includes for SoC IP blocks.
Other changes include:
* Reworked PCIe nodes to allow supportin IRQs for controller (errors)
and moved PCI device IRQs down to virtual bridge level
* Changed GP
Update all dts files that support SRIO controllers to match the new
fsl,srio device tree binding.
Signed-off-by: Kumar Gala
---
arch/powerpc/boot/dts/fsl/mpc8568si-post.dtsi | 25 +
arch/powerpc/boot/dts/fsl/mpc8569si-post.dtsi | 28 +++---
arch/powerpc/boot/dts/fsl/p2041si-post.
On Thu, Nov 17, 2011 at 1:16 AM, Kumar Gala wrote:
> - localbus@fffe05000 {
> - #address-cells = <2>;
> - #size-cells = <1>;
> - compatible = "fsl,p1022-elbc", "fsl,elbc", "simple-bus";
> + lbc: localbus@fffe05000 {
> reg = <0 0
The re-binding (unbind..bind) of an EMAC device fails because the
static variable "busy_phy_map" is not updated when the device is
removed.
Signed-off-by: Wolfgang Grandegger
---
drivers/net/ethernet/ibm/emac/core.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drive
This patch series ports the cpuidle framework for ppc64 platform and
implements a cpuidle back-end driver for ppc64 (pSeries) platform.
Currently idle states are managed by pseries_{dedicated,shared}_idle_sleep()
routines in arch/powerpc/platforms/pseries/setup.c. There are
two idle states (snooze
On Wed, Nov 16, 2011 at 06:17:56PM -0600, Scott Wood wrote:
> On 11/16/2011 03:55 AM, Zhao Chenhui wrote:
> > From: Li Yang
> >
> > Some 85xx silicons like MPC8536 and P1022 has the JOG PM feature.
>
> P1023 as well -- any plan to support?
>
> I see this in the p1022 and mpc8536 manuals:
>
> >
This patch makes pseries_idle_driver not to be registered when
power_save=off kernel boot option is specified. The
boot_option_idle_override variable used here is similar to
its usage on x86.
Signed-off-by: Deepthi Dharwar
Signed-off-by: Trinabh Gupta
Signed-off-by: Arun R Bharadwaj
---
arch/p
This patch enables cpuidle for pSeries and cpuidle_idle_call() is
directly called from the idle loop. As a result pseries_idle cpuidle
driver registered with cpuidle subsystem comes into action. This patch
also removes the routines pseries_shared_idle_sleep and
pseries_dedicated_idle_sleep as they
This patch implements a backhand cpuidle driver for pSeries
based on pseries_dedicated_idle_loop and pseries_shared_idle_loop
routines. The driver is built only if CONFIG_CPU_IDLE is set. This
cpuidle driver uses global registration of idle states and
not per-cpu.
Signed-off-by: Deepthi Dharwar
This patch provides cpu_idle_wait() routine for the powerpc
platform which is required by the cpuidle subsystem. This
routine is requied to change the idle handler on SMP systems.
The equivalent routine for x86 is in arch/x86/kernel/process.c
but the powerpc implementation is different.
Signed-off
>Cc: linuxppc-dev@lists.ozlabs.org; Li Yang-R58472
>Subject: Re: [PATCH v2 2/7] powerpc/85xx: add HOTPLUG_CPU support
>
>On 11/16/2011 03:55 AM, Zhao Chenhui wrote:
>> +static void __cpuinit smp_85xx_mach_cpu_die(void) {
>> +unsigned int cpu = smp_processor_id();
>> +register u32 tmp;
>>
On certain chip like MPC8536 and P1022, system can be waked up from
sleep by user-defined packet and Magic Patcket.(The eTSEC cannot
supports both types of wake-up event simultaneously.) This patch
implements wake-up on user-defined patcket including ARP request
packet and unicast patcket to this s
Utilize new split between board & SoC, and new SoC device trees split
into pre & post utilizing 'template' includes for SoC IP blocks.
Other changes include:
* Adding of MPIC timer blocks
* Dropping "fsl,p5020-IP..." from compatibles for standard blocks
* Removed mpic interrupt-parent from dcsr-ep
arch/powerpc/oprofile/common.c has this init code:
int __init oprofile_arch_init(struct oprofile_operations *ops)
{
if (!cur_cpu_spec->oprofile_cpu_type)
return -ENODEV;
if (firmware_has_feature(FW_FEATURE_ISERIES))
Do we have AFDX support in Linux/Rt-Linux ?
tried grep.couldnt find any.
Thanks
Vineeth
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
Utilize new split between board & SoC, and new SoC device trees split
into pre & post utilizing 'template' includes for SoC IP blocks.
Other changes include:
* Adding of MPIC timer blocks
* Dropping "fsl,p4080-IP..." from compatibles for standard blocks
* Removed mpic interrupt-parent from dcsr-ep
Utilize new split between board & SoC, and new SoC device trees split
into pre & post utilizing 'template' includes for SoC IP blocks.
Other changes include:
* Adding of MPIC timer blocks
* Dropping "fsl,p3041-IP..." from compatibles for standard blocks
* Removed mpic interrupt-parent from dcsr-ep
63 matches
Mail list logo
