)]}'
{
  "commit": "513c4eb162aecea92e0b05a7c5e206474526eda2",
  "tree": "731dc0326955d5d568a13416799c7ff92d08b2fc",
  "parents": [
    "b5e074a6ff4cfa090f7aa8a87f5079d19206d91c"
  ],
  "author": {
    "name": "Paul Fertser",
    "email": "fercerpav@gmail.com",
    "time": "Mon Oct 10 11:19:23 2011 +0400"
  },
  "committer": {
    "name": "Greg Kroah-Hartman",
    "email": "gregkh@suse.de",
    "time": "Fri Nov 11 09:36:16 2011 -0800"
  },
  "message": "plat-mxc: iomux-v3.h: implicitly enable pull-up/down when that\u0027s desired\n\ncommit 6571534b600b8ca1936ff5630b9e0947f21faf16 upstream.\n\nTo configure pads during the initialisation a set of special constants\nis used, e.g.\n#define MX25_PAD_FEC_MDIO__FEC_MDIO IOMUX_PAD(0x3c4, 0x1cc, 0x10, 0, 0, PAD_CTL_HYS | PAD_CTL_PUS_22K_UP)\n\nThe problem is that no pull-up/down is getting activated unless both\nPAD_CTL_PUE (pull-up enable) and PAD_CTL_PKE (pull/keeper module\nenable) set. This is clearly stated in the i.MX25 datasheet and is\nconfirmed by the measurements on hardware. This leads to some rather\nhard to understand bugs such as misdetecting an absent ethernet PHY (a\nreal bug i had), unstable data transfer etc. This might affect mx25,\nmx35, mx50, mx51 and mx53 SoCs.\n\nIt\u0027s reasonable to expect that if the pullup value is specified, the\nintention was to have it actually active, so we implicitly add the\nneeded bits.\n\nSigned-off-by: Paul Fertser \u003cfercerpav@gmail.com\u003e\nSigned-off-by: Sascha Hauer \u003cs.hauer@pengutronix.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ebbce33097a76f81cae8696758ac713091279f88",
      "old_mode": 33188,
      "old_path": "arch/arm/plat-mxc/include/mach/iomux-v3.h",
      "new_id": "45099566fecc64e68588126b0c794e3346f15193",
      "new_mode": 33188,
      "new_path": "arch/arm/plat-mxc/include/mach/iomux-v3.h"
    }
  ]
}