23 Nov, 2016

3 commits


25 Sep, 2016

1 commit


14 Jul, 2016

1 commit

  • powernv marks it's halt and restart calls as __noreturn. However,
    ppc_md does not have this annotation. Add the annotation to ppc_md,
    and then to every halt/restart function that is missing it.

    Additionally, I have verified that all of these functions do not
    return. Occasionally I have added a spin loop to be sure.

    Signed-off-by: Daniel Axtens
    Signed-off-by: Michael Ellerman

    Daniel Axtens
     

10 Nov, 2014

1 commit

  • Of_node_put supports NULL as its argument, so the initial test is not
    necessary.

    Suggested by Uwe Kleine-König.

    The semantic patch that fixes this problem is as follows:
    (http://coccinelle.lip6.fr/)

    //
    @@
    expression e;
    @@

    -if (e)
    of_node_put(e);
    //

    Signed-off-by: Julia Lawall
    Acked-by: Benjamin Herrenschmidt
    Signed-off-by: Michael Ellerman

    Julia Lawall
     

03 Nov, 2014

1 commit

  • The generic Linux framework to power off the machine is a function pointer
    called pm_power_off. The trick about this pointer is that device drivers can
    potentially implement it rather than board files.

    Today on powerpc we set pm_power_off to invoke our generic full machine power
    off logic which then calls ppc_md.power_off to invoke machine specific power
    off.

    However, when we want to add a power off GPIO via the "gpio-poweroff" driver,
    this card house falls apart. That driver only registers itself if pm_power_off
    is NULL to ensure it doesn't override board specific logic. However, since we
    always set pm_power_off to the generic power off logic (which will just not
    power off the machine if no ppc_md.power_off call is implemented), we can't
    implement power off via the generic GPIO power off driver.

    To fix this up, let's get rid of the ppc_md.power_off logic and just always use
    pm_power_off as was intended. Then individual drivers such as the GPIO power off
    driver can implement power off logic via that function pointer.

    With this patch set applied and a few patches on top of QEMU that implement a
    power off GPIO on the virt e500 machine, I can successfully turn off my virtual
    machine after halt.

    Signed-off-by: Alexander Graf
    [mpe: Squash into one patch and update changelog based on cover letter]
    Signed-off-by: Michael Ellerman

    Alexander Graf
     

23 May, 2014

1 commit

  • Parsing and registration of fixed PHY devices was needed with the use of
    of_phy_connect_fixed_link() because this function was using the
    designated PHY address identifier (first cell of the property) as the
    address to bind the PHY on the emulated bus.

    Since commit 3be2a49e5c08d268f8af0dd4fe89a24ea8cdc339 ("of: provide a
    binding for fixed link PHYs") a new pair of functions has been
    introduced which allows for dynamic address allocation of these fixed
    PHY devices, but also parses the old 'fixed-link' 5-digit property.

    Registration of fixed PHY early in platform code was needed because we
    could not issue a fixed MDIO bus re-scan within network drivers. The
    fixed PHYs had to be registered before the network drivers would call
    of_phy_connect_fixed_link(). All of these caveats are solved now, such
    that we can safely remove of_add_fixed_phys() now.

    Signed-off-by: Florian Fainelli
    Signed-off-by: David S. Miller

    Florian Fainelli
     

13 Feb, 2013

1 commit

  • arch/powerpc/sysdev/fsl_soc.c:70:67: warning: incorrect type in argument 2 (different base types)
    arch/powerpc/sysdev/fsl_soc.c:70:67: expected restricted __be32 const [usertype] *addr
    arch/powerpc/sysdev/fsl_soc.c:70:67: got unsigned int const [usertype] *

    Signed-off-by: Kim Phillips
    Signed-off-by: Kumar Gala

    Kim Phillips
     

06 Oct, 2012

1 commit


29 Mar, 2012

1 commit


01 Nov, 2011

1 commit


27 Jul, 2011

1 commit

  • This allows us to move duplicated code in
    (atomic_inc_not_zero() for now) to

    Signed-off-by: Arun Sharma
    Reviewed-by: Eric Dumazet
    Cc: Ingo Molnar
    Cc: David Miller
    Cc: Eric Dumazet
    Acked-by: Mike Frysinger
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Arun Sharma
     

27 Jun, 2011

1 commit

  • Add functions to restart and halt the current partition when running under
    the Freescale hypervisor. These functions should be assigned to various
    function pointers of the ppc_md structure during the .probe() function for
    the board:

    ppc_md.restart = fsl_hv_restart;
    ppc_md.power_off = fsl_hv_halt;
    ppc_md.halt = fsl_hv_halt;

    Signed-off-by: Timur Tabi
    Signed-off-by: Kumar Gala

    Timur Tabi
     

23 Oct, 2010

2 commits

  • * git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb-2.6: (141 commits)
    USB: mct_u232: fix broken close
    USB: gadget: amd5536udc.c: fix error path
    USB: imx21-hcd - fix off by one resource size calculation
    usb: gadget: fix Kconfig warning
    usb: r8a66597-udc: Add processing when USB was removed.
    mxc_udc: add workaround for ENGcm09152 for i.MX35
    USB: ftdi_sio: add device ids for ScienceScope
    USB: musb: AM35x: Workaround for fifo read issue
    USB: musb: add musb support for AM35x
    USB: AM35x: Add musb support
    usb: Fix linker errors with CONFIG_PM=n
    USB: ohci-sh - use resource_size instead of defining its own resource_len macro
    USB: isp1362-hcd - use resource_size instead of defining its own resource_len macro
    USB: isp116x-hcd - use resource_size instead of defining its own resource_len macro
    USB: xhci: Fix compile error when CONFIG_PM=n
    USB: accept some invalid ep0-maxpacket values
    USB: xHCI: PCI power management implementation
    USB: xHCI: bus power management implementation
    USB: xHCI: port remote wakeup implementation
    USB: xHCI: port power management implementation
    ...

    Manually fix up (non-data) conflict: the SCSI merge gad renamed the
    'hw_sector_size' member to 'physical_block_size', and the USB tree
    brought a new use of it.

    Linus Torvalds
     
  • Replace FSL USB platform code by simple platform driver for
    creation of FSL USB platform devices.

    The driver creates platform devices based on the information
    from USB nodes in the flat device tree. This is the replacement
    for old arch fsl_soc usb code removed by this patch. The driver
    uses usual of-style binding, available EHCI-HCD and UDC
    drivers can be bound to the created devices. The new of-style
    driver additionaly instantiates USB OTG platform device, as the
    appropriate USB OTG driver will be added soon.

    Signed-off-by: Anatolij Gustschin
    Cc: Kumar Gala
    Cc: Grant Likely
    Signed-off-by: Greg Kroah-Hartman

    Anatolij Gustschin
     

14 Oct, 2010

1 commit


21 Nov, 2009

1 commit


25 Aug, 2009

1 commit


19 May, 2009

1 commit


09 May, 2009

1 commit

  • commit b31a1d8b41513b96e9c7ec2f68c5734cef0b26a4 ("gianfar: Convert
    gianfar to an of_platform_driver"), possibly due merge issues,
    reintroduced completely unneded mpc83xx_wdt_init call, which
    I removed some time ago in commit 20d38e01d48019c578ab0ec1464454c0
    ("powerpc/fsl_soc: remove mpc83xx_wdt code").

    Remove it once again.

    Signed-off-by: Anton Vorontsov
    Signed-off-by: Kumar Gala

    Anton Vorontsov
     

01 Apr, 2009

2 commits

  • The advantages of this:
    - Don't encourage legacy support;
    - Less external symbols, less code to compile-in for !MPC832x_RDB
    platforms.

    Signed-off-by: Anton Vorontsov
    Cc: David Brownell
    Cc: Benjamin Herrenschmidt
    Cc: Kumar Gala
    Cc: Grant Likely
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Anton Vorontsov
     
  • The main purpose of this patch is to pass 'struct spi_device' to the chip
    select handling routines. This is needed so that we could implement
    full-fledged OpenFirmware support for this driver.

    While at it, also:
    - Replace two {de,activate}_cs routines by single cs_contol().
    - Don't duplicate platform data callbacks in mpc83xx_spi struct.

    Signed-off-by: Anton Vorontsov
    Cc: David Brownell
    Cc: Benjamin Herrenschmidt
    Cc: Kumar Gala
    Cc: Grant Likely
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Anton Vorontsov
     

09 Mar, 2009

1 commit


17 Dec, 2008

1 commit

  • Does the same for the accompanying MDIO driver, and then modifies the TBI
    configuration method. The old way used fields in einfo, which no longer
    exists. The new way is to create an MDIO device-tree node for each instance
    of gianfar, and create a tbi-handle property to associate ethernet controllers
    with the TBI PHYs they are connected to.

    Signed-off-by: Andy Fleming
    Signed-off-by: David S. Miller

    Andy Fleming
     

31 Oct, 2008

1 commit

  • The init_phy() function attaches to the PHY, then configures the
    SerDesTBI link (in SGMII mode). The TBI is on the MDIO bus with the PHY
    (sort of) and is accessed via the gianfar's MDIO registers, using the
    functions gfar_local_mdio_read/write(), which don't do any locking.

    The previously attached PHY will start a work-queue on a timer, and
    probably an irq handler as well, which will talk to the PHY and thus use
    the MDIO bus. This uses phy_read/write(), which have locking, but not
    against the gfar_local_mdio versions.

    The result is that PHY code will try to use the MDIO bus at the same time
    as the SerDes setup code, corrupting the transfers.

    Setting up the SerDes before attaching to the PHY will insure that there is
    no race between the SerDes code and *our* PHY, but doesn't fix everything.
    Typically the PHYs for all gianfar devices are on the same MDIO bus, which
    is associated with the first gianfar device. This means that the first
    gianfar's SerDes code could corrupt the MDIO transfers for a different
    gianfar's PHY.

    The lock used by phy_read/write() is contained in the mii_bus structure,
    which is pointed to by the PHY. This is difficult to access from the
    gianfar drivers, as there is no link between a gianfar device and the
    mii_bus which shares the same MDIO registers. As far as the device layer
    and drivers are concerned they are two unrelated devices (which happen to
    share registers).

    Generally all gianfar devices' PHYs will be on the bus associated with the
    first gianfar. But this might not be the case, so simply locking the
    gianfar's PHY's mii bus might not lock the mii bus that the SerDes setup
    code is going to use.

    We solve this by having the code that creates the gianfar platform device
    look in the device tree for an mdio device that shares the gianfar's
    registers. If one is found the ID of its platform device is saved in the
    gianfar's platform data.

    A new function in the gianfar mii code, gfar_get_miibus(), can use the bus
    ID to search through the platform devices for a gianfar_mdio device with
    the right ID. The platform device's driver data is the mii_bus structure,
    which the SerDes setup code can use to lock the current bus.

    Signed-off-by: Trent Piepho
    CC: Andy Fleming
    Signed-off-by: Jeff Garzik

    Trent Piepho
     

14 Oct, 2008

1 commit


29 Sep, 2008

1 commit


17 Jul, 2008

3 commits


13 Jul, 2008

1 commit


09 Jun, 2008

1 commit


07 Jun, 2008

1 commit

  • Change the name of the device from "rtc-ds1374" to just "ds1374", to match
    what all other RTC drivers do. I seem to remember that this name was
    chosen to avoid possible confusion with an older ds1374 driver, but that
    driver was removed 3 months ago.

    Signed-off-by: Jean Delvare
    Signed-off-by: Alessandro Zummo
    Acked-by: Kumar Gala
    Cc: Paul Mackerras
    Cc: Benjamin Herrenschmidt
    Cc: David Brownell
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Jean Delvare
     

03 Jun, 2008

3 commits


04 May, 2008

1 commit

  • * git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc:
    [POWERPC] Bolt in SLB entry for kernel stack on secondary cpus
    [POWERPC] PS3: Update ps3_defconfig
    [POWERPC] PS3: Remove unsupported wakeup sources
    [POWERPC] PS3: Make ps3_virq_setup and ps3_virq_destroy static
    [POWERPC] PS3: Add time include to lpm
    [POWERPC] Fix slb.c compile warnings
    [POWERPC] Xilinx: Fix compile warnings
    [POWERPC] Squash build warning for print of resource_size_t in fsl_soc.c
    [RAPIDIO] fix current kernel-doc notation
    [POWERPC] 86xx: mpc8610_hpcd: add support for PCI Express x8 slot
    Fix a potential issue in mpc52xx uart driver
    [POWERPC] mpc5200: Allow for fixed speed MII configurations
    [POWERPC] 86xx: Fix the wrong serial1 interrupt for 8610 board

    Linus Torvalds
     

02 May, 2008

1 commit


30 Apr, 2008

1 commit

  • Based on earlier work by Jon Smirl and Jochen Friedrich.

    Update most new-style i2c drivers to use standard module aliasing
    instead of the old driver_name/type driver matching scheme. I've
    left the video drivers apart (except for SoC camera drivers) as
    they're a bit more diffcult to deal with, they'll have their own
    patch later.

    Signed-off-by: Jean Delvare
    Cc: Jon Smirl
    Cc: Jochen Friedrich

    Jean Delvare