{"push_id":1046211204,"size":4,"distinct_size":4,"ref":"refs/heads/master","head":"59c03bc4c644b0f0bbf3c6807a97755b7509b319","before":"7aa42e2ba9a33530dd97bc5e814cd1b73d2cbb25","commits":[{"sha":"55bd1930f1822d3f7947721e47004800a65b8095","author":{"email":"5259333ce42e3ace6a73988cec7115ed9d3a661a@chromium.org","name":"Shawn Nematbakhsh"},"message":"charger: bd99955: Add support for extended features\n\nAdd support for charge port switching and extpower detection, which are\nnot part of the standard charger API.\n\nIn addition, add a console command for dumping all regs, which is\nhelpful for debug.\n\nBUG=chrome-os-partner:51722\nTEST=Manual with subsequent commit. Verify kevin charges at 3A input current\nwhen zinger is inserted, and verify battery actually charges.\nBRANCH=None\n\nChange-Id: I98a0c0142d26facc0e0b9ef7f1dcd003ebffd9c1\nSigned-off-by: Shawn Nematbakhsh <shawnn@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/335537\nCommit-Ready: Shawn N <shawnn@chromium.org>\nTested-by: Shawn N <shawnn@chromium.org>\nReviewed-by: Vijay P Hiremath <vijay.p.hiremath@intel.com>\nReviewed-by: Kevin K Wong <kevin.k.wong@intel.com>\nReviewed-by: Mary Ruthven <mruthven@chromium.org>","distinct":true,"url":"https://api.github.com/repos/coreboot/chrome-ec/commits/55bd1930f1822d3f7947721e47004800a65b8095"},{"sha":"e2deea36495ae4c6541db0ff0899c700b731ced7","author":{"email":"5259333ce42e3ace6a73988cec7115ed9d3a661a@chromium.org","name":"Shawn Nematbakhsh"},"message":"kevin: Add battery and charger support\n\nAdd support for bd99955 charger and battery.\n\nBUG=chrome-os-partner:51722\nTEST=Verify kevin charges at 3A input current when zinger is inserted,\nand verify battery actually charges.\nBRANCH=None\n\nSigned-off-by: Shawn Nematbakhsh <shawnn@chromium.org>\nChange-Id: Iccd8185585fe39440681f5830cf58acafe6291b8\nReviewed-on: https://chromium-review.googlesource.com/335538\nCommit-Ready: Shawn N <shawnn@chromium.org>\nTested-by: Shawn N <shawnn@chromium.org>\nReviewed-by: Mary Ruthven <mruthven@chromium.org>","distinct":true,"url":"https://api.github.com/repos/coreboot/chrome-ec/commits/e2deea36495ae4c6541db0ff0899c700b731ced7"},{"sha":"9e0c450f726d3d6dfd3486d7b816fd90621a6321","author":{"email":"129945214b1d548d8e49b6c29c43094f8c78057f@chromium.org","name":"Bill Richardson"},"message":"Cr50: First attempt at USB suspend with deep sleep\n\nThis is still in testing mode, so you have to take special steps\nto enable it (keep reading). But if you do the right dance, it\ndoes go into deep sleep for USB suspend, and resumes correctly.\n\nHowever, it doesn't yet wake for any other reason. That's coming next.\n\nNormal sleep is not yet supported, either.\n\nBUG=chrome-os-partner:49955, chrome-os-partner:50721\nBRANCH=none\nTEST=make buildall; extensive tests on Cr50\n\nTesting is a pain.\n\nFirst, you can't print anything in the idle task, because that\njust makes it stop being idle, so the only way to detect when\nit's triggered is by wiring up a GPIO and instrumenting things.\n\nSecond, you have to manually reenable USB suspend on the host\nevery time the Cr50 boots with\n\n  echo auto > /sys/bus/usb/devices/<BLEH>/power/control\n\nwhere <BLEH> is the correct device.\n\nThird, for reasons probably related to the mysteries of HID\ndevices combined with crbug.com/431886, you have to build the\nfirmware without CONFIG_USB_HID (and the related items in\nboard.h)\n\nFinally, because it's still a work in progress, you have to type\n\n  idle d\n\nat the serial console after every boot (or resume) to reenable\ndeep sleep in the idle task.\n\nIf you do all that, then you'll see that it does go into deep\nsleep. Ping it again with \"lsusb -v -d 18d1:5014\" or\n./test/usb_test/device_configuration, and it wakes up and\nresponds!\n\nIf you disconnect the USB while it's in deep sleep, it stays\nasleep. When you plug it in again, it wakes up, but it correctly\nrecognizes that it shouldn't resume and does a normal reset\ninstead.\n\nChange-Id: I3cc66e48ce671142a4d12edbe0eb9fdacecea0d9\nSigned-off-by: Bill Richardson <wfrichar@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/336279\nReviewed-by: Dominic Rizzo <domrizzo@google.com>","distinct":true,"url":"https://api.github.com/repos/coreboot/chrome-ec/commits/9e0c450f726d3d6dfd3486d7b816fd90621a6321"},{"sha":"59c03bc4c644b0f0bbf3c6807a97755b7509b319","author":{"email":"81380f3403fed74252e92df3ed012a1819ec6296@chromium.org","name":"Mary Ruthven"},"message":"cr50: enable use of multiple UARTs\n\ncr50 has three UARTs that it will be using. This change modifies the\nuart api to specify which uart to use.\n\nBUG=chrome-os-partner:50702\nBRANCH=none\nTEST=change the interrupts and CONFIG_UART_CONSOLE to see that the\ndifferent UARTs can be used.\n\nChange-Id: I754a69159103b48bc3f2f8ab1b9c8b86cea6bea5\nSigned-off-by: Mary Ruthven <mruthven@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/333402\nTested-by: Bill Richardson <wfrichar@chromium.org>\nReviewed-by: Bill Richardson <wfrichar@chromium.org>","distinct":true,"url":"https://api.github.com/repos/coreboot/chrome-ec/commits/59c03bc4c644b0f0bbf3c6807a97755b7509b319"}]}