)]}'
{
  "log": [
    {
      "commit": "e833acaf2b5cfac0fb53692652a8c39667f1e559",
      "tree": "f530c2ea75a3d7e52045e1f543ced58757895b9d",
      "parents": [
        "7dfc4b284ca395a035e7da058f86dfb4275dd509"
      ],
      "author": {
        "name": "Duy Truong",
        "email": "dtruong@codeaurora.org",
        "time": "Tue Feb 12 13:35:08 2013 -0800"
      },
      "committer": {
        "name": "Duy Truong",
        "email": "dtruong@codeaurora.org",
        "time": "Tue Feb 12 13:35:08 2013 -0800"
      },
      "message": "Update copyright to The Linux Foundation\n\nChange-Id: Ibead64ce2e901dede2ddd1b86088b88f2350ce92\nSigned-off-by: Duy Truong \u003cdtruong@codeaurora.org\u003e\n"
    },
    {
      "commit": "978d335cee5541033ce66d6ec63a70535b523600",
      "tree": "c80940f3ce34edba5e00de19c0ea47e439fd9542",
      "parents": [
        "a05f455aee64cc006c5c26c210c3620ed7f2d660"
      ],
      "author": {
        "name": "Michael Bohan",
        "email": "mbohan@codeaurora.org",
        "time": "Fri May 25 15:02:38 2012 -0700"
      },
      "committer": {
        "name": "Michael Bohan",
        "email": "mbohan@codeaurora.org",
        "time": "Tue Jun 26 10:35:18 2012 -0700"
      },
      "message": "spmi: Add spmi_resource for non spmi-dev-container cases\n\nThe devnode array is currently being used for non\nspmi-dev-container devices as a special case where the number of\ndevnodes is 1. This obfuscates the code and also removes the\nability to store the dev-container\u0027s device resource information,\nsince in that special case the devnode array is dedicated for the\nchild devices.\n\nAdd a new spmi_resource entry used for typical spmi_devices, and\ntreat the devnode array as the special case for\nspmi-dev-container.\n\nAlso add a new API spmi_get_primary_dev_name() to return the name\nof the device assigned with the \u0027label\u0027 binding if it exists.\n\nChange-Id: Ibe7b12285e37bb0529024558550a96d71393bc10\nSigned-off-by: Michael Bohan \u003cmbohan@codeaurora.org\u003e\n"
    },
    {
      "commit": "8d6aae33e4f6ebe7627acb7f589f56e02dc775bc",
      "tree": "b5af90e4a7c571f52a16ed2894112c807786b3be",
      "parents": [
        "a6a354dd3d5bfbbefb9fc09295be5e31bc67b48b"
      ],
      "author": {
        "name": "Michael Bohan",
        "email": "mbohan@codeaurora.org",
        "time": "Tue May 22 15:41:06 2012 -0700"
      },
      "committer": {
        "name": "Michael Bohan",
        "email": "mbohan@codeaurora.org",
        "time": "Tue Jun 26 10:35:17 2012 -0700"
      },
      "message": "of: spmi: Add support for device naming and lookups\n\nSince we support multiple device_nodes per spmi_device when used\nwith the spmi-dev-container flag, it\u0027s often unclear how a driver\nshould make reference to a particular device. Therefore,\nintroduce the spmi specific binding spmi-dev-name that specifies\nthe device name for the device_node.\n\nAlso introduce an API that can be used from\nthe driver to lookup the specific device node associated with a\nparticular device name.\n\nNote that it may seem at first glance that the binding \u0027label\u0027 is\nredundant with device_node-\u003ename. However, per the ePAPR,\ndevice_node-\u003ename is intended to be as generic as possible,\nrepresenting the function of the device and not the precise\nprogramming model. \u0027label\u0027 is used to give a platform\nspecific name that can be queried from device drivers.\n\nChange-Id: I28eca35d0b625372c26a6d8ad81e7679f200d14b\nSigned-off-by: Michael Bohan \u003cmbohan@codeaurora.org\u003e\n"
    },
    {
      "commit": "a6a354dd3d5bfbbefb9fc09295be5e31bc67b48b",
      "tree": "399509d12fe0c6bc2c4574fcc8c354b0b99f9271",
      "parents": [
        "0e5534d92f03c76de4c15736729101520c4f0c3a"
      ],
      "author": {
        "name": "Michael Bohan",
        "email": "mbohan@codeaurora.org",
        "time": "Mon May 21 17:47:11 2012 -0700"
      },
      "committer": {
        "name": "Michael Bohan",
        "email": "mbohan@codeaurora.org",
        "time": "Tue Jun 26 10:35:16 2012 -0700"
      },
      "message": "of: spmi: Support resource naming\n\nreg-names and interrupt-names are standard bindings to map device\ntree reg and interrupt indices to particular names. This way the\ndriver does not need to be concerned with hard coded assignments.\nTherefore, add spmi support for these bindings.\n\nExplicit support for reg-names is required since the\nimplementation does not make use of of_address_to_resource(),\nwhich happens to already support this.\nThis is because of_address_to_resource() mandates address\ntranslation, which is not relevant to spmi.\n\ninterrupt-names is already implicitly handled by\nof_irq_to_resource(), which is used in the spmi implementation.\nAdd additional documentation to state clearly that this binding\nis also supported.\n\nAlso add supporting routines to easily lookup a resource by name\nfor both registers and interrupts.\n\nChange-Id: I94faf950da5106ecd4ff36f47e5b46102d9bd426\nSigned-off-by: Michael Bohan \u003cmbohan@codeaurora.org\u003e\n"
    },
    {
      "commit": "0e5534d92f03c76de4c15736729101520c4f0c3a",
      "tree": "bc74e13f707040750e6dd8d77b365e9e1c394442",
      "parents": [
        "08e1e909c7822559e2ca78b3953eb43d0b0c5dcb"
      ],
      "author": {
        "name": "Michael Bohan",
        "email": "mbohan@codeaurora.org",
        "time": "Tue May 22 17:33:45 2012 -0700"
      },
      "committer": {
        "name": "Michael Bohan",
        "email": "mbohan@codeaurora.org",
        "time": "Tue Jun 26 10:35:16 2012 -0700"
      },
      "message": "spmi: qpnp: Change APIs to take a spmi_resource pointer instead of index\n\nPointers are more flexible than index numbers, since index\nnumbers depend upon an additional reference to the array in\nquestion. In particular, we\u0027d like to add a new API to lookup a\ndevnode based on a predefined name in the Device Tree. This API\nwill return a spmi_resource, and so it\u0027s natural to want to use\nthis pointer directly with the other existing APIs.\n\nAlso introduce a new API spmi_for_each_devnode that can be used\nto iterate each spmi_resource in the dev_node array. This\nabstracts the traversal of the array, which was previously done\nwithin the existing APIs.\n\nChange-Id: I18f9397e5d78770e840a9f95dd8061201931df6e\nSigned-off-by: Michael Bohan \u003cmbohan@codeaurora.org\u003e\n"
    },
    {
      "commit": "08e1e909c7822559e2ca78b3953eb43d0b0c5dcb",
      "tree": "9eb7d3bb8a7badd403199c27145d243f78396d4b",
      "parents": [
        "7c06410945495fc13caf69d9ad83da0195a7166e"
      ],
      "author": {
        "name": "Michael Bohan",
        "email": "mbohan@codeaurora.org",
        "time": "Wed May 23 10:55:22 2012 -0700"
      },
      "committer": {
        "name": "Michael Bohan",
        "email": "mbohan@codeaurora.org",
        "time": "Tue Jun 26 10:35:15 2012 -0700"
      },
      "message": "spmi: Rename qpnp library to be part of the spmi framework\n\nIt turns out that the only use cases for the qpnp library use\nthe existing spmi data structures. As such, there\u0027s really\nno justification for having the library not be called \u0027spmi\u0027.\nThere is nothing Qualcomm specific about this code.\n\nAlso cleanup some inconsistencies in the Kernel Doc comments\nwhile we\u0027re here.\n\nChange-Id: I1c73c88be740b6f5d38ba2de62de1737981b30fa\nSigned-off-by: Michael Bohan \u003cmbohan@codeaurora.org\u003e\n"
    },
    {
      "commit": "86622b3ef7ed42713f82dcfc7338b15202097024",
      "tree": "dd1390959ade69ff143d25260adb40147cd02072",
      "parents": [
        "5fafd3ce289590ca749004cc061975782b684902"
      ],
      "author": {
        "name": "Michael Bohan",
        "email": "mbohan@codeaurora.org",
        "time": "Wed Feb 08 16:59:00 2012 -0800"
      },
      "committer": {
        "name": "Michael Bohan",
        "email": "mbohan@codeaurora.org",
        "time": "Wed Mar 14 14:05:41 2012 -0700"
      },
      "message": "of: of_spmi: Add support for spmi-dev-container binding\n\nThe spmi-dev-container binding is intended for SPMI\nconfigurations that have multiple device nodes associated with\nonly one spmi_device. By default, if this flag is not specified,\neach device node will create a new spmi_device.\n\nSometimes having multiple spmi_devices for SPMI device nodes is\nsuperfluous. One example of this is gpios. In some architectures,\na single gpio is treated as a unique device. But from a gpio_chip\nperspective, the chip is comprised of many gpios. Beyond wasting\nmemory allocating a unique spmi_device per gpio, the implication\nof not coalescing spmi_devices is that the clients probe() routine\nwould be called N number of times. But this sort of behavior makes\nit difficult to realize when a gpio_chip starts and stops. If we\nassume that one gpio_chip represents one call to probe(), then\nthis problem is solved, since all gpios in that chip will be\npassed as resources.\n\nIn order to support multiple device nodes per spmi_device, we\nalso need to extend the data structures for spmi_resources.\n\nThis change also makes an effort to cleanup some of the error\nhandling for illegal combinations of device bindings, as well as\nadding some additional documentation.\n\nChange-Id: If3ce2aaaa07bdf79e0d9fdedf16419e74a00fbec\nSigned-off-by: Michael Bohan \u003cmbohan@codeaurora.org\u003e\n"
    },
    {
      "commit": "ee44ade0261441a62d4472ec02a302731d4b5b82",
      "tree": "ada2335547f5b65e2d029485fe6b1aca65553321",
      "parents": [
        "1268d1e0a2109f40f67830dd92e6a1200eb94ee2"
      ],
      "author": {
        "name": "Kenneth Heitke",
        "email": "kheitke@codeaurora.org",
        "time": "Wed Feb 08 13:45:33 2012 -0700"
      },
      "committer": {
        "name": "Kenneth Heitke",
        "email": "kheitke@codeaurora.org",
        "time": "Tue Feb 14 14:50:38 2012 -0700"
      },
      "message": "spmi: Linux driver framework for SPMI\n\nSPMI (System Power Management Interface) is a specification\ndeveloped by the MIPI (Mobile Industry Process Interface) Alliance\noptimized for the real time control of Power Management ICs (PMIC).\n\nSPMI is a two-wire serial interface that supports up to 4 master\ndevices and up to 16 logical slaves.  A physical PMIC device may\nconsist of multiple logical slave interfaces.\n\nThe framework supports message APIs, multiple busses (1 controller\nper bus) and multiple clients/slave devices per controller.\n\nChange-Id: Ib6319047b4ab9cea6dfb0879312c4c1f63462439\nSigned-off-by: Kenneth Heitke \u003ckheitke@codeaurora.org\u003e\n"
    }
  ]
}
