31 May, 2019

1 commit

  • Based on 1 normalized pattern(s):

    this program is free software you can redistribute it and or modify
    it under the terms of the gnu general public license as published by
    the free software foundation either version 2 of the license or at
    your option any later version

    extracted by the scancode license scanner the SPDX license identifier

    GPL-2.0-or-later

    has been chosen to replace the boilerplate/reference in 3029 file(s).

    Signed-off-by: Thomas Gleixner
    Reviewed-by: Allison Randal
    Cc: linux-spdx@vger.kernel.org
    Link: https://lkml.kernel.org/r/20190527070032.746973796@linutronix.de
    Signed-off-by: Greg Kroah-Hartman

    Thomas Gleixner
     

16 May, 2018

1 commit


06 May, 2015

1 commit

  • In our department we are using some older Janz ICAN3-modules in our dekstop
    pcs. There we have slightly different carrier boards than the janz-cmodio
    supported in the kernel sources, called CAN-PCI2 with two submodules. But the
    pci configuration regions are identical. So extending the supported pci devices
    to the corresponding device ids is sufficient to get the drivers working.

    * The old ICAN3-modules with firmware 1.28 need more then 250ms for the restart
    after reset. I've increased the timeout to 500ms.
    * The janz_ican3 module uses the raw can services of the Janz-firmware, this
    means firmware must be ICANOS/2. Our ICAN3-modules are equipped with
    CAL/CANopen-firmware, so I must use the appropriate commands for the layer
    management services.

    Te driver detects the firmware after module reset and selects the commands
    matching the firmware. This affects the bus on/off-command
    (ican3_set_bus_state) and the configuration of the bittiming
    (ican3_set_bittiming). For better diagnostics the detected firmware string is
    presented as sysfs attribute (fwinfo).

    Signed-off-by: Andreas Gröger
    Signed-off-by: Marc Kleine-Budde

    Andreas Gröger
     

19 Mar, 2014

1 commit


21 Jan, 2014

1 commit


13 Jun, 2013

1 commit


29 Nov, 2012

3 commits

  • CONFIG_HOTPLUG is going away as an option so __devexit is no
    longer needed.

    Signed-off-by: Bill Pemberton
    Cc: Srinidhi Kasagar
    Cc: Peter Tyser
    Cc: Daniel Walker
    Cc: Bryan Huntsman
    Acked-by: David Brown
    Acked-by: Linus Walleij
    Acked-by: Mark Brown
    Signed-off-by: Greg Kroah-Hartman

    Bill Pemberton
     
  • CONFIG_HOTPLUG is going away as an option so __devinit is no longer
    needed.

    Signed-off-by: Bill Pemberton
    Cc: Srinidhi Kasagar
    Cc: Peter Tyser
    Cc: Daniel Walker
    Cc: Bryan Huntsman
    Acked-by: David Brown
    Acked-by: Mark Brown
    Signed-off-by: Greg Kroah-Hartman

    Bill Pemberton
     
  • CONFIG_HOTPLUG is going away as an option so __devexit_p is no longer
    needed.

    Signed-off-by: Bill Pemberton
    Cc: Srinidhi Kasagar
    Cc: Peter Tyser
    Cc: Daniel Walker
    Cc: Bryan Huntsman
    Acked-by: David Brown
    Acked-by: Linus Walleij
    Acked-by: Mark Brown
    Signed-off-by: Greg Kroah-Hartman

    Bill Pemberton
     

16 Sep, 2012

1 commit

  • Currently the MFD core supports remapping MFD cell interrupts using an
    irqdomain but only if the MFD is being instantiated using device tree
    and only if the device tree bindings use the pattern of registering IPs
    in the device tree with compatible properties. This will be actively
    harmful for drivers which support non-DT platforms and use this pattern
    for their DT bindings as it will mean that the core will silently change
    remapping behaviour and it is also limiting for drivers which don't do
    DT with this particular pattern. There is also a potential fragility if
    there are interrupts not associated with MFD cells and all the cells are
    omitted from the device tree for some reason.

    Instead change the code to take an IRQ domain as an optional argument,
    allowing drivers to take the decision about the parent domain for their
    interrupts. The one current user of this feature is ab8500-core, it has
    the domain lookup pushed out into the driver.

    Signed-off-by: Mark Brown
    Signed-off-by: Samuel Ortiz

    Mark Brown
     

01 May, 2012

1 commit

  • This patch converts the drivers in drivers/mfd/* to use module_pci_driver()
    macro which makes the code smaller and a bit simpler.

    Signed-off-by: Axel Lin
    Cc: Andres Salomon
    Cc: Ira W. Snyder
    Cc: Florian Fainelli
    Cc: Denis Turischev
    Cc: Harald Welte
    Signed-off-by: Samuel Ortiz

    Axel Lin
     

13 Jan, 2012

1 commit


27 May, 2011

1 commit

  • With the addition of a platform device mfd_cell pointer, MFD drivers
    can go back to passing platform data back to their sub drivers.
    This allows for an mfd_cell->mfd_data removal and thus keep the
    sub drivers MFD agnostic. This is mostly needed for non MFD aware
    sub drivers.

    Cc: Ira W. Snyder
    Cc: Wolfgang Grandegger
    Cc: Grant Likely
    Signed-off-by: Samuel Ortiz

    Samuel Ortiz
     

23 Mar, 2011

2 commits

  • Rename the platform_data variable to imply a distinction between
    common platform_data driver usage (typically accessed via
    pdev->dev.platform_data) and the way MFD passes data down to
    clients (using a wrapper named mfd_get_data).

    All clients have already been changed to use the wrapper function,
    so this can be a quick single-commit change that only touches things
    in drivers/mfd.

    Signed-off-by: Andres Salomon
    Acked-by: Linus Walleij
    Signed-off-by: Samuel Ortiz

    Andres Salomon
     
  • The cell's platform_data is now accessed with a helper function;
    change clients to use that, and remove the now-unused data_size.

    Signed-off-by: Andres Salomon
    Signed-off-by: Samuel Ortiz

    Andres Salomon
     

12 Aug, 2010

1 commit


28 May, 2010

1 commit