There is simply no reason to be manually setting the private driver
data to NULL in the remove/fail to probe cases. This is just extra
cruft code that can be removed.
A few notes:
* Nothing relies on drvdata being set to NULL.
* The __device_release_driver() function eventually calls
dev_set_dr
On Jan 21, 2013, at 7:56 PM, Scott Wood wrote:
> The MPIC code will disable coreint if it detects an insufficient
> MPIC version.
>
> Signed-off-by: Scott Wood
> ---
> arch/powerpc/platforms/85xx/qemu_e500.c |7 ---
> 1 file changed, 4 insertions(+), 3 deletions(-)
applied to next
- k
On Jan 21, 2013, at 7:56 PM, Scott Wood wrote:
> This will be used by the qemu-e500 platform, as the MPIC version (and
> thus whether we have coreint) depends on how QEMU is configured.
>
> Signed-off-by: Scott Wood
> ---
> arch/powerpc/sysdev/mpic.c | 26 +++---
> 1 file c
On Jan 14, 2013, at 5:28 AM, Varun Sethi wrote:
> The pci controller structure has a provision to store the device strcuture
> pointer of the corresponding platform device. Currently this information is
> not stored during fsl pci controller initialization. This information is
> required while de
On Feb 13, 2013, at 8:09 AM, Stef van Os wrote:
> Initial board support for the Prodrive PPA8548 AMC module. Board
> is an MPC8548 AMC platform used in RapidIO systems. This module is
> also used to test/work on mainline linux RapidIO software.
>
> PPA8548 overview:
> - 1.3 GHz Freescale PowerQU
On Jan 17, 2013, at 5:26 PM, Timur Tabi wrote:
> From: Timur Tabi
>
> The Freescale DIU driver was recently updated to not require every DIU
> platform function, so now we can remove the unneeded functions from
> some boards.
>
> Signed-off-by: Timur Tabi
> ---
> arch/powerpc/platforms/512x/m
On Jan 21, 2013, at 7:02 AM, Julia Lawall wrote:
> From: Julia Lawall
>
> Delete successive tests to the same location. The code tested the result
> of a previous call, that itself was already tested. It is changed to test
> the result of the most recent call.
>
> A simplified version of the
Hi Vincent,
On 02/15/2013 06:58 PM, Vincent Guittot wrote:
> Hi Srivatsa,
>
> I have run some tests with you branch (thanks Paul for the git tree)
> and you will find results below.
>
Thank you very much for testing this patchset!
> The tests condition are:
> - 5 CPUs system in 2 clusters
> -
> * The proto-VSIDs are then scrambled into real VSIDs with the
> * multiplicative hash:
> ...
> * VSID_MULTIPLIER is prime, so in particular it is
> * co-prime to VSID_MODULUS, making this a 1:1 scrambling function.
> * Because the modulus is 2^n-1 we can compute it efficiently without
>
From: "Aneesh Kumar K.V"
VSID_BITS and VSID_BITS_1T depends on the context bits and user esid
bits. Make the dependency explicit
Signed-off-by: Aneesh Kumar K.V
---
arch/powerpc/include/asm/mmu-hash64.h | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/arch/pow
From: "Aneesh Kumar K.V"
This patch change the kernel VSID range so that we limit VSID_BITS to 37.
This enables us to support 64TB with 65 bit VA (37+28). Without this patch
we have boot hangs on platforms that only support 65 bit VA.
With this patch we now have proto vsid generated as below:
W
On 02/15/2013 02:11 AM, Benjamin Herrenschmidt wrote:
On Thu, 2013-02-14 at 14:56 +0200, Diana Craciun wrote:
From: Diana Craciun
On Freescale e6500 cores EPCR[DGTMI] controls whether guest supervisor
state can execute TLB management instructions. If EPCR[DGTMI]=0
tlbwe and tlbilx are allowed
12 matches
Mail list logo
