1. 03 Feb, 2015 1 commit
    • Alan Cox's avatar
      i2o: move to staging · 2cbf7fe2
      Alan Cox authored
      The I2O layer deals with a technology that to say the least didn't catch on
      in the market.
      The only relevant products are some of the AMI MegaRAID - which supported I2O
      and its native mode (The native mode is faster and runs on Linux), an
      obscure crypto ethernet card that's now so many years out of date nobody
      would use it, the old DPT controllers, which speak their own dialect and
      have their own driver - and ermm.. thats about it.
      We also know the code isn't in good shape as recently a patch was proposed
      and queried as buggy, which in turn showed the existing code was broken
      already by prior "clean up" and nobody had noticed that either.
      It's coding style robot code nothing more. Like some forgotten corridor
      cleaned relentlessly by a lost Roomba but where no user has trodden in years.
      Move it to staging and then to /dev/null.
      The headers remain as they are shared with dpt_i2o.
      Signed-off-by: default avatarAlan Cox <alan@linux.intel.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
  2. 25 Jan, 2015 1 commit
  3. 26 Nov, 2014 1 commit
  4. 19 Oct, 2014 1 commit
  5. 24 Sep, 2014 1 commit
    • Sandeep Nair's avatar
      soc: ti: add Keystone Navigator QMSS driver · 41f93af9
      Sandeep Nair authored
      The QMSS (Queue Manager Sub System) found on Keystone SOCs is one of
      the main hardware sub system which forms the backbone of the Keystone
      Multi-core Navigator. QMSS consist of queue managers, packed-data structure
      processors(PDSP), linking RAM, descriptor pools and infrastructure
      Packet DMA.
      The Queue Manager is a hardware module that is responsible for accelerating
      management of the packet queues. Packets are queued/de-queued by writing or
      reading descriptor address to a particular memory mapped location. The PDSPs
      perform QMSS related functions like accumulation, QoS, or event management.
      Linking RAM registers are used to link the descriptors which are stored in
      descriptor RAM. Descriptor RAM is configurable as internal or external memory.
      The QMSS driver manages the PDSP setups, linking RAM regions,
      queue pool management (allocation, push, pop and notify) and descriptor
      pool management. The specifics on the device tree bindings for
      QMSS can be found in:
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Cc: Kumar Gala <galak@codeaurora.org>
      Cc: Olof Johansson <olof@lixom.net>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Grant Likely <grant.likely@linaro.org>
      Cc: Rob Herring <robh+dt@kernel.org>
      Cc: Mark Rutland <mark.rutland@arm.com>
      Signed-off-by: default avatarSandeep Nair <sandeep_n@ti.com>
      Signed-off-by: default avatarSantosh Shilimkar <santosh.shilimkar@ti.com>
  6. 23 Jun, 2014 1 commit
  7. 19 Jun, 2014 1 commit
    • Andreas Noever's avatar
      thunderbolt: Add initial cactus ridge NHI support · 16603153
      Andreas Noever authored
      Thunderbolt hotplug is supposed to be handled by the firmware. But Apple
      decided to implement thunderbolt at the operating system level. The
      firmare only initializes thunderbolt devices that are present at boot
      time. This driver enables hotplug of thunderbolt of non-chained
      thunderbolt devices on Apple systems with a cactus ridge controller.
      This first patch adds the Kconfig file as well the parts of the driver
      which talk directly to the hardware (that is pci device setup, interrupt
      handling and RX/TX ring management).
      Signed-off-by: default avatarAndreas Noever <andreas.noever@gmail.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
  8. 23 May, 2014 1 commit
  9. 28 Feb, 2014 1 commit
  10. 15 Feb, 2014 1 commit
  11. 16 Oct, 2013 1 commit
  12. 27 Sep, 2013 1 commit
  13. 17 Jun, 2013 1 commit
  14. 11 Jun, 2013 1 commit
  15. 30 Apr, 2013 1 commit
  16. 12 Apr, 2013 1 commit
  17. 25 Mar, 2013 1 commit
    • Kenneth Heitke's avatar
      add single-wire serial bus interface (SSBI) driver · e44b0cee
      Kenneth Heitke authored
      SSBI is the Qualcomm single-wire serial bus interface used to connect
      the MSM devices to the PMIC and other devices.
      Since SSBI only supports a single slave, the driver gets the name of the
      slave device passed in from the board file through the master device's
      platform data.
      SSBI registers pretty early (postcore), so that the PMIC can come up
      before the board init. This is useful if the board init requires the
      use of gpios that are connected through the PMIC.
      Based on a patch by Dima Zavin <dima@android.com> that can be found at:
      This patch adds PMIC Arbiter support for the MSM8660. The PMIC Arbiter
      is a hardware wrapper around the SSBI 2.0 controller that is designed to
      overcome concurrency issues and security limitations.  A controller_type
      field is added to the platform data to specify the type of the SSBI
      controller (1.0, 2.0, or PMIC Arbiter).
       I've moved this driver into drivers/ssbi/ and added an include for
       linux/module.h so that it will compile]
      Signed-off-by: default avatarKenneth Heitke <kheitke@codeaurora.org>
      Signed-off-by: default avatarDavid Brown <davidb@codeaurora.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
  18. 01 Feb, 2013 1 commit
  19. 17 Jan, 2013 1 commit
    • Jon Mason's avatar
      PCI-Express Non-Transparent Bridge Support · fce8a7bb
      Jon Mason authored
      A PCI-Express non-transparent bridge (NTB) is a point-to-point PCIe bus
      connecting 2 systems, providing electrical isolation between the two subsystems.
      A non-transparent bridge is functionally similar to a transparent bridge except
      that both sides of the bridge have their own independent address domains.  The
      host on one side of the bridge will not have the visibility of the complete
      memory or I/O space on the other side of the bridge.  To communicate across the
      non-transparent bridge, each NTB endpoint has one (or more) apertures exposed to
      the local system.  Writes to these apertures are mirrored to memory on the
      remote system.  Communications can also occur through the use of doorbell
      registers that initiate interrupts to the alternate domain, and scratch-pad
      registers accessible from both sides.
      The NTB device driver is needed to configure these memory windows, doorbell, and
      scratch-pad registers as well as use them in such a way as they can be turned
      into a viable communication channel to the remote system.  ntb_hw.[ch]
      determines the usage model (NTB to NTB or NTB to Root Port) and abstracts away
      the underlying hardware to provide access and a common interface to the doorbell
      registers, scratch pads, and memory windows.  These hardware interfaces are
      exported so that other, non-mainlined kernel drivers can access these.
      ntb_transport.[ch] also uses the exported interfaces in ntb_hw.[ch] to setup a
      communication channel(s) and provide a reliable way of transferring data from
      one side to the other, which it then exports so that "client" drivers can access
      them.  These client drivers are used to provide a standard kernel interface
      (i.e., Ethernet device) to NTB, such that Linux can transfer data from one
      system to the other in a standard way.
      Signed-off-by: default avatarJon Mason <jon.mason@intel.com>
      Reviewed-by: default avatarNicholas Bellinger <nab@linux-iscsi.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
  20. 16 Nov, 2012 1 commit
  21. 19 Sep, 2012 1 commit
    • Simon Arlott's avatar
      ARM: bcm2835: add interrupt controller driver · 89214f00
      Simon Arlott authored
      The BCM2835 contains a custom interrupt controller, which supports 72
      interrupt sources using a 2-level register scheme. The interrupt
      controller, or the HW block containing it, is referred to occasionally
      as "armctrl" in the SoC documentation, hence the symbol naming in the
      This patch was extracted from git://github.com/lp0/linux.git branch
      rpi-split as of 2012/09/08, and modified as follows:
      * s/bcm2708/bcm2835/.
      * Modified device tree vendor prefix.
      * Moved implementation to drivers/irchip/.
      * Added devicetree documentation, and hence removed list of IRQs from
      * Changed shift in MAKE_HWIRQ() and HWIRQ_BANK() from 8 to 5 to reduce
        the size of the hwirq space, and pass the total size of the hwirq space
        to irq_domain_add_linear(), rather than just the number of valid hwirqs;
        the two are different due to the hwirq space being sparse.
      * Added the interrupt controller DT node to the top-level of the DT,
        rather than nesting it inside a /axi node. Hence, changed the reg value
        since /axi had a ranges property. This seems simpler to me, but I'm not
        sure if everyone will like this change or not.
      * Don't set struct irq_domain_ops.map = irq_domain_simple_map, hence
        removing the need to patch include/linux/irqdomain.h or
      * Simplified armctrl_of_init() using of_iomap().
      * Removed unused IS_VALID_BANK()/IS_VALID_IRQ() macros.
      * Renamed armctrl_handle_irq() to prevent possible symbol clashes.
      * Made armctrl_of_init() static.
      * Removed comment "Each bank is registered as a separate interrupt
        controller" since this is no longer true.
      * Removed FSF address from license header.
      * Added my name to copyright header.
      Signed-off-by: default avatarChris Boot <bootc@bootc.net>
      Signed-off-by: default avatarSimon Arlott <simon@fire.lp0.eu>
      Signed-off-by: default avatarDom Cobley <popcornmix@gmail.com>
      Signed-off-by: default avatarDom Cobley <dc4@broadcom.com>
      Signed-off-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      Acked-by: default avatarArnd Bergmann <arnd@arndb.de>
  22. 22 Aug, 2012 1 commit
  23. 31 Jul, 2012 1 commit
    • Alex Williamson's avatar
      vfio: VFIO core · cba3345c
      Alex Williamson authored
      VFIO is a secure user level driver for use with both virtual machines
      and user level drivers.  VFIO makes use of IOMMU groups to ensure the
      isolation of devices in use, allowing unprivileged user access.  It's
      intended that VFIO will replace KVM device assignment and UIO drivers
      (in cases where the target platform includes a sufficiently capable
      New in this version of VFIO is support for IOMMU groups managed
      through the IOMMU core as well as a rework of the API, removing the
      group merge interface.  We now go back to a model more similar to
      original VFIO with UIOMMU support where the file descriptor obtained
      from /dev/vfio/vfio allows access to the IOMMU, but only after a
      group is added, avoiding the previous privilege issues with this type
      of model.  IOMMU support is also now fully modular as IOMMUs have
      vastly different interface requirements on different platforms.  VFIO
      users are able to query and initialize the IOMMU model of their
      Please see the follow-on Documentation commit for further description
      and usage example.
      Signed-off-by: default avatarAlex Williamson <alex.williamson@redhat.com>
  24. 15 Jun, 2012 1 commit
    • Sascha Hauer's avatar
      pwm: Add PWM framework support · 0c2498f1
      Sascha Hauer authored
      This patch adds framework support for PWM (pulse width modulation) devices.
      The is a barebone PWM API already in the kernel under include/linux/pwm.h,
      but it does not allow for multiple drivers as each of them implements the
      pwm_*() functions.
      There are other PWM framework patches around from Bill Gatliff. Unlike
      his framework this one does not change the existing API for PWMs so that
      this framework can act as a drop in replacement for the existing API.
      Why another framework?
      Several people argue that there should not be another framework for PWMs
      but they should be integrated into one of the existing frameworks like led
      or hwmon. Unlike these frameworks the PWM framework is agnostic to the
      purpose of the PWM. In fact, a PWM can drive a LED, but this makes the
      LED framework a user of a PWM, like already done in leds-pwm.c. The gpio
      framework also is not suitable for PWMs. Every gpio could be turned into
      a PWM using timer based toggling, but on the other hand not every PWM hardware
      device can be turned into a gpio due to the lack of hardware capabilities.
      This patch does not try to improve the PWM API yet, this could be done in
      subsequent patches.
      Signed-off-by: default avatarSascha Hauer <s.hauer@pengutronix.de>
      Acked-by: default avatarKurt Van Dijck <kurt.van.dijck@eia.be>
      Reviewed-by: default avatarArnd Bergmann <arnd@arndb.de>
      Reviewed-by: default avatarMatthias Kaehlcke <matthias@kaehlcke.net>
      Reviewed-by: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      Reviewed-by: default avatarShawn Guo <shawn.guo@linaro.org>
      [thierry.reding@avionic-design.de: fixup typos, kerneldoc comments]
      Signed-off-by: default avatarThierry Reding <thierry.reding@avionic-design.de>
  25. 02 May, 2012 1 commit
  26. 26 Apr, 2012 1 commit
    • Greg Kroah-Hartman's avatar
      Staging: VME: move VME drivers out of staging · db3b9e99
      Greg Kroah-Hartman authored
      This moves the VME core, VME board drivers, and VME bridge drivers out
      of the drivers/staging/vme/ area to drivers/vme/.
      The VME device drivers have not moved out yet due to some API questions
      they are still working through, that should happen soon, hopefully.
      Cc: Martyn Welch <martyn.welch@ge.com>
      Cc: Manohar Vanga <manohar.vanga@cern.ch>
      Cc: Vincent Bossier <vincent.bossier@gmail.com>
      Cc: "Emilio G. Cota" <cota@braap.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
  27. 25 Apr, 2012 1 commit
  28. 20 Apr, 2012 1 commit
    • MyungJoo Ham's avatar
      Extcon (external connector): import Android's switch class and modify. · de55d871
      MyungJoo Ham authored
      External connector class (extcon) is based on and an extension of
      Android kernel's switch class located at linux/drivers/switch/.
      This patch provides the before-extension switch class moved to the
      location where the extcon will be located (linux/drivers/extcon/) and
      updates to handle class properly.
      The before-extension class, switch class of Android kernel, commits
      imported are:
      switch: switch class and GPIO drivers. (splitted)
      Author: Mike Lockwood <lockwood@android.com>
      switch: Use device_create instead of device_create_drvdata.
      Author: Arve Hjønnevåg <arve@android.com>
      In this patch, upon the commits of Android kernel, we have added:
      - Relocated and renamed for extcon.
      - Comments, module name, and author information are updated
      - Code clean for successing patches
      - Bugfix: enabling write access without write functions
      - Class/device/sysfs create/remove handling
      - Added comments about uevents
      - Format changes for extcon_dev_register() to have a parent dev.
      Signed-off-by: default avatarMyungJoo Ham <myungjoo.ham@samsung.com>
      Signed-off-by: default avatarKyungmin Park <kyungmin.park@samsung.com>
      Reviewed-by: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      Changes from v7
      - Compiler error fixed when it is compiled as a module.
      - Removed out-of-date Kconfig entry
      Changes from v6
      - Updated comment/strings
      - Revised "Android-compatible" mode.
         * Automatically activated if CONFIG_ANDROID && !CONFIG_ANDROID_SWITCH
         * Creates /sys/class/switch/*, which is a copy of /sys/class/extcon/*
      Changes from v5
      - Split the patch
      - Style fixes
      - "Android-compatible" mode is enabled by Kconfig option.
      Changes from v2
      - Updated name_show
      - Sysfs entries are handled by class itself.
      - Updated the method to add/remove devices for the class
      - Comments on uevent send
      - Able to become a module
      - Compatible with Android platform
      Changes from RFC
      - Renamed to extcon (external connector) from multistate switch
      - Added a seperated directory (drivers/extcon)
      - Added kerneldoc comments
      - Removed unused variables from extcon_gpio.c
      - Added ABI Documentation.
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
  29. 08 Feb, 2012 3 commits
    • Joe Perches's avatar
      telephony: Move to staging · 6222d7a1
      Joe Perches authored
      This stuff is really old and in quite poor shape.
      Does anyone still use it?
      If not, I think it's appropriate to let it simmer
      in staging for a few releases.
      Signed-off-by: default avatarJoe Perches <joe@perches.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
    • Ohad Ben-Cohen's avatar
      rpmsg: add virtio-based remote processor messaging bus · bcabbcca
      Ohad Ben-Cohen authored
      Add a virtio-based inter-processor communication bus, which enables
      kernel drivers to communicate with entities, running on remote
      processors, over shared memory using a simple messaging protocol.
      Every pair of AMP processors share two vrings, which are used to send
      and receive the messages over shared memory.
      The header of every message sent on the rpmsg bus contains src and dst
      addresses, which make it possible to multiplex several rpmsg channels on
      the same vring.
      Every rpmsg channel is a device on this bus. When a channel is added,
      and an appropriate rpmsg driver is found and probed, it is also assigned
      a local rpmsg address, which is then bound to the driver's callback.
      When inbound messages carry the local address of a bound driver,
      its callback is invoked by the bus.
      This patch provides a kernel interface only; user space interfaces
      will be later exposed by kernel users of this rpmsg bus.
      Designed with Brian Swetland <swetland@google.com>.
      Signed-off-by: default avatarOhad Ben-Cohen <ohad@wizery.com>
      Acked-by: Rusty Russell <rusty@rustcorp.com.au> (virtio_ids.h)
      Cc: Brian Swetland <swetland@google.com>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Grant Likely <grant.likely@secretlab.ca>
      Cc: Tony Lindgren <tony@atomide.com>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Cc: Greg KH <greg@kroah.com>
      Cc: Stephen Boyd <sboyd@codeaurora.org>
    • Ohad Ben-Cohen's avatar
      remoteproc: add framework for controlling remote processors · 400e64df
      Ohad Ben-Cohen authored
      Modern SoCs typically employ a central symmetric multiprocessing (SMP)
      application processor running Linux, with several other asymmetric
      multiprocessing (AMP) heterogeneous processors running different instances
      of operating system, whether Linux or any other flavor of real-time OS.
      Booting a remote processor in an AMP configuration typically involves:
      - Loading a firmware which contains the OS image
      - Allocating and providing it required system resources (e.g. memory)
      - Programming an IOMMU (when relevant)
      - Powering on the device
      This patch introduces a generic framework that allows drivers to do
      that. In the future, this framework will also include runtime power
      management and error recovery.
      Based on (but now quite far from) work done by Fernando Guzman Lugo
      ELF loader was written by Mark Grosen <mgrosen@ti.com>, based on
      msm's Peripheral Image Loader (PIL) by Stephen Boyd <sboyd@codeaurora.org>.
      Designed with Brian Swetland <swetland@google.com>.
      Signed-off-by: default avatarOhad Ben-Cohen <ohad@wizery.com>
      Acked-by: default avatarGrant Likely <grant.likely@secretlab.ca>
      Cc: Brian Swetland <swetland@google.com>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Tony Lindgren <tony@atomide.com>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Rusty Russell <rusty@rustcorp.com.au>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Cc: Greg KH <greg@kroah.com>
      Cc: Stephen Boyd <sboyd@codeaurora.org>
  30. 05 Jan, 2012 1 commit
  31. 26 Nov, 2011 1 commit
  32. 13 Oct, 2011 1 commit
    • Linus Walleij's avatar
      drivers: create a pin control subsystem · 2744e8af
      Linus Walleij authored
      This creates a subsystem for handling of pin control devices.
      These are devices that control different aspects of package
      Currently it handles pinmuxing, i.e. assigning electronic
      functions to groups of pins on primarily PGA and BGA type of
      chip packages which are common in embedded systems.
      The plan is to also handle other I/O pin control aspects
      such as biasing, driving, input properties such as
      schmitt-triggering, load capacitance etc within this
      subsystem, to remove a lot of ARM arch code as well as
      feature-creepy GPIO drivers which are implementing the same
      thing over and over again.
      This is being done to depopulate the arch/arm/* directory
      of such custom drivers and try to abstract the infrastructure
      they all need. See the Documentation/pinctrl.txt file that is
      part of this patch for more details.
      ChangeLog v1->v2:
      - Various minor fixes from Joe's and Stephens review comments
      - Added a pinmux_config() that can invoke custom configuration
        with arbitrary data passed in or out to/from the pinmux driver
      ChangeLog v2->v3:
      - Renamed subsystem folder to "pinctrl" since we will likely
        want to keep other pin control such as biasing in this
        subsystem too, so let us keep to something generic even though
        we're mainly doing pinmux now.
      - As a consequence, register pins as an abstract entity separate
        from the pinmux. The muxing functions will claim pins out of the
        pin pool and make sure they do not collide. Pins can now be
        named by the pinctrl core.
      - Converted the pin lookup from a static array into a radix tree,
        I agreed with Grant Likely to try to avoid any static allocation
        (which is crap for device tree stuff) so I just rewrote this
        to be dynamic, just like irq number descriptors. The
        platform-wide definition of number of pins goes away - this is
        now just the sum total of the pins registered to the subsystem.
      - Make sure mappings with only a function name and no device
        works properly.
      ChangeLog v3->v4:
      - Define a number space per controller instead of globally,
        Stephen and Grant requested the same thing so now maps need to
        define target controller, and the radix tree of pin descriptors
        is a property on each pin controller device.
      - Add a compulsory pinctrl device entry to the pinctrl mapping
        table. This must match the pinctrl device, like "pinctrl.0"
      - Split the file core.c in two: core.c and pinmux.c where the
        latter carry all pinmux stuff, the core is for generic pin
        control, and use local headers to access functionality between
        files. It is now possible to implement a "blank" pin controller
        without pinmux capabilities. This split will make new additions
        like pindrive.c, pinbias.c etc possible for combined drivers
        and chunks of functionality which is a GoodThing(TM).
      - Rewrite the interaction with the GPIO subsystem - the pin
        controller descriptor now handles this by defining an offset
        into the GPIO numberspace for its handled pin range. This is
        used to look up the apropriate pin controller for a GPIO pin.
        Then that specific GPIO range is matched 1-1 for the target
        controller instance.
      - Fixed a number of review comments from Joe Perches.
      - Broke out a header file pinctrl.h for the core pin handling
        stuff that will be reused by other stuff than pinmux.
      - Fixed some erroneous EXPORT() stuff.
      - Remove mispatched U300 Kconfig and Makefile entries
      - Fixed a number of review comments from Stephen Warren, not all
        of them - still WIP. But I think the new mapping that will
        specify which function goes to which pin mux controller address
        50% of your concerns (else beat me up).
      ChangeLog v4->v5:
      - Defined a "position" for each function, so the pin controller now
        tracks a function in a certain position, and the pinmux maps define
        what position you want the function in. (Feedback from Stephen
        Warren and Sascha Hauer).
      - Since we now need to request a combined function+position from
        the machine mapping table that connect mux settings to drivers,
        it was extended with a position field and a name field. The
        name field is now used if you e.g. need to switch between two
        mux map settings at runtime.
      - Switched from a class device to using struct bus_type for this
        subsystem. Verified sysfs functionality: seems to work fine.
        (Feedback from Arnd Bergmann and Greg Kroah-Hartman)
      - Define a per pincontroller list of GPIO ranges from the GPIO
        pin space that can be handled by the pin controller. These can
        be added one by one at runtime. (Feedback from Barry Song)
      - Expanded documentation of regulator_[get|enable|disable|put]
      - Fixed a number of review comments from Barry Song. (Thanks!)
      ChangeLog v5->v6:
      - Create an abstract pin group concept that can sort pins into
        named and enumerated groups no matter what the use of these
        groups may be, one possible usecase is a group of pins being
        muxed in or so. The intention is however to also use these
        groups for other pin control activities.
      - Make it compulsory for pinmux functions to associate with
        at least one group, so the abstract pin group concept is used
        to define the groups of pins affected by a pinmux function.
        The pinmux driver interface has been altered so as to enforce
        a function to list applicable groups per function.
      - Provide an optional .group entry in the pinmux machine map
        so the map can select beteween different available groups
        to be used with a certain function.
      - Consequent changes all over the place so that e.g. debugfs
        present reasonable information about the world.
      - Drop the per-pin mux (*config) function in the pinmux_ops
        struct - I was afraid that this would start to be used for
        things totally unrelated to muxing, we can introduce that to
        the generic struct pinctrl_ops if needed. I want to keep
        muxing orthogonal to other pin control subjects and not mix
        these things up.
      ChangeLog v6->v7:
      - Make it possible to have several map entries matching the
        same device, pin controller and function, but using
        a different group, and alter the semantics so that
        pinmux_get() will pick all matching map entries, and
        store the associated groups in a list. The list will
        then be iterated over at pinmux_enable()/pinmux_disable()
        and corresponding driver functions called for each
        defined group. Notice that you're only allowed to map
        multiple *groups* to the same
        { device, pin controller, function } triplet, attempts
        to map the same device to multiple pin controllers will
        for example fail. This is hopefully the crucial feature
        requested by Stephen Warren.
      - Add a pinmux hogging field to the pinmux mapping entries,
        and enable the pinmux core to hog pinmux map entries.
        This currently only works for pinmuxes without assigned
        devices as it looks now, but with device trees we can
        look up the corresponding struct device * entries when
        we register the pinmux driver, and have it hog each
        pinmux map in turn, for a simple approach to
        non-dynamic pin muxing. This addresses an issue from
        Grant Likely that the machine should take care of as
        much of the pinmux setup as possible, not the devices.
        By supplying a list of hogs, it can now instruct the
        core to take care of any static mappings.
      - Switch pinmux group retrieveal function to grab an
        array of strings representing the groups rather than an
        array of unsigned and rewrite accordingly.
      - Alter debugfs to show the grouplist handled by each
        pinmux. Also add a list of hogs.
      - Dynamically allocate a struct pinmux at pinmux_get() and
        free it at pinmux_put(), then add these to the global
        list of pinmuxes active as we go along.
      - Go over the list of pinmux maps at pinmux_get() time
        and repeatedly apply matches.
      - Retrieve applicable groups per function from the driver
        as a string array rather than a unsigned array, then
        lookup the enumerators.
      - Make the device to pinmux map a singleton - only allow the
        mapping table to be registered once and even tag the
        registration function with __init so it surely won't be
      - Create a separate debugfs file to view the pinmux map at
      - Introduce a spin lock to the pin descriptor struct, lock it
        when modifying pin status entries. Reported by Stijn Devriendt.
      - Fix up the documentation after review from Stephen Warren.
      - Let the GPIO ranges give names as const char * instead of some
        fixed-length string.
      - add a function to unregister GPIO ranges to mirror the
        registration function.
      - Privatized the struct pinctrl_device and removed it from the
        <linux/pinctrl/pinctrl.h> API, the drivers do not need to know
        the members of this struct. It is now in the local header
      - Rename the concept of "anonymous" mux maps to "system" muxes
        and add convenience macros and documentation.
      ChangeLog v7->v8:
      - Delete the leftover pinmux_config() function from the
       <linux/pinctrl/pinmux.h> header.
      - Fix a race condition found by Stijn Devriendt in pin_request()
      ChangeLog v8->v9:
      - Drop the bus_type and the sysfs attributes and all, we're not on
        the clear about how this should be used for e.g. userspace
        interfaces so let us save this for the future.
      - Use the right name in MAINTAINERS, PIN CONTROL rather than
      - Don't kfree() the device state holder, let the .remove() callback
        handle this.
      - Fix up numerous kerneldoc headers to have one line for the function
        description and more verbose documentation below the parameters
      ChangeLog v9->v10:
      - pinctrl: EXPORT_SYMBOL needs export.h, folded in a patch
        from Steven Rothwell
      - fix pinctrl_register error handling, folded in a patch from
        Axel Lin
      - Various fixes to documentation text so that it's consistent.
      - Removed pointless comment from drivers/Kconfig
      - Removed dependency on SYSFS since we removed the bus in
      - Renamed hopelessly abbreviated pctldev_* functions to the
        more verbose pinctrl_dev_*
      - Drop mutex properly when looking up GPIO ranges
      - Return NULL instead of ERR_PTR() errors on registration of
        pin controllers, using cast pointers is fragile. We can
        live without the detailed error codes for sure.
      Cc: Stijn Devriendt <highguy@gmail.com>
      Cc: Joe Perches <joe@perches.com>
      Cc: Russell King <linux@arm.linux.org.uk>
      Acked-by: default avatarGrant Likely <grant.likely@secretlab.ca>
      Acked-by: default avatarStephen Warren <swarren@nvidia.com>
      Tested-by: default avatarBarry Song <21cnbao@gmail.com>
      Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
  33. 10 Oct, 2011 1 commit
  34. 01 Oct, 2011 1 commit
    • MyungJoo Ham's avatar
      PM: Introduce devfreq: generic DVFS framework with device-specific OPPs · a3c98b8b
      MyungJoo Ham authored
      With OPPs, a device may have multiple operable frequency and voltage
      sets. However, there can be multiple possible operable sets and a system
      will need to choose one from them. In order to reduce the power
      consumption (by reducing frequency and voltage) without affecting the
      performance too much, a Dynamic Voltage and Frequency Scaling (DVFS)
      scheme may be used.
      This patch introduces the DVFS capability to non-CPU devices with OPPs.
      DVFS is a techique whereby the frequency and supplied voltage of a
      device is adjusted on-the-fly. DVFS usually sets the frequency as low
      as possible with given conditions (such as QoS assurance) and adjusts
      voltage according to the chosen frequency in order to reduce power
      consumption and heat dissipation.
      The generic DVFS for devices, devfreq, may appear quite similar with
      /drivers/cpufreq.  However, cpufreq does not allow to have multiple
      devices registered and is not suitable to have multiple heterogenous
      devices with different (but simple) governors.
      Normally, DVFS mechanism controls frequency based on the demand for
      the device, and then, chooses voltage based on the chosen frequency.
      devfreq also controls the frequency based on the governor's frequency
      recommendation and let OPP pick up the pair of frequency and voltage
      based on the recommended frequency. Then, the chosen OPP is passed to
      device driver's "target" callback.
      When PM QoS is going to be used with the devfreq device, the device
      driver should enable OPPs that are appropriate with the current PM QoS
      requests. In order to do so, the device driver may call opp_enable and
      opp_disable at the notifier callback of PM QoS so that PM QoS's
      update_target() call enables the appropriate OPPs. Note that at least
      one of OPPs should be enabled at any time; be careful when there is a
      Signed-off-by: default avatarMyungJoo Ham <myungjoo.ham@samsung.com>
      Signed-off-by: default avatarKyungmin Park <kyungmin.park@samsung.com>
      Reviewed-by: default avatarMike Turquette <mturquette@ti.com>
      Acked-by: default avatarKevin Hilman <khilman@ti.com>
      Signed-off-by: default avatarRafael J. Wysocki <rjw@sisk.pl>
  35. 23 Jul, 2011 1 commit
    • Ohad Ben-Cohen's avatar
      virtio: expose for non-virtualization users too · e7254219
      Ohad Ben-Cohen authored
      virtio has been so far used only in the context of virtualization,
      and the virtio Kconfig was sourced directly by the relevant arch
      Kconfigs when VIRTUALIZATION was selected.
      Now that we start using virtio for inter-processor communications,
      we need to source the virtio Kconfig outside of the virtualization
      scope too.
      Moreover, some architectures might use virtio for both virtualization
      and inter-processor communications, so directly sourcing virtio
      might yield unexpected results due to conflicting selections.
      The simple solution offered by this patch is to always source virtio's
      Kconfig in drivers/Kconfig, and remove it from the appropriate arch
      Kconfigs. Additionally, a virtio menu entry has been added so virtio
      drivers don't show up in the general drivers menu.
      This way anyone can use virtio, though it's arguably less accessible
      (and neat!) for virtualization users now.
      Note: some architectures (mips and sh) seem to have a VIRTUALIZATION
      menu merely for sourcing virtio's Kconfig, so that menu is removed too.
      Signed-off-by: default avatarOhad Ben-Cohen <ohad@wizery.com>
      Signed-off-by: default avatarRusty Russell <rusty@rustcorp.com.au>
  36. 07 Jul, 2011 1 commit
    • Timur Tabi's avatar
      drivers/virt: introduce Freescale hypervisor management driver · 6db71994
      Timur Tabi authored
      Add the drivers/virt directory, which houses drivers that support
      virtualization environments, and add the Freescale hypervisor management
      The Freescale hypervisor management driver provides several services to
      drivers and applications related to the Freescale hypervisor:
      1. An ioctl interface for querying and managing partitions
      2. A file interface to reading incoming doorbells
      3. An interrupt handler for shutting down the partition upon receiving the
         shutdown doorbell from a manager partition
      4. A kernel interface for receiving callbacks when a managed partition
         shuts down.
      Signed-off-by: default avatarTimur Tabi <timur@freescale.com>
      Acked-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarKumar Gala <galak@kernel.crashing.org>
  37. 05 Jul, 2011 1 commit
  38. 14 Jun, 2011 1 commit