)]}'
{
  "log": [
    {
      "commit": "0d2006bbf09e817f125ba1e42b2549bc2c5d7351",
      "tree": "f452f0a77705139763448c5676f6118270285439",
      "parents": [
        "706e8520e8450a631ca6f798f8c811faf56f0a59"
      ],
      "author": {
        "name": "Chanho Park",
        "email": "chanho61.park@samsung.com",
        "time": "Tue Jan 03 16:47:51 2012 +0900"
      },
      "committer": {
        "name": "Linus Walleij",
        "email": "linus.walleij@linaro.org",
        "time": "Tue Jan 03 09:10:09 2012 +0100"
      },
      "message": "pinctrl: remove unnecessary max pin number\n\nThis patch removes maxpin member in the pin control descriptor\nbecause we don\u0027t need this value as we enumerate a pin space\nusing offset.\n\nSigned-off-by: Chanho Park \u003cchanho61.park@samsung.com\u003e\nSigned-off-by: Kyungmin Park \u003ckyungmin.park@samsung.com\u003e\nSigned-off-by: Linus Walleij \u003clinus.walleij@linaro.org\u003e\n"
    },
    {
      "commit": "43699dea1ea21a0d5786317a794cb2ba27a6f4fe",
      "tree": "6a1f26cce9cfe04ac93cd62005c14759722ffb74",
      "parents": [
        "63fd5984a9b2214cba7dd7dd7b5a75cf40dde39f"
      ],
      "author": {
        "name": "Stephen Warren",
        "email": "swarren@nvidia.com",
        "time": "Thu Dec 15 16:57:17 2011 -0700"
      },
      "committer": {
        "name": "Linus Walleij",
        "email": "linus.walleij@linaro.org",
        "time": "Tue Jan 03 09:10:07 2012 +0100"
      },
      "message": "pinctrl: pass name instead of device to pin_config_*\n\nObtaining a \"struct pinctrl_dev *\" is difficult for code not directly\nrelated to the pinctrl subsystem. However, the device name of the pinctrl\ndevice is fairly well known. So, modify pin_config_*() to take the device\nname instead of the \"struct pinctrl_dev *\".\n\nSigned-off-by: Stephen Warren \u003cswarren@nvidia.com\u003e\n[rebased on top of refactoring code]\nSigned-off-by: Linus Walleij \u003clinus.walleij@linaro.org\u003e\n"
    },
    {
      "commit": "63fd5984a9b2214cba7dd7dd7b5a75cf40dde39f",
      "tree": "1e5e59227b98df62920896db2aa9da613c288f6f",
      "parents": [
        "ca53c5f1ca5c936777caca46b7c716a40682ce83"
      ],
      "author": {
        "name": "Stephen Warren",
        "email": "swarren@nvidia.com",
        "time": "Thu Dec 15 16:57:16 2011 -0700"
      },
      "committer": {
        "name": "Linus Walleij",
        "email": "linus.walleij@linaro.org",
        "time": "Tue Jan 03 09:10:07 2012 +0100"
      },
      "message": "pinctrl: add \"struct seq_file;\" to pinconf.h\n\nThis allows one to include pinconf.h without having to include other\nheaders first.\n\nSigned-off-by: Stephen Warren \u003cswarren@nvidia.com\u003e\nSigned-off-by: Linus Walleij \u003clinus.walleij@linaro.org\u003e\n"
    },
    {
      "commit": "23750196ef472e9249958d5165b0bb292518c710",
      "tree": "8c49d754f8291bff02ef124a44bbc3bd94c10160",
      "parents": [
        "51cd24ee625c348654114032499914d0311e5832"
      ],
      "author": {
        "name": "Linus Walleij",
        "email": "linus.walleij@linaro.org",
        "time": "Wed Dec 14 09:30:08 2011 +0100"
      },
      "committer": {
        "name": "Linus Walleij",
        "email": "linus.walleij@linaro.org",
        "time": "Tue Jan 03 09:10:06 2012 +0100"
      },
      "message": "pinctrl: add a group-specific hog macro\n\nTo create elegant tables for pinmux hogs on the PXA MMP platform,\nwe need this hog macro that can specify both function and group in\none go.\n\nAcked-by: Stephen Warren \u003cswarren@nvidia.com\u003e\nAcked-by: Haojian Zhuang \u003chaojian.zhuang@gmail.com\u003e\nSigned-off-by: Linus Walleij \u003clinus.walleij@linaro.org\u003e\n"
    },
    {
      "commit": "51cd24ee625c348654114032499914d0311e5832",
      "tree": "7483fbdc4db119f9a8f013035005f374e729ffd0",
      "parents": [
        "528b78306ecf82af06c4862aa5518643fe20a440"
      ],
      "author": {
        "name": "Stephen Warren",
        "email": "swarren@nvidia.com",
        "time": "Fri Dec 09 16:59:05 2011 -0700"
      },
      "committer": {
        "name": "Linus Walleij",
        "email": "linus.walleij@linaro.org",
        "time": "Tue Jan 03 09:10:06 2012 +0100"
      },
      "message": "pinctrl: don\u0027t create a device for each pin controller\n\nPin controllers should already be instantiated as a device, so there\u0027s\nno need for the pinctrl core to create a new struct device for each\ncontroller.\n\nThis allows the controller\u0027s real name to be used in the mux mapping\ntable, rather than e.g. \"pinctrl.0\", \"pinctrl.1\", etc.\n\nThis necessitates removal of the PINMUX_MAP_PRIMARY*() macros, since\ntheir sole purpose was to hard-code the .ctrl_dev_name field to be\n\"pinctrl.0\".\n\nSigned-off-by: Stephen Warren \u003cswarren@nvidia.com\u003e\nSigned-off-by: Linus Walleij \u003clinus.walleij@linaro.org\u003e\n"
    },
    {
      "commit": "1ddb6ff03c0cdec58c6cfdbada95acddcce4a7b7",
      "tree": "7bfc08fd3fb424f7faeefdcd5f60afba9d9954b2",
      "parents": [
        "ae6b4d8588f4fc95520b0e62c4b1f474c82191a9"
      ],
      "author": {
        "name": "Stephen Warren",
        "email": "swarren@nvidia.com",
        "time": "Fri Dec 09 16:59:03 2011 -0700"
      },
      "committer": {
        "name": "Linus Walleij",
        "email": "linus.walleij@linaro.org",
        "time": "Tue Jan 03 09:10:05 2012 +0100"
      },
      "message": "pinctrl: implement PINMUX_MAP_SYS_HOG\n\nThis is the same as PINMUX_MAP_PRIMARY_SYS_HOG, except that it allows\nyou to specify a particular control device.\n\nSigned-off-by: Stephen Warren \u003cswarren@nvidia.com\u003e\nSigned-off-by: Linus Walleij \u003clinus.walleij@linaro.org\u003e\n"
    },
    {
      "commit": "ae6b4d8588f4fc95520b0e62c4b1f474c82191a9",
      "tree": "3da8e553a6374f02e89b5a6ba52b83f34c3abea2",
      "parents": [
        "b4e3ac74d5cd4152f2ec6b3280b1ff3428952f7f"
      ],
      "author": {
        "name": "Linus Walleij",
        "email": "linus.walleij@linaro.org",
        "time": "Wed Oct 19 18:14:33 2011 +0200"
      },
      "committer": {
        "name": "Linus Walleij",
        "email": "linus.walleij@linaro.org",
        "time": "Tue Jan 03 09:10:04 2012 +0100"
      },
      "message": "pinctrl: add a pin config interface\n\nThis add per-pin and per-group pin config interfaces for biasing,\ndriving and other such electronic properties. The details of passed\nconfigurations are passed in an opaque unsigned long which may be\ndereferences to integer types, structs or lists on either side\nof the configuration interface.\n\nChangeLog v1-\u003ev2:\n- Clear split of terminology: we now have pin controllers, and\n  those may support two interfaces using vtables: pin\n  multiplexing and pin configuration.\n- Break out pin configuration to its own C file, controllers may\n  implement only config without mux, and vice versa, so keep each\n  sub-functionality of pin controllers separate. Introduce\n  CONFIG_PINCONF in Kconfig.\n- Implement some core logic around pin configuration in the\n  pinconf.c file.\n- Remove UNKNOWN config states, these were just surplus baggage.\n- Remove FLOAT config state - HIGH_IMPEDANCE should be enough for\n  everyone.\n- PIN_CONFIG_POWER_SOURCE added to handle switching the power\n  supply for the pin logic between different sources\n- Explicit DISABLE config enums to turn schmitt-trigger,\n  wakeup etc OFF.\n- Update documentation to reflect all the recent reasoning.\nChangeLog v2-\u003ev3:\n- Twist API around to pass around arrays of config tuples instead\n  of (param, value) pairs everywhere.\n- Explicit drive strength semantics for push/pull and similar\n  drive modes, this shall be the number of drive stages vs\n  nominal load impedance, which should match the actual\n  electronics used in push/pull CMOS or TTY totempoles.\n- Drop load capacitance configuration - I probably don\u0027t know\n  what I\u0027m doing here so leave it out.\n- Drop PIN_CONFIG_INPUT_SCHMITT_OFF, instead the argument zero to\n  PIN_CONFIG_INPUT_SCHMITT turns schmitt trigger off.\n- Drop PIN_CONFIG_NORMAL_POWER_MODE and have a well defined\n  argument to PIN_CONFIG_LOW_POWER_MODE to get out of it instead.\n- Drop PIN_CONFIG_WAKEUP_ENABLE/DISABLE and just use\n  PIN_CONFIG_WAKEUP with defined value zero to turn wakeup off.\n- Add PIN_CONFIG_INPUT_DEBOUNCE for configuring debounce time\n  on input lines.\n- Fix a bug when we tried to configure pins for pin controllers\n  without pinconf support.\n- Initialized debugfs properly so it works.\n- Initialize the mutex properly and lock around config tampering\n  sections.\n- Check the return value from get_initial_config() properly.\nChangeLog v3-\u003ev4:\n- Export the pin_config_get(), pin_config_set() and\n  pin_config_group() functions.\n- Drop the entire concept of just getting initial config and\n  keeping track of pin states internally, instead ask the pins\n  what state they are in. Previous idea was plain wrong, if the\n  device cannot keep track of its state, the driver should do\n  it.\n- Drop the generic configuration layout, it seems this impose\n  too much restriction on some pin controllers, so let them do\n  things the way they want and split off support for generic\n  config as an optional add-on.\nChangeLog v4-\u003ev5:\n- Introduce two symmetric driver calls for group configuration,\n  .pin_config_group_[get|set] and corresponding external calls.\n- Remove generic semantic meanings of return values from config\n  calls, these belong in the generic config patch. Just pass the\n  return value through instead.\n- Add a debugfs entry \"pinconf-groups\" to read status from group\n  configuration only, also slam in a per-group debug callback in\n  the pinconf_ops so custom drivers can display something\n  meaningful for their pins.\n- Fix some dangling newline.\n- Drop dangling #else clause.\n- Update documentation to match the above.\nChangeLog v5-\u003ev6:\n- Change to using a pin name as parameter for the\n  [get|set]_config() functions, as suggested by Stephen Warren.\n  This is more natural as names will be what a developer has\n  access to in written documentation etc.\nChangeLog v6-\u003ev7:\n- Refactor out by-pin and by-name get/set functions, only expose\n  the by-name functions externally, expose the by-pin functions\n  internally.\n- Show supported pin control functionality in the debugfs\n  pinctrl-devices file.\n\nAcked-by: Stephen Warren \u003cswarren@nvidia.com\u003e\nSigned-off-by: Linus Walleij \u003clinus.walleij@linaro.org\u003e\n"
    },
    {
      "commit": "97607d157c133ab18dfcd77fa836e37fa950a44a",
      "tree": "f9ac62a9534295f24ab40a2890bfd285bc157a03",
      "parents": [
        "542e704f3ffee1dc4539c9e8191e4dc215220f5e"
      ],
      "author": {
        "name": "Linus Walleij",
        "email": "linus.walleij@linaro.org",
        "time": "Tue Nov 29 12:52:39 2011 +0100"
      },
      "committer": {
        "name": "Linus Walleij",
        "email": "linus.walleij@linaro.org",
        "time": "Tue Jan 03 09:10:02 2012 +0100"
      },
      "message": "pinctrl: make a copy of pinmux map\n\nThis makes a deep copy of the pinmux function map instead of\nkeeping the copy supplied from the platform around. This makes\nit possible to tag the platforms map with __initdata as is also\ndone as part of this patch.\n\nRationale: a certain target platform (PXA) has numerous\npinmux maps, many of which will be lying around unused after\nboot in a multi-platform binary. Instead, deep-copy the one\nwe\u0027re going to use and tag them all __initdata so they go away\nafter boot.\n\nChangeLog v1-\u003ev2:\n- Fixup the deep copy, missed a few items on the struct,\n  plus mark bool member non-const since we\u0027re making runtime\n  copies if this stuff now.\nChangeLog v2-\u003ev3:\n- Make a shallow copy (just copy the array of map structs)\n  as Arnd noticed, string constants never get discarded by the\n  kernel anyway, so these pointers may be safely copied over.\n\nReviewed-by: Arnd Bergmann \u003carnd.bergmann@linaro.org\u003e\nSigned-off-by: Linus Walleij \u003clinus.walleij@linaro.org\u003e\n"
    },
    {
      "commit": "542e704f3ffee1dc4539c9e8191e4dc215220f5e",
      "tree": "da2f8aae8bedb6e3216b4808dc743eb94c3270e3",
      "parents": [
        "75d6642a3ee1dfe2552028997cdcc2c4207bec8f"
      ],
      "author": {
        "name": "Linus Walleij",
        "email": "linus.walleij@linaro.org",
        "time": "Mon Nov 14 10:06:22 2011 +0100"
      },
      "committer": {
        "name": "Linus Walleij",
        "email": "linus.walleij@linaro.org",
        "time": "Tue Jan 03 09:10:01 2012 +0100"
      },
      "message": "pinctrl: GPIO direction support for muxing\n\nWhen requesting a single GPIO pin to be muxed in, some controllers\nwill need to poke a different value into the control register\ndepending on whether the pin will be used for GPIO output or GPIO\ninput. So create pinmux counterparts to gpio_direction_[input|output]\nin the pinctrl framework.\n\nChangeLog v1-\u003ev2:\n- This also amends the documentation to make it clear the this\n  function and associated machinery is *ONLY* intended as a backend\n  to gpiolib machinery, not for everyone and his dog to start playing\n  around with pins.\nChangeLog v2-\u003ev3:\n- Don\u0027t pass an argument to the common request function, instead\n  provide pinmux_* counterparts to the gpio_direction_[input|output]\n  calls, simpler and anyone can understand it.\nChangeLog v3-\u003ev4:\n- Fix numerous spelling mistakes and dangling text in documentation.\n  Add Ack and Rewewed-by.\n\nCc: Igor Grinberg \u003cgrinberg@compulab.co.il\u003e\nAcked-by: Stephen Warren \u003cswarren@nvidia.com\u003e\nReviewed-by: Thomas Abraham \u003cthomas.abraham@linaro.org\u003e\nSigned-off-by: Linus Walleij \u003clinus.walleij@linaro.org\u003e\n"
    },
    {
      "commit": "3c739ad0df5eb41cd7adad879eda6aa09879eb76",
      "tree": "4ab739e639373a18ca993b26b6c18ace7edee9e2",
      "parents": [
        "33d58949adee5086478e140751e4a7263bd7e207"
      ],
      "author": {
        "name": "Chanho Park",
        "email": "chanho61.park@samsung.com",
        "time": "Fri Nov 11 18:47:58 2011 +0900"
      },
      "committer": {
        "name": "Linus Walleij",
        "email": "linus.walleij@linaro.org",
        "time": "Tue Jan 03 09:10:01 2012 +0100"
      },
      "message": "pinctrl: add a pin_base for sparse gpio-ranges\n\nThis patch enables mapping a base offset of gpio ranges with\na pin offset even if does\u0027nt matched. A base of pinctrl_gpio_range\nmeans a base offset of gpio. However, we cannot convert gpio to pin\nnumber for sparse gpio ranges just only using a gpio base offset.\nWe can convert a gpio to real pin number(even if not matched) using\na new pin_base which means a base pin offset of requested gpio range.\nNow, the pin control subsystem passes the pin base offset to the\npinmux driver.\n\nFor example, let\u0027s assume below two gpio ranges in the system.\n\nstatic struct pinctrl_gpio_range gpio_range_a \u003d {\n    .name \u003d \"chip a\",\n    .id \u003d 0,\n    .base \u003d 32,\n    .pin_base \u003d 32,\n    .npins \u003d 16,\n    .gc \u003d \u0026chip_a;\n};\n\nstatic struct pinctrl_gpio_range gpio_range_b \u003d {\n    .name \u003d \"chip b\",\n    .id \u003d 0,\n    .base \u003d 48,\n    .pin_base \u003d 64,\n    .npins \u003d 8,\n    .gc \u003d \u0026chip_b;\n};\n\nWe can calucalate a exact pin ranges even if doesn\u0027t matched with gpio ranges.\n\nchip a:\n    gpio-range : [32 .. 47]\n    pin-range  : [32 .. 47]\nchip b:\n    gpio-range : [48 .. 55]\n    pin-range  : [64 .. 71]\n\nSigned-off-by: Chanho Park \u003cchanho61.park@samsung.com\u003e\nSigned-off-by: Kyungmin Park \u003ckyungmin.park@samsung.com\u003e\nSigned-off-by: Linus Walleij \u003clinus.walleij@linaro.org\u003e\n"
    },
    {
      "commit": "3712a3c488987849613a4ad74129e67e40b12b38",
      "tree": "c3b155ed171bb0542d6ea4b18dcfc3d279ee610f",
      "parents": [
        "d2f6a1c6fb0e510a24ccac066eefbcfd0c932858"
      ],
      "author": {
        "name": "Stephen Warren",
        "email": "swarren@nvidia.com",
        "time": "Fri Oct 21 12:25:53 2011 -0600"
      },
      "committer": {
        "name": "Linus Walleij",
        "email": "linus.walleij@linaro.org",
        "time": "Tue Jan 03 09:09:59 2012 +0100"
      },
      "message": "pinctrl: add explicit gpio_disable_free pinmux_op\n\nSome pinctrl drivers (Tegra at least) program a pin to be a GPIO in a\ncompletely different manner than they select which function to mux out of\nthat pin. In order to support a single \"free\" pinmux_op, the driver would\nneed to maintain a per-pin state of requested-for-gpio vs. requested-for-\nfunction. However, that\u0027s a lot of work when the core already has explicit\nseparate paths for gpio request/free and function request/free.\n\nSo, add a gpio_disable_free op to struct pinmux_ops, and make pin_free()\ncall it when appropriate.\n\nWhen doing this, I noticed that when calling pin_request():\n\n    !!gpio \u003d\u003d (gpio_range !\u003d NULL)\n\n... and so I collapsed those two parameters in both pin_request(), and\nwhen adding writing the new code in pin_free().\n\nAlso, for pin_free():\n\n    !!free_func \u003d\u003d (gpio_range !\u003d NULL)\n\nHowever, I didn\u0027t want pin_free() to know about the GPIO function naming\nspecial case, so instead, I reworked pin_free() to always return the pin\u0027s\npreviously requested function, and now pinmux_free_gpio() calls\nkfree(function). This is much more balanced with the allocation having\nbeen performed in pinmux_request_gpio().\n\nSigned-off-by: Stephen Warren \u003cswarren@nvidia.com\u003e\nSigned-off-by: Linus Walleij \u003clinus.walleij@linaro.org\u003e\n"
    },
    {
      "commit": "e0e20753c15fc418d94fee826af394907df856d8",
      "tree": "e503026776ba7e593f15f39c3c03999f1136d9bc",
      "parents": [
        "1ea6b8f48918282bdca0b32a34095504ee65bab5"
      ],
      "author": {
        "name": "Barry Song",
        "email": "Baohua.Song@csr.com",
        "time": "Thu Oct 27 20:38:24 2011 -0700"
      },
      "committer": {
        "name": "Linus Walleij",
        "email": "linus.walleij@linaro.org",
        "time": "Wed Nov 09 15:07:40 2011 +0100"
      },
      "message": "pinctrl: fix \"warning: \u0027struct pinctrl_dev\u0027 declared inside parameter list\"\n\nwhen pinctl subsystem is not selected, when compiling drivers including\nthe include/linux/pinctrl/pinctrl.h, we will get the warning as below:\nIn file included from include/linux/pinctrl/pinmux.h:17,\n                 from drivers/tty/serial/sirfsoc_uart.c:25:\ninclude/linux/pinctrl/pinctrl.h:126: warning: \u0027struct pinctrl_dev\u0027\n\t\tdeclared inside parameter list\ninclude/linux/pinctrl/pinctrl.h:126: warning: its scope is only this\n      definition or declaration, which is probably not what you want\n\nSigned-off-by: Barry Song \u003cBaohua.Song@csr.com\u003e\nSigned-off-by: Linus Walleij \u003clinus.walleij@linaro.org\u003e\n"
    },
    {
      "commit": "a5818a8bd095a08cfb1871b63af9c8bed103e4b9",
      "tree": "7fc2ade1186cc42877f21a0eead3843515b914be",
      "parents": [
        "393daa814f4bbc6f5c099178c073fae9f7ef6177"
      ],
      "author": {
        "name": "Stephen Warren",
        "email": "swarren@nvidia.com",
        "time": "Wed Oct 19 16:19:25 2011 -0600"
      },
      "committer": {
        "name": "Linus Walleij",
        "email": "linus.walleij@linaro.org",
        "time": "Thu Oct 20 11:41:49 2011 +0200"
      },
      "message": "pinctrl: get_group_pins() const fixes\n\nget_group_pins() \"returns\" a pointer to an array of const objects, through\na pointer parameter. Fix the prototype so what\u0027s pointed at by the returned\npointer is const, rather than the function parameter being const.\n\nThis also allows the removal of a cast in each of the two current pinmux\ndrivers.\n\nSigned-off-by: Stephen Warren \u003cswarren@nvidia.com\u003e\nSigned-off-by: Linus Walleij \u003clinus.walleij@linaro.org\u003e\n"
    },
    {
      "commit": "2744e8afb3b76343e7eb8197e8b3e085036010a5",
      "tree": "2a96122ef4a6114483bda0fe9696d61a6e6f1bb5",
      "parents": [
        "a102a9ece5489e1718cd7543aa079082450ac3a2"
      ],
      "author": {
        "name": "Linus Walleij",
        "email": "linus.walleij@linaro.org",
        "time": "Mon May 02 20:50:54 2011 +0200"
      },
      "committer": {
        "name": "Linus Walleij",
        "email": "linus.walleij@stericsson.com",
        "time": "Thu Oct 13 12:49:17 2011 +0200"
      },
      "message": "drivers: create a pin control subsystem\n\nThis creates a subsystem for handling of pin control devices.\nThese are devices that control different aspects of package\npins.\n\nCurrently it handles pinmuxing, i.e. assigning electronic\nfunctions to groups of pins on primarily PGA and BGA type of\nchip packages which are common in embedded systems.\n\nThe plan is to also handle other I/O pin control aspects\nsuch as biasing, driving, input properties such as\nschmitt-triggering, load capacitance etc within this\nsubsystem, to remove a lot of ARM arch code as well as\nfeature-creepy GPIO drivers which are implementing the same\nthing over and over again.\n\nThis is being done to depopulate the arch/arm/* directory\nof such custom drivers and try to abstract the infrastructure\nthey all need. See the Documentation/pinctrl.txt file that is\npart of this patch for more details.\n\nChangeLog v1-\u003ev2:\n\n- Various minor fixes from Joe\u0027s and Stephens review comments\n- Added a pinmux_config() that can invoke custom configuration\n  with arbitrary data passed in or out to/from the pinmux driver\n\nChangeLog v2-\u003ev3:\n\n- Renamed subsystem folder to \"pinctrl\" since we will likely\n  want to keep other pin control such as biasing in this\n  subsystem too, so let us keep to something generic even though\n  we\u0027re mainly doing pinmux now.\n- As a consequence, register pins as an abstract entity separate\n  from the pinmux. The muxing functions will claim pins out of the\n  pin pool and make sure they do not collide. Pins can now be\n  named by the pinctrl core.\n- Converted the pin lookup from a static array into a radix tree,\n  I agreed with Grant Likely to try to avoid any static allocation\n  (which is crap for device tree stuff) so I just rewrote this\n  to be dynamic, just like irq number descriptors. The\n  platform-wide definition of number of pins goes away - this is\n  now just the sum total of the pins registered to the subsystem.\n- Make sure mappings with only a function name and no device\n  works properly.\n\nChangeLog v3-\u003ev4:\n\n- Define a number space per controller instead of globally,\n  Stephen and Grant requested the same thing so now maps need to\n  define target controller, and the radix tree of pin descriptors\n  is a property on each pin controller device.\n- Add a compulsory pinctrl device entry to the pinctrl mapping\n  table. This must match the pinctrl device, like \"pinctrl.0\"\n- Split the file core.c in two: core.c and pinmux.c where the\n  latter carry all pinmux stuff, the core is for generic pin\n  control, and use local headers to access functionality between\n  files. It is now possible to implement a \"blank\" pin controller\n  without pinmux capabilities. This split will make new additions\n  like pindrive.c, pinbias.c etc possible for combined drivers\n  and chunks of functionality which is a GoodThing(TM).\n- Rewrite the interaction with the GPIO subsystem - the pin\n  controller descriptor now handles this by defining an offset\n  into the GPIO numberspace for its handled pin range. This is\n  used to look up the apropriate pin controller for a GPIO pin.\n  Then that specific GPIO range is matched 1-1 for the target\n  controller instance.\n- Fixed a number of review comments from Joe Perches.\n- Broke out a header file pinctrl.h for the core pin handling\n  stuff that will be reused by other stuff than pinmux.\n- Fixed some erroneous EXPORT() stuff.\n- Remove mispatched U300 Kconfig and Makefile entries\n- Fixed a number of review comments from Stephen Warren, not all\n  of them - still WIP. But I think the new mapping that will\n  specify which function goes to which pin mux controller address\n  50% of your concerns (else beat me up).\n\nChangeLog v4-\u003ev5:\n\n- Defined a \"position\" for each function, so the pin controller now\n  tracks a function in a certain position, and the pinmux maps define\n  what position you want the function in. (Feedback from Stephen\n  Warren and Sascha Hauer).\n- Since we now need to request a combined function+position from\n  the machine mapping table that connect mux settings to drivers,\n  it was extended with a position field and a name field. The\n  name field is now used if you e.g. need to switch between two\n  mux map settings at runtime.\n- Switched from a class device to using struct bus_type for this\n  subsystem. Verified sysfs functionality: seems to work fine.\n  (Feedback from Arnd Bergmann and Greg Kroah-Hartman)\n- Define a per pincontroller list of GPIO ranges from the GPIO\n  pin space that can be handled by the pin controller. These can\n  be added one by one at runtime. (Feedback from Barry Song)\n- Expanded documentation of regulator_[get|enable|disable|put]\n  semantics.\n- Fixed a number of review comments from Barry Song. (Thanks!)\n\nChangeLog v5-\u003ev6:\n\n- Create an abstract pin group concept that can sort pins into\n  named and enumerated groups no matter what the use of these\n  groups may be, one possible usecase is a group of pins being\n  muxed in or so. The intention is however to also use these\n  groups for other pin control activities.\n- Make it compulsory for pinmux functions to associate with\n  at least one group, so the abstract pin group concept is used\n  to define the groups of pins affected by a pinmux function.\n  The pinmux driver interface has been altered so as to enforce\n  a function to list applicable groups per function.\n- Provide an optional .group entry in the pinmux machine map\n  so the map can select beteween different available groups\n  to be used with a certain function.\n- Consequent changes all over the place so that e.g. debugfs\n  present reasonable information about the world.\n- Drop the per-pin mux (*config) function in the pinmux_ops\n  struct - I was afraid that this would start to be used for\n  things totally unrelated to muxing, we can introduce that to\n  the generic struct pinctrl_ops if needed. I want to keep\n  muxing orthogonal to other pin control subjects and not mix\n  these things up.\n\nChangeLog v6-\u003ev7:\n\n- Make it possible to have several map entries matching the\n  same device, pin controller and function, but using\n  a different group, and alter the semantics so that\n  pinmux_get() will pick all matching map entries, and\n  store the associated groups in a list. The list will\n  then be iterated over at pinmux_enable()/pinmux_disable()\n  and corresponding driver functions called for each\n  defined group. Notice that you\u0027re only allowed to map\n  multiple *groups* to the same\n  { device, pin controller, function } triplet, attempts\n  to map the same device to multiple pin controllers will\n  for example fail. This is hopefully the crucial feature\n  requested by Stephen Warren.\n- Add a pinmux hogging field to the pinmux mapping entries,\n  and enable the pinmux core to hog pinmux map entries.\n  This currently only works for pinmuxes without assigned\n  devices as it looks now, but with device trees we can\n  look up the corresponding struct device * entries when\n  we register the pinmux driver, and have it hog each\n  pinmux map in turn, for a simple approach to\n  non-dynamic pin muxing. This addresses an issue from\n  Grant Likely that the machine should take care of as\n  much of the pinmux setup as possible, not the devices.\n  By supplying a list of hogs, it can now instruct the\n  core to take care of any static mappings.\n- Switch pinmux group retrieveal function to grab an\n  array of strings representing the groups rather than an\n  array of unsigned and rewrite accordingly.\n- Alter debugfs to show the grouplist handled by each\n  pinmux. Also add a list of hogs.\n- Dynamically allocate a struct pinmux at pinmux_get() and\n  free it at pinmux_put(), then add these to the global\n  list of pinmuxes active as we go along.\n- Go over the list of pinmux maps at pinmux_get() time\n  and repeatedly apply matches.\n- Retrieve applicable groups per function from the driver\n  as a string array rather than a unsigned array, then\n  lookup the enumerators.\n- Make the device to pinmux map a singleton - only allow the\n  mapping table to be registered once and even tag the\n  registration function with __init so it surely won\u0027t be\n  abused.\n- Create a separate debugfs file to view the pinmux map at\n  runtime.\n- Introduce a spin lock to the pin descriptor struct, lock it\n  when modifying pin status entries. Reported by Stijn Devriendt.\n- Fix up the documentation after review from Stephen Warren.\n- Let the GPIO ranges give names as const char * instead of some\n  fixed-length string.\n- add a function to unregister GPIO ranges to mirror the\n  registration function.\n- Privatized the struct pinctrl_device and removed it from the\n  \u003clinux/pinctrl/pinctrl.h\u003e API, the drivers do not need to know\n  the members of this struct. It is now in the local header\n  \"core.h\".\n- Rename the concept of \"anonymous\" mux maps to \"system\" muxes\n  and add convenience macros and documentation.\n\nChangeLog v7-\u003ev8:\n\n- Delete the leftover pinmux_config() function from the\n \u003clinux/pinctrl/pinmux.h\u003e header.\n- Fix a race condition found by Stijn Devriendt in pin_request()\n\nChangeLog v8-\u003ev9:\n\n- Drop the bus_type and the sysfs attributes and all, we\u0027re not on\n  the clear about how this should be used for e.g. userspace\n  interfaces so let us save this for the future.\n- Use the right name in MAINTAINERS, PIN CONTROL rather than\n  PINMUX\n- Don\u0027t kfree() the device state holder, let the .remove() callback\n  handle this.\n- Fix up numerous kerneldoc headers to have one line for the function\n  description and more verbose documentation below the parameters\n\nChangeLog v9-\u003ev10:\n- pinctrl: EXPORT_SYMBOL needs export.h, folded in a patch\n  from Steven Rothwell\n- fix pinctrl_register error handling, folded in a patch from\n  Axel Lin\n- Various fixes to documentation text so that it\u0027s consistent.\n- Removed pointless comment from drivers/Kconfig\n- Removed dependency on SYSFS since we removed the bus in\n  v9.\n- Renamed hopelessly abbreviated pctldev_* functions to the\n  more verbose pinctrl_dev_*\n- Drop mutex properly when looking up GPIO ranges\n- Return NULL instead of ERR_PTR() errors on registration of\n  pin controllers, using cast pointers is fragile. We can\n  live without the detailed error codes for sure.\n\nCc: Stijn Devriendt \u003chighguy@gmail.com\u003e\nCc: Joe Perches \u003cjoe@perches.com\u003e\nCc: Russell King \u003clinux@arm.linux.org.uk\u003e\nAcked-by: Grant Likely \u003cgrant.likely@secretlab.ca\u003e\nAcked-by: Stephen Warren \u003cswarren@nvidia.com\u003e\nTested-by: Barry Song \u003c21cnbao@gmail.com\u003e\nSigned-off-by: Linus Walleij \u003clinus.walleij@linaro.org\u003e\n"
    }
  ]
}