)]}' { "log": [ { "commit": "c4b5be98fe78508e7199d6919eb712feba9a4f01", "tree": "9e688dd076cea9213f8bcbda3627aa7941a01879", "parents": [ "796a8e423ac8afe9e98ad96e668f50142bdd7825" ], "author": { "name": "Felipe Balbi", "email": "felipe.balbi@nokia.com", "time": "Wed May 26 14:42:23 2010 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu May 27 09:12:42 2010 -0700" }, "message": "gpiolib: introduce set_debounce method\n\nA few architectures, like OMAP, allow you to set a debouncing time for the\ngpio before generating the IRQ. Teach gpiolib about that.\n\nMark said:\n: This would be generally useful for embedded systems, especially where\n: the interrupt concerned is a wake source. It allows drivers to avoid\n: spurious interrupts from noisy sources so if the hardware supports it\n: the driver can avoid having to explicitly wait for the signal to become\n: stable and software has to cope with fewer events. We\u0027ve lived without\n: it for quite some time, though.\n\nDavid said:\n: I looked at adding debounce support to the generic GPIO calls (and thus\n: gpiolib) some time back, but decided against it. I forget why at this\n: time (check list archives) but it wasn\u0027t because of lack of utility in\n: certain contexts.\n:\n: One thing to watch out for is just how variable the hardware capabilities\n: are. Atmel GPIOs have something like a fixed number of 32K clock cycles\n: for debounce, twl4030 had something odd, OMAPs were more like the Atmel\n: chips but with a different clock. In some cases debouncing had to be\n: ganged, not per-GPIO. And so forth.\n\nSigned-off-by: Felipe Balbi \u003cfelipe.balbi@nokia.com\u003e\nCc: Tony Lindgren \u003ctony@atomide.com\u003e\nCc: David Brownell \u003cdavid-b@pacbell.net\u003e\nReviewed-by: Mark Brown \u003cbroonie@opensource.wolfsonmicro.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "0769746183caff9d4334be48c7b0e7d2ec8716c4", "tree": "e23768be82bd84cf8331709ecc1fd36c3d468f33", "parents": [ "35570ac6039ef490b9c5abde1fee4803a39bf4e1" ], "author": { "name": "Jani Nikula", "email": "ext-jani.1.nikula@nokia.com", "time": "Tue Dec 15 16:46:20 2009 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Wed Dec 16 07:20:01 2009 -0800" }, "message": "gpiolib: add support for changing value polarity in sysfs\n\nDrivers may use gpiolib sysfs as part of their public user space\ninterface. The GPIO number and polarity might change from board to\nboard. The gpio_export_link() call can be used to hide the GPIO number\nfrom user space. Add support for also hiding the GPIO line polarity\nchanges from user space.\n\nSigned-off-by: Jani Nikula \u003cext-jani.1.nikula@nokia.com\u003e\nCc: David Brownell \u003cdavid-b@pacbell.net\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "a4177ee7f1a83eecb1d75e85d32664b023ef65e9", "tree": "614b12b1f28a1a9090d96bea33639265e3e79839", "parents": [ "d8c1acb1664d17dd995e34507533321e986d9215" ], "author": { "name": "Jani Nikula", "email": "ext-jani.1.nikula@nokia.com", "time": "Tue Sep 22 16:46:33 2009 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Wed Sep 23 07:39:46 2009 -0700" }, "message": "gpiolib: allow exported GPIO nodes to be named using sysfs links\n\nCommit 926b663ce8215ba448960e1ff6e58b67a2c3b99b (gpiolib: allow GPIOs to\nbe named) already provides naming on the chip level. This patch provides\nmore flexibility by allowing multiple names where ever in sysfs on a per\nGPIO basis.\n\nAdapted from David Brownell\u0027s comments on a similar concept:\nhttp://lkml.org/lkml/2009/4/20/203.\n\n[randy.dunlap@oracle.com: fix build for CONFIG_GENERIC_GPIO\u003dn]\nSigned-off-by: Jani Nikula \u003cext-jani.1.nikula@nokia.com\u003e\nAcked-by: David Brownell \u003cdavid-b@pacbell.net\u003e\nCc: Daniel Silverstone \u003cdsilvers@simtec.co.uk\u003e\nSigned-off-by: Randy Dunlap \u003crandy.dunlap@oracle.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "3d599d1ca57f443e5c4ff5af1e69d90350082f77", "tree": "475b066c18f2b610d6a0ee0a6313237ce61afc4a", "parents": [ "c557fa3e4c156b8713c177d9dde08920130bf551" ], "author": { "name": "Uwe Kleine-König", "email": "ukleinek@informatik.uni-freiburg.de", "time": "Wed Oct 15 22:03:12 2008 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Oct 16 11:21:40 2008 -0700" }, "message": "gpio_free might sleep, generic part\n\nAccording to the documentation gpio_free should only be called from task\ncontext only. To make this more explicit add a might sleep to all\nimplementations.\n\nThis is the generic part which changes gpiolib and the fallback\nimplementation only.\n\nSigned-off-by: Uwe Kleine-König \u003cukleinek@informatik.uni-freiburg.de\u003e\nCc: David Brownell \u003cdavid-b@pacbell.net\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "d8f388d8dc8d4f36539dd37c1fff62cc404ea0fc", "tree": "df8603775c889f29f8a03c77b9f7913bfd90d296", "parents": [ "8b6dd986823a8d92ed9f54baa5cef8604d9d9d44" ], "author": { "name": "David Brownell", "email": "dbrownell@users.sourceforge.net", "time": "Fri Jul 25 01:46:07 2008 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Jul 25 10:53:30 2008 -0700" }, "message": "gpio: sysfs interface\n\nThis adds a simple sysfs interface for GPIOs.\n\n /sys/class/gpio\n \t/export ... asks the kernel to export a GPIO to userspace\n \t/unexport ... to return a GPIO to the kernel\n /gpioN ... for each exported GPIO #N\n\t /value ... always readable, writes fail for input GPIOs\n\t /direction ... r/w as: in, out (default low); write high, low\n\t/gpiochipN ... for each gpiochip; #N is its first GPIO\n\t /base ... (r/o) same as N\n\t /label ... (r/o) descriptive, not necessarily unique\n\t /ngpio ... (r/o) number of GPIOs; numbered N .. N+(ngpio - 1)\n\nGPIOs claimed by kernel code may be exported by its owner using a new\ngpio_export() call, which should be most useful for driver debugging.\nSuch exports may optionally be done without a \"direction\" attribute.\n\nUserspace may ask to take over a GPIO by writing to a sysfs control file,\nhelping to cope with incomplete board support or other \"one-off\"\nrequirements that don\u0027t merit full kernel support:\n\n echo 23 \u003e /sys/class/gpio/export\n\t... will gpio_request(23, \"sysfs\") and gpio_export(23);\n\tuse /sys/class/gpio/gpio-23/direction to (re)configure it,\n\twhen that GPIO can be used as both input and output.\n echo 23 \u003e /sys/class/gpio/unexport\n\t... will gpio_free(23), when it was exported as above\n\nThe extra D-space footprint is a few hundred bytes, except for the sysfs\nresources associated with each exported GPIO. The additional I-space\nfootprint is about two thirds of the current size of gpiolib (!). Since\nno /dev node creation is involved, no \"udev\" support is needed.\n\nRelated changes:\n\n * This adds a device pointer to \"struct gpio_chip\". When GPIO\n providers initialize that, sysfs gpio class devices become children of\n that device instead of being \"virtual\" devices.\n\n * The (few) gpio_chip providers which have such a device node have\n been updated.\n\n * Some gpio_chip drivers also needed to update their module \"owner\"\n field ... for which missing kerneldoc was added.\n\n * Some gpio_chips don\u0027t support input GPIOs. Those GPIOs are now\n flagged appropriately when the chip is registered.\n\nBased on previous patches, and discussion both on and off LKML.\n\nA Documentation/ABI/testing/sysfs-gpio update is ready to submit once this\nmerges to mainline.\n\n[akpm@linux-foundation.org: a few maintenance build fixes]\nSigned-off-by: David Brownell \u003cdbrownell@users.sourceforge.net\u003e\nCc: Guennadi Liakhovetski \u003cg.liakhovetski@pengutronix.de\u003e\nCc: Greg KH \u003cgreg@kroah.com\u003e\nCc: Kay Sievers \u003ckay.sievers@vrfy.org\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "6ea0205b56546cef782b74d9f4664ec00290a6ae", "tree": "6d95b52af65d6de540e606d95159e539d5cc2852", "parents": [ "ee29420aca6ca6fbb3e72ee8a980b2600911b864" ], "author": { "name": "David Brownell", "email": "david-b@pacbell.net", "time": "Fri May 23 13:04:58 2008 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat May 24 09:56:13 2008 -0700" }, "message": "gpio: build fixes\n\nThis fixes various gpio-related build errors (mostly potential)\nreported in part by Russell King and Uwe Kleine-König.\n\nSigned-off-by: David Brownell \u003cdbrownell@users.sourceforge.net\u003e\nCc: Uwe Kleine-König \u003cUwe.Kleine-Koenig@digi.com\u003e\nCc: Russell King \u003crmk@arm.linux.org.uk\u003e\nCc: Arnaud Patard \u003carnaud.patard@rtp-net.org\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "7560fa60fcdcdb0da662f6a9fad9064b554ef46c", "tree": "2089d826b0b9230752f318b20884dca20b3847d5", "parents": [ "83c7c693ed3e61535ad6a097ad991a88aafc54b8" ], "author": { "name": "David Brownell", "email": "david-b@pacbell.net", "time": "Tue Mar 04 14:28:27 2008 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Tue Mar 04 16:35:10 2008 -0800" }, "message": "gpio: \u003clinux/gpio.h\u003e and \"no GPIO support here\" stubs\n\nAdd a \u003clinux/gpio.h\u003e defining fail/warn stubs for GPIO calls on platforms that\ndon\u0027t support the GPIO programming interface. That includes the arch-specific\nimplementation glue otherwise.\n\nThis facilitates a new model for GPIO usage: drivers that can use GPIOs if\nthey\u0027re available, but don\u0027t require them. One example of such a driver is\nNAND driver for various FreeScale chips. On platforms update with GPIO\nsupport, they can be used instead of a worst-case delay to verify that the\nBUSY signal is off.\n\n(Also includes a couple minor unrelated doc updates.)\n\nSigned-off-by: David Brownell \u003cdbrownell@users.sourceforge.net\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" } ] }