>+ msi_mask = of_get_property(dev->dev.of_node, "msi-mask", NULL);
> >+ if (!msi_mask) {
> >+ err = -1;
> >+ goto error_out;
> >+ }
>
> This will return non zero value to probe function which would call
ppc4xx_msi_remove() function. In the ppc4xx_msi_remove(
From: Tirumala Marri
This patch adds MSI support for 440SPe, 460Ex, 460Sx and 405Ex.
Signed-off-by: Tirumala R Marri
---
v3:
* Rebased to Josh next tree
* Cleanup and remove some unwanted log msg.
* Remove list member and its references.
* Keep msi_data local reference.
v2:
* Remove or ad
On 29.11.2010 [12:38:41 +1100], Benjamin Herrenschmidt wrote:
> On Tue, 2010-10-26 at 20:35 -0700, Nishanth Aravamudan wrote:
> > The iommu_table pointer in the pci auxiliary struct of device_node has
> > not been used by the iommu ops since the dma refactor of
> > 12d04eef927bf61328af2c7cbe756c96f
This driver allows userspace to access the data processing FPGAs on the
OVRO CARMA board. It has two modes of operation:
1) random access
This allows users to poke any DATA-FPGA registers by using mmap to map
the address region directly into their memory map.
2) correlation dumping
When correla
This adds support for programming the data processing FPGAs on the OVRO
CARMA board. These FPGAs have a special programming sequence that
requires that we program the Freescale DMA engine, which is only
available inside the kernel.
Signed-off-by: Ira W. Snyder
---
drivers/misc/carma/Kconfig
Hello everyone,
This is the third posting of these drivers, taking into account comments
from earlier postings. The DMAEngine patches are in mainline now, and
therefore are not part of this series anymore.
RFCv2 -> RFCv3:
- use miscdevice framework (removing the carma class)
- add bitfile readbac
On Fri, Dec 03, 2010 at 01:43:37PM -0600, Timur Tabi wrote:
>Josh Boyer wrote:
>> Just the moving of the clear_bit inside the #ifndef
>> CONFIG_WATCHDOG_NOWAYOUT.
>
>If I move the clear_bit() call inside the #ifndef, then when
>CONFIG_WATCHDOG_NOWAYOUT is defined, after a process closes /dev/watchd
Josh Boyer wrote:
> Just the moving of the clear_bit inside the #ifndef
> CONFIG_WATCHDOG_NOWAYOUT.
If I move the clear_bit() call inside the #ifndef, then when
CONFIG_WATCHDOG_NOWAYOUT is defined, after a process closes /dev/watchdog, no
process will ever be able to open it again. Are you saying
On Fri, Dec 03, 2010 at 01:10:02PM -0600, Timur Tabi wrote:
>> I guess I don't really care either way if multiple processes have the
>> device open, as long as none of them can "disable" the watchdog if
>> NOWAYOUT is set.
>
>Well, this patch takes care of that problem.
>
>So just to be clear, do y
I think they should follow the previous two that are in Kumar's tree.
Probably Kumar may give you a better timeline estimate for this.
Alex.
From: linuxppc-dev-bounces+alexandre.bounine=idt@lists.ozlabs.org
[mailto:linuxppc-dev-bounces+alexandre.bounine=idt@lists.ozlabs.org]
On
Josh Boyer wrote:
> No, you definitely want to allow something to open it. If it's running
> and nothing opens the device and calls write, then you have no way of
> preventing the watchdog from just resetting your board every time.
Now it's my turn to go Doh! Of course you have to be able to ope
On Fri, Dec 03, 2010 at 12:22:30PM -0600, Timur Tabi wrote:
>Josh Boyer wrote:
>> I'm confused why you can't use booke_wdt_enabled for the purposes of the
>> device having been opened. It seems the use of the wdt_is_active
>> basically duplicates this functionalit (and oddly with the bit
>> manipu
Josh Boyer wrote:
> I'm confused why you can't use booke_wdt_enabled for the purposes of the
> device having been opened. It seems the use of the wdt_is_active
> basically duplicates this functionalit (and oddly with the bit
> manipulation instead of just atomic_inc/dec).
Because the watchdog can
On Sat, Dec 4, 2010 at 12:40 AM, Kumar Gala wrote:
>
> On Dec 3, 2010, at 6:34 AM, Li Yang wrote:
>
>> The timebase sync is not only necessary when using KEXEC. It should also
>> be used by normal boot up and cpu hotplug. Remove the ifdef added by
>> the KEXEC patch. Fix a problem that cpu hotp
On Fri, Dec 03, 2010 at 10:51:43AM -0600, Timur Tabi wrote:
>Normally, the watchdog is disabled when dev/watchdog is closed, but if
>CONFIG_WATCHDOG_NOWAYOUT is defined, then it means that the watchdog should
>remain enabled. So we should disable it only if CONFIG_WATCHDOG_NOWAYOUT is
>not defined
In order to prevent the fsl_dma driver from claiming the DMA channels that the
P1022DS audio driver needs, the compatible properties for those nodes must say
"fsl,ssi-dma-channel" instead of "fsl,eloplus-dma-channel".
Signed-off-by: Timur Tabi
---
Kumar, please pick up this patch for 2.6.37.
a
Normally, the watchdog is disabled when dev/watchdog is closed, but if
CONFIG_WATCHDOG_NOWAYOUT is defined, then it means that the watchdog should
remain enabled. So we should disable it only if CONFIG_WATCHDOG_NOWAYOUT is
not defined.
Also ensure that /dev/watchdog is only opened by one process
On Dec 3, 2010, at 6:34 AM, Li Yang wrote:
> The timebase sync is not only necessary when using KEXEC. It should also
> be used by normal boot up and cpu hotplug. Remove the ifdef added by
> the KEXEC patch. Fix a problem that cpu hotplugging freezes the whole system.
>
> Signed-off-by: Jin Q
> Is there any update on this in the meantime? Do you know of any plans to re-
> work/-push this patchset? Just checking...
I had another look recently; I wouldn't like to just copy/paste the
"new_id"-mechanism from PCI because the code would then exist three
times in the kernel (PCMCIA being the
Wolfram,
On Thursday 28 January 2010 11:45:45 Wolfram Sang wrote:
> > I guess I'd like to just open up a discussion, see if there's been any
> > progress towards a general solution.
>
> I decided to wait for the outcome of the of_platform-removal-idea. Though,
> I have to admit that in the last w
On 03/12/10 14:58, Guillaume Dargaud wrote:
> Why is there not a word about the functions platform_*_register in my various
> driver books ? LDD 3rd ed (O'Reilly), Writing LDD (Cooperstein) or LKD
> (Love)... Is it something specific to powerpc and the books are oriented x86
> ?
> What's a good
> No. of_platform_drivers are more/less obsolete. Normal platform drivers
> can now be associated with a device-tree node just fine.
OK.
If my dts definition is thus:
xps_acqui_data_0: xps-acqui-d...@c980 {
compatible = "xlnx,xps-acqui-data-3.00.a";
Hi Ben
Some 4xx power management patches from Victor. I would have liked to
include the PCI-e and Canyonlands USB phy fix patches as well, but they
still need rework. I might include those in a later pull request if
they show up relatively soon.
josh
The following changes since commit 46f52210
Some 85xx silicons like MPC8536 and P1022 has the JOG PM feature.
The patch adds the support to change CPU frequency using the standard
cpufreq interface.
Signed-off-by: Dave Liu
Signed-off-by: Li Yang
---
arch/powerpc/platforms/85xx/Makefile |1 +
arch/powerpc/platforms/85xx/cpufreq.c |
Signed-off-by: Li Yang
---
Documentation/powerpc/dts-bindings/fsl/pmc.txt | 63 +--
1 files changed, 36 insertions(+), 27 deletions(-)
diff --git a/Documentation/powerpc/dts-bindings/fsl/pmc.txt
b/Documentation/powerpc/dts-bindings/fsl/pmc.txt
index 07256b7..d84b4f8 100644
There are global timers in the MPIC interrupt controller. The patch
adds support to the timers.
The timer can generate interrupt which can be used as a wakeup event.
Signed-off-by: Dave Liu
Signed-off-by: Li Yang
---
arch/powerpc/include/asm/mpic.h |1 +
arch/powerpc/sysdev/Makefile
Some Freescale chips like MPC8536 and P1022 has deep sleep PM mode
in addtion to the sleep PM mode.
In sleep power management mode, the clock of e500 core
is turned off, the clocks of most IP blocks are shut off,
only the modules clocks which allows to wake up the
processor are still running.
Whi
This can be used as a wakeup source for power management.
Signed-off-by: Li Yang
---
arch/powerpc/boot/dts/p2020ds.dts|9 -
arch/powerpc/platforms/85xx/mpc85xx_ds.c | 26 +-
2 files changed, 33 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc
Add support to disable and re-enable individual cores at runtime
on MPC85xx/QorIQ SMP machines.
This makes suspend/resume possible for SMP systems, as the power management
code on SMP always disable non-boot cpus on suspend.
MPC85xx machines use ePAPR spin-table in boot page for CPU kick-off.
Thi
The timebase sync is not only necessary when using KEXEC. It should also
be used by normal boot up and cpu hotplug. Remove the ifdef added by
the KEXEC patch. Fix a problem that cpu hotplugging freezes the whole system.
Signed-off-by: Jin Qing
Singed-off-by: Li Yang
---
arch/powerpc/platform
On Fri, Dec 03, 2010 at 04:59:58PM +1100, Benjamin Herrenschmidt wrote:
>On Fri, 2010-12-03 at 16:32 +1100, Stephen Rothwell wrote:
>>
>> After merging the tree, today's linux-next build (powerpc allmodconfig)
>> failed like this:
>>
>> arch/powerpc/lib/hweight_64.S: Assembler messages:
>> arch/
31 matches
Mail list logo
