)]}' { "log": [ { "commit": "b1bf7d4d1b3911352cf1ec63c1de06214288ccd0", "tree": "0fd27c638977cb5c7e6e3f95085ce842b57a4ae3", "parents": [ "0708500d49e8439d9fe5529795bdc1485f0f46c3", "3e11f7b840b4671213c66817294ad7dd0b572756" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu May 24 14:01:46 2012 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu May 24 14:01:46 2012 -0700" }, "message": "Merge tag \u0027gpio-for-linus\u0027 of git://git.secretlab.ca/git/linux-2.6\n\nPull GPIO driver changes from Grant Likely:\n \"Lots of gpio changes, both to core code and drivers.\n\n Changes do touch architecture code to remove the need for separate\n arm/gpio.h includes in most architectures.\n\n Some new drivers are added, and a number of gpio drivers are converted\n to use irq_domains for gpio inputs used as interrupts. Device tree\n support has been amended to allow multiple gpio_chips to use the same\n device tree node.\n\n Remaining changes are primarily bug fixes.\"\n\n* tag \u0027gpio-for-linus\u0027 of git://git.secretlab.ca/git/linux-2.6: (33 commits)\n gpio/generic: initialize basic_mmio_gpio shadow variables properly\n gpiolib: Remove \u0027const\u0027 from data argument of gpiochip_find()\n gpio/rc5t583: add gpio driver for RICOH PMIC RC5T583\n gpiolib: quiet gpiochip_add boot message noise\n gpio: mpc8xxx: Prevent NULL pointer deref in demux handler\n gpio/lpc32xx: Add device tree support\n gpio: Adjust of_xlate API to support multiple GPIO chips\n gpiolib: Implement devm_gpio_request_one()\n gpio-mcp23s08: dbg_show: fix pullup configuration display\n Add support for TCA6424A\n gpio/omap: (re)fix wakeups on level-triggered GPIOs\n gpio/omap: fix broken context restore for non-OFF mode transitions\n gpio/omap: fix missing check in *_runtime_suspend()\n gpio/omap: remove cpu_is_omapxxxx() checks from *_runtime_resume()\n gpio/omap: remove suspend/resume callbacks\n gpio/omap: remove retrigger variable in gpio_irq_handler\n gpio/omap: remove saved_wakeup field from struct gpio_bank\n gpio/omap: remove suspend_wakeup field from struct gpio_bank\n gpio/omap: remove saved_fallingdetect, saved_risingdetect\n gpio/omap: remove virtual_irq_start variable\n ...\n\nConflicts:\n\tdrivers/gpio/gpio-samsung.c\n" }, { "commit": "7563bbf89d065a2c3f05059ecbcc805645edcc62", "tree": "2b8231e8145a73cce0da67ce38e0360fcd0a802e", "parents": [ "25cf25073a4e1e0563c288908481f10f98acb19a" ], "author": { "name": "Mark Brown", "email": "broonie@opensource.wolfsonmicro.com", "time": "Sun Apr 15 10:52:54 2012 +0100" }, "committer": { "name": "Grant Likely", "email": "grant.likely@secretlab.ca", "time": "Fri May 11 18:00:14 2012 -0600" }, "message": "gpiolib/arches: Centralise bolierplate asm/gpio.h\n\nRather than requiring architectures that use gpiolib but don\u0027t have any\nneed to define anything custom to copy an asm/gpio.h provide a Kconfig\nsymbol which architectures must select in order to include gpio.h and\nfor other architectures just provide the trivial implementation directly.\n\nThis makes it much easier to do gpiolib updates and is also a step towards\nmaking gpiolib APIs available on every architecture.\n\nFor architectures with existing boilerplate code leave a stub header in\nplace which warns on direct inclusion of asm/gpio.h and includes\nlinux/gpio.h to catch code that\u0027s doing this. Direct inclusion of\nasm/gpio.h has long been deprecated.\n\nSigned-off-by: Mark Brown \u003cbroonie@opensource.wolfsonmicro.com\u003e\nAcked-by: Jonas Bonn \u003cjonas@southpole.se\u003e\nAcked-by: Tony Luck \u003ctony.luck@intel.com\u003e\nAcked-by: Linus Walleij \u003clinus.walleij@linaro.org\u003e\nSigned-off-by: Grant Likely \u003cgrant.likely@secretlab.ca\u003e\n" }, { "commit": "6b2aac42b20f495d9ea220036f57596d525d4233", "tree": "838c0537310ebd6198eeef7f5826edf141f467d7", "parents": [ "b40b26ccfc31465363dbd3ff849bd84ec87fe9b7" ], "author": { "name": "Masanari Iida", "email": "standby24x7@gmail.com", "time": "Sat Apr 14 00:14:11 2012 +0900" }, "committer": { "name": "Jiri Kosina", "email": "jkosina@suse.cz", "time": "Mon Apr 16 14:40:08 2012 +0200" }, "message": "Fix typo in various Kconfig file\n\nCorrect spelling typo in various Kconfig file.\n\nSigned-off-by: Masanari Iida \u003cstandby24x7@gmail.com\u003e\nSigned-off-by: Jiri Kosina \u003cjkosina@suse.cz\u003e\n" }, { "commit": "1f7034b9616e6f14dc7b6aa280210421428f31af", "tree": "52a950a4f58d00b3e28440bf5c4da2496453d982", "parents": [ "ad8f955daf77d303f0ee08d2acab30d3886cbd2b" ], "author": { "name": "Greg Ungerer", "email": "gerg@uclinux.org", "time": "Wed Oct 19 14:13:18 2011 +1000" }, "committer": { "name": "Greg Ungerer", "email": "gerg@uclinux.org", "time": "Fri Dec 30 10:20:50 2011 +1000" }, "message": "m68k: allow ColdFire 547x and 548x CPUs to be built with MMU enabled\n\nThe ColdFire 547x and 548x CPUs have internal MMU hardware. All code\nto support this is now in, so we can build kernels with it enabled.\n\nSigned-off-by: Greg Ungerer \u003cgerg@uclinux.org\u003e\nAcked-by: Geert Uytterhoeven \u003cgeert@linux-m68k.org\u003e\nAcked-by: Matt Waddel \u003cmwaddel@yahoo.com\u003e\nAcked-by: Kurt Mahan \u003ckmahan@xmission.com\u003e\n" }, { "commit": "ad8f955daf77d303f0ee08d2acab30d3886cbd2b", "tree": "325095c2c9411c3ca753be57e83ef31d4979d57b", "parents": [ "fbe3364ac4fa82caa585f98e4a525946d2cc21f4" ], "author": { "name": "Geert Uytterhoeven", "email": "geert@linux-m68k.org", "time": "Mon Dec 26 20:32:02 2011 +0100" }, "committer": { "name": "Greg Ungerer", "email": "gerg@uclinux.org", "time": "Fri Dec 30 10:20:49 2011 +1000" }, "message": "m68k/Kconfig: Separate classic m68k and coldfire early\n\nWhile you can build multiplatform kernels for machines with classic\nm68k processors, you cannot mix support for classic m68k and coldfire\nprocessors. To avoid such hybrid kernels, introduce CONFIG_M68KCLASSIC\nas an antipole for CONFIG_COLDFIRE, and make all specific processor\nsupport depend on one of them.\nAll classic m68k machine support also needs to depend on this.\n\nThe defaults (CONFIG_M68KCLASSIC if MMU, CONFIG_COLDFIRE if !MMU) are\nchosen such to make most of the existing configs build and work.\n\nSigned-off-by: Geert Uytterhoeven \u003cgeert@linux-m68k.org\u003e\nSigned-off-by: Greg Ungerer \u003cgerg@uclinux.org\u003e\n" }, { "commit": "e08d703cc2ab6e47dbd10a74eb029f7dfa93d71d", "tree": "f81a41ca2a92ed39a723b024b984d220373e6e01", "parents": [ "2c9b82adb5ea65745d5d73d97bb0e1cc16cba4a0" ], "author": { "name": "Greg Ungerer", "email": "gerg@uclinux.org", "time": "Fri Oct 14 14:43:30 2011 +1000" }, "committer": { "name": "Greg Ungerer", "email": "gerg@uclinux.org", "time": "Fri Dec 30 10:20:21 2011 +1000" }, "message": "m68k: modify user space access functions to support ColdFire CPUs\n\nModify the user space access functions to support the ColdFire V4e cores\nrunning with MMU enabled.\n\nThe ColdFire processors do not support the \"moves\" instruction used by\nthe traditional 680x0 processors for moving data into and out of another\naddress space. They only support the notion of a single address space,\nand you use the usual \"move\" instruction to access that.\n\nCreate a new config symbol (CONFIG_CPU_HAS_ADDRESS_SPACES) to mark the\nCPU types that support separate address spaces, and thus also support\nthe sfc/dfc registers and the \"moves\" instruction that go along with that.\n\nThe code is almost identical for user space access, so lets just use a\ndefine to choose either the \"move\" or \"moves\" in the assembler code.\n\nSigned-off-by: Greg Ungerer \u003cgerg@uclinux.org\u003e\nAcked-by: Matt Waddel \u003cmwaddel@yahoo.com\u003e\nAcked-by: Kurt Mahan \u003ckmahan@xmission.com\u003e\nAcked-by: Geert Uytterhoeven \u003cgeert@linux-m68k.org\u003e\n" }, { "commit": "84f3fb7a2aadeda3c0a34e61591a8eccf5e367b4", "tree": "a1d64dd3c6da8726cb74bb206d4da15228cfdae2", "parents": [ "7f73bafc4630a450ebe8b021efa14781ffd992b1" ], "author": { "name": "Greg Ungerer", "email": "gerg@uclinux.org", "time": "Fri Nov 11 15:13:08 2011 +1000" }, "committer": { "name": "Greg Ungerer", "email": "gerg@uclinux.org", "time": "Sat Dec 24 21:47:57 2011 +1000" }, "message": "m68k: handle presence of 64bit mul/div instructions cleanly\n\nThe traditional 68000 processors and the newer reduced instruction set\nColdFire processors do not support the 32*32-\u003e64 multiply or the 64/32-\u003e32\ndivide instructions. This is not a difference based on the presence of\na hardware MMU or not.\n\nCreate a new config symbol to mark that a CPU type doesn\u0027t support the\nlonger multiply/divide instructions. Use this then as a basis for using\nthe fast 64bit based divide (in div64.h) and for linking in the extra\nlibgcc functions that may be required (mulsi3, divsi3, etc).\n\nSigned-off-by: Greg Ungerer \u003cgerg@uclinux.org\u003e\nAcked-by: Geert Uytterhoeven \u003cgeert@linux-m68k.org\u003e\n" }, { "commit": "7f73bafc4630a450ebe8b021efa14781ffd992b1", "tree": "81d6448d479d48e5c93f6a444a6e5431a63aff4a", "parents": [ "479badc364b52774d77264aaf81f4d4b375a4a97" ], "author": { "name": "Greg Ungerer", "email": "gerg@uclinux.org", "time": "Tue Oct 18 15:49:19 2011 +1000" }, "committer": { "name": "Greg Ungerer", "email": "gerg@uclinux.org", "time": "Sat Dec 24 21:47:57 2011 +1000" }, "message": "m68k: simpler m68k and ColdFire CPU\u0027s can use generic csum code\n\nWe have two implementations of the IP checksuming code for the m68k arch.\nOne uses the more advanced instructions available in 68020 and above\nprocessors, the other uses the simpler instructions available on the\noriginal 68000 processors and the modern ColdFire processors.\n\nThis simpler code is pretty much the same as the generic lib implementation\nof the IP csum functions. So lets just switch over to using that. That\nmeans we can completely remove the checksum_no.c file, and only have the\nlocal fast code used for the more complex 68k CPU family members.\n\nSigned-off-by: Greg Ungerer \u003cgerg@uclinux.org\u003e\n" }, { "commit": "5717a02becd2f5dae8b11cb5808de4e5369d607c", "tree": "829e1e28b20ea1284cbaabe2c3e3083a94d143fd", "parents": [ "d25ba98afce7c87afa39f553a3ff8effed87db03" ], "author": { "name": "Greg Ungerer", "email": "gerg@uclinux.org", "time": "Wed Oct 19 16:27:30 2011 +1000" }, "committer": { "name": "Greg Ungerer", "email": "gerg@uclinux.org", "time": "Sat Dec 24 21:47:57 2011 +1000" }, "message": "m68k: selection of GENERIC_ATOMIC64 is not MMU specific\n\nThe selection of the CONFIG_GENERIC_ATOMIC64 option is not specific to the\nMMU being present and enabled. It is a property of certain CPU families.\nSo select it based on those CPU types being selected.\n\nSigned-off-by: Greg Ungerer \u003cgerg@uclinux.org\u003e\n" }, { "commit": "0e152d80507b75c00aac60f2ffc586360687cd52", "tree": "786a8ab6c69b15dfbc6b34072c7e66f7339a4b9c", "parents": [ "89127ed381fb244aa51c1a74ed695a1f3578ef7d" ], "author": { "name": "Greg Ungerer", "email": "gerg@uclinux.org", "time": "Mon Jun 20 15:49:09 2011 +1000" }, "committer": { "name": "Greg Ungerer", "email": "gerg@uclinux.org", "time": "Tue Oct 18 14:22:25 2011 +1000" }, "message": "m68k: reorganize Kconfig options to improve mmu/non-mmu selections\n\nThe current mmu and non-mmu Kconfig files can be merged to form\na more general selection of options. The current break up of options\nis due to the simple brute force merge from the m68k and m68knommu\narch directories.\n\nMany of the options are not at all specific to having the MMU enabled\nor not. They are actually associated with a particular CPU type or\nplatform type.\n\nUltimately as we support all processors with the MMU disabled we need\nmany of these options to be selectable without the MMU option enabled.\nAnd likewise some of the ColdFire processors, which currently are only\nsupported with the MMU disabled, do have MMU hardware, and will need\nto have options selected on CPU type, not MMU disabled.\n\nThis patch removes the old mmu and non-mmu Kconfigs and instead breaks\nup the configuration into four areas: cpu, machine, bus, devices.\n\nThe Kconfig.cpu lists all the options associated with selecting a CPU,\nand includes options specific to each CPU type as well.\n\nKconfig.machine lists all options associated with selecting a machine\ntype. Almost always the machines selectable is restricted by the chosen\nCPU.\n\nKconfig.bus contains options associated with selecting bus types on the\nvarious machine types. That includes PCI bus, PCMCIA bus, etc.\n\nKconfig.devices contains options for drivers and driver associated\noptions.\n\nSigned-off-by: Greg Ungerer \u003cgerg@uclinux.org\u003e\n" } ] }