)]}'
{
  "log": [
    {
      "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"
    }
  ]
}