1. 17 1月, 2014 2 次提交
    • G
      dt/bindings: remove users of device_type "mdio" · dae95c1f
      Grant Likely 提交于
      device_type is a deprecated property, but some MDIO bus nodes still have
      it. Except for a couple of old binding (compatible="gianfar" and
      compatible="ucc_geth_phy") the kernel doesn't look for
      device_type="mdio" at all.
      
      This patch removes all instances of device_type="mdio" from the binding
      documentation and the .dts files.
      Signed-off-by: NGrant Likely <grant.likely@linaro.org>
      Cc: Rob Herring <rob.herring@calxeda.com>
      Cc: Pawel Moll <pawel.moll@arm.com>
      Cc: Mark Rutland <mark.rutland@arm.com>
      Cc: Ian Campbell <ijc+devicetree@hellion.org.uk>
      Cc: Kumar Gala <galak@codeaurora.org>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      dae95c1f
    • G
      dt/bindings: Remove references to linux,phandle properties · aadfb32b
      Grant Likely 提交于
      The linux,phandle property is essentially an internal structural element
      of the DT data structure. The dtc toolchain takes care of maintaining it
      at compile time. It does not need to appear as part of the binding
      documentation. This patch removes it so that users don't think they need
      to add a phandle property manually.
      Signed-off-by: NGrant Likely <grant.likely@linaro.org>
      Cc: Rob Herring <rob.herring@calxeda.com>
      Cc: Pawel Moll <pawel.moll@arm.com>
      Cc: Mark Rutland <mark.rutland@arm.com>
      Cc: Ian Campbell <ijc+devicetree@hellion.org.uk>
      Cc: Kumar Gala <galak@codeaurora.org>
      aadfb32b
  2. 16 1月, 2014 1 次提交
    • G
      dt/bindings: Remove all references to device_type "ethernet-phy" · 40aad3c1
      Grant Likely 提交于
      The device_type property is deprecated for the flattened device tree and
      the value "ethernet-phy" has never been defined as having a useful
      meaning. Neither the kernel nor u-boot depend on it. It should never
      have appeared in PHY bindings. This patch removes all references to
      "ethernet-phy" as a device_type value from the documentation and the
      .dts files.
      
      This patch was generated mechanically with the following command and
      then verified by looking at the diff.
      
      sed -i '/"ethernet-phy"/d' `git grep -l '"ethernet-phy"'`
      Signed-off-by: NGrant Likely <grant.likely@linaro.org>
      Acked-by: NSrinivas Kandagatla <srinivas.kandagatla@st.com>
      Cc: Rob Herring <rob.herring@calxeda.com>
      Cc: Pawel Moll <pawel.moll@arm.com>
      Cc: Mark Rutland <mark.rutland@arm.com>
      Cc: Ian Campbell <ijc+devicetree@hellion.org.uk>
      Cc: Kumar Gala <galak@codeaurora.org>
      Cc: Florian Fainelli <f.fainelli@gmail.com>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      40aad3c1
  3. 22 12月, 2013 2 次提交
  4. 19 12月, 2013 1 次提交
  5. 18 12月, 2013 1 次提交
  6. 17 12月, 2013 1 次提交
  7. 13 12月, 2013 1 次提交
  8. 12 12月, 2013 1 次提交
  9. 11 12月, 2013 1 次提交
  10. 10 12月, 2013 2 次提交
  11. 06 12月, 2013 1 次提交
    • T
      net: davinci_emac: Fix platform data handling and make usable for am3517 · dd0df47d
      Tony Lindgren 提交于
      When booted with device tree, we may still have platform data passed
      as auxdata. For am3517 this is needed for passing the interrupt_enable
      and interrupt_disable callbacks that access the omap system control module
      registers. These callback functions will eventually go away when we have
      a separate system control module driver.
      
      Some of the things that are currently passed as platform data we don't need
      to set up as device tree properties as they are always the same on am3517.
      So let's use a new compatible flag for those so we can get those from
      the device tree match data.
      
      Also note that we need to fix setting of phy_dev to NULL instead of an empty
      string as the code later on uses that to find the first phy on the mdio bus.
      This seems to have been caused by 5d69e007 (net: davinci_emac: switch to
      new mdio).
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      dd0df47d
  12. 03 12月, 2013 10 次提交
  13. 02 12月, 2013 1 次提交
    • D
      KEYS: Fix multiple key add into associative array · 23fd78d7
      David Howells 提交于
      If sufficient keys (or keyrings) are added into a keyring such that a node in
      the associative array's tree overflows (each node has a capacity N, currently
      16) and such that all N+1 keys have the same index key segment for that level
      of the tree (the level'th nibble of the index key), then assoc_array_insert()
      calls ops->diff_objects() to indicate at which bit position the two index keys
      vary.
      
      However, __key_link_begin() passes a NULL object to assoc_array_insert() with
      the intention of supplying the correct pointer later before we commit the
      change.  This means that keyring_diff_objects() is given a NULL pointer as one
      of its arguments which it does not expect.  This results in an oops like the
      attached.
      
      With the previous patch to fix the keyring hash function, this can be forced
      much more easily by creating a keyring and only adding keyrings to it.  Add any
      other sort of key and a different insertion path is taken - all 16+1 objects
      must want to cluster in the same node slot.
      
      This can be tested by:
      
      	r=`keyctl newring sandbox @s`
      	for ((i=0; i<=16; i++)); do keyctl newring ring$i $r; done
      
      This should work fine, but oopses when the 17th keyring is added.
      
      Since ops->diff_objects() is always called with the first pointer pointing to
      the object to be inserted (ie. the NULL pointer), we can fix the problem by
      changing the to-be-inserted object pointer to point to the index key passed
      into assoc_array_insert() instead.
      
      Whilst we're at it, we also switch the arguments so that they are the same as
      for ->compare_object().
      
      BUG: unable to handle kernel NULL pointer dereference at 0000000000000088
      IP: [<ffffffff81191ee4>] hash_key_type_and_desc+0x18/0xb0
      ...
      RIP: 0010:[<ffffffff81191ee4>] hash_key_type_and_desc+0x18/0xb0
      ...
      Call Trace:
       [<ffffffff81191f9d>] keyring_diff_objects+0x21/0xd2
       [<ffffffff811f09ef>] assoc_array_insert+0x3b6/0x908
       [<ffffffff811929a7>] __key_link_begin+0x78/0xe5
       [<ffffffff81191a2e>] key_create_or_update+0x17d/0x36a
       [<ffffffff81192e0a>] SyS_add_key+0x123/0x183
       [<ffffffff81400ddb>] tracesys+0xdd/0xe2
      Signed-off-by: NDavid Howells <dhowells@redhat.com>
      Tested-by: NStephen Gallagher <sgallagh@redhat.com>
      23fd78d7
  14. 28 11月, 2013 5 次提交
  15. 27 11月, 2013 2 次提交
  16. 25 11月, 2013 1 次提交
    • A
      Documentation: gpiolib: document new interface · fd8e198c
      Alexandre Courbot 提交于
      gpiolib now exports a new descriptor-based interface which deprecates
      the older integer-based one. This patch documents this new interface and
      also takes the opportunity to brush-up the GPIO documentation a little
      bit.
      
      The new descriptor-based interface follows the same consumer/driver
      model as many other kernel subsystems (e.g. clock, regulator), so its
      documentation has similarly been splitted into different files.
      
      The content of the former documentation has been reused whenever it
      made sense; however, some of its content did not apply to the new
      interface anymore and have this been removed. Likewise, new sections
      like the mapping of GPIOs to devices have been written from scratch.
      
      The deprecated legacy-based documentation is still available, untouched,
      under Documentation/gpio/gpio-legacy.txt.
      Signed-off-by: NAlexandre Courbot <acourbot@nvidia.com>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      fd8e198c
  17. 22 11月, 2013 3 次提交
  18. 19 11月, 2013 1 次提交
  19. 18 11月, 2013 3 次提交