[PATCH] perf_counter/powerpc: Fix compilation after perf_counter_overflow change

2009-09-20 Thread Paul Mackerras
Commit 5622f295 ("x86, perf_counter, bts: Optimize BTS overflow handling") removed the regs field from struct perf_sample_data and added a regs parameter to perf_counter_overflow(). This breaks the build on powerpc as reported by Sachin Sant: arch/powerpc/kernel/perf_counter.c: In function 'recor

2.6.31-git10 : perf counters build failure on powerpc

2009-09-20 Thread Sachin Sant
Latest 31 git(2.6.31-git10 : ebc79c4f8da0f92efa968e0328f32334a2ce80cf) fails to build on powerpc with following error arch/powerpc/kernel/perf_counter.c: In function 'record_and_restart': arch/powerpc/kernel/perf_counter.c:1165: error: unknown field 'regs' specified in initializer cc1: warnings

Re: [PATCH 2/2] powerpc: Change archdata dma_data to a union

2009-09-20 Thread Benjamin Herrenschmidt
On Wed, 2009-09-02 at 17:23 -0500, Becky Bruce wrote: > Sometimes this is used to hold a simple offset, and sometimes > it is used to hold a pointer. This patch changes it to a union containing > void * and dma_addr_t. get/set accessors are also provided, because it was > getting a bit ugly to ge

Re: [PATCH 1/2] powerpc: rename get_dma_direct_offset get_dma_offset

2009-09-20 Thread Benjamin Herrenschmidt
On Wed, 2009-09-02 at 17:23 -0500, Becky Bruce wrote: > #ifdef CONFIG_NOT_COHERENT_CACHE > /* > @@ -90,6 +89,14 @@ static inline void set_dma_ops(struct device *dev, struct > dma_map_ops *ops) > dev->archdata.dma_ops = ops; > } > > +static inline unsigned long get_dma_offset(struct dev

Re: PPC_4xx synopsy USB driver

2009-09-20 Thread Stefan Roese
Hi Sylvain, On Friday 18 September 2009 17:50:24 Cote, Sylvain wrote: > USB gadget support --> y > Maximum VBUS power usage = 500 > Synopsys DWC OTG controller > Synopsys DWC OTG internal DMA mode --> y > USB gadget --> M > gadget zero --

[PATCH] sbc8548: fixup of PCI-e related DTS fields

2009-09-20 Thread Paul Gortmaker
The PCI-e addressing was originally patterned of the MPC8548CDS which has PCI1, PCI2, and PCI-e. Since this board only has PCI1 and PCI-e, it makes more sense to be similar to the MPC8568MDS board. This does that by cutting the PCI/PCI-e I/O sizes from 16MB to 8MB and pulling the PCI-e I/O range