GitHub PushEvent at 2014-12-22 08:03:02
Repository: kernel_msm
Actor: billchen1977
Payload: {"shas":[["6f6b47b3ebec5cd4c30b4807e975fecd5637b2b4","2a0259761cc3e88db42be5300c1579a67c77e65e@samsung.com","mm: cma: fix alignment requirements for contiguous regions\n\nContiguous Memory Allocator requires each of its regions to be aligned\nin such a way that it is possible to change migration type for all\npageblocks holding it and then isolate page of largest possible order from\nthe buddy allocator (which is MAX_ORDER-1). This patch relaxes alignment\nrequirements by one order, because MAX_ORDER alignment is not really\nneeded.\n\nChange-Id: I57798e709636873da27520bc42f7bdb03af15beb\nSigned-off-by: Marek Szyprowski <m.szyprowski@samsung.com>\nCC: Michal Nazarewicz <mina86@mina86.com>\nAcked-by: Michal Nazarewicz <mina86@mina86.com>\nSigned-off-by: Laura Abbott <lauraa@codeaurora.org>","Marek Szyprowski",true],["968ef98247e6417af9e4e3b772715118e08962fc","e15bea67e0bd782de26f1c3a3259ad680ed0e6e8@ti.com","drivers: cma: represent physical addresses as phys_addr_t\n\nThis commit changes the CMA early initialization code to use phys_addr_t\nfor representing physical addresses instead of unsigned long.\n\nWithout this change, among other things, dma_declare_contiguous() simply\ndiscards any memory regions whose address is not representable as unsigned\nlong.\n\nThis is a problem on 32-bit PAE machines where unsigned long is 32-bit\nbut physical address space is larger.\n\nChange-Id: I0651ae4bfdbd86139398433f4a3f632efd482b8a\nSigned-off-by: Vitaly Andrianov <vitalya@ti.com>\nSigned-off-by: Cyril Chemparathy <cyril@ti.com>\nAcked-by: Michal Nazarewicz <mina86@mina86.com>\nSigned-off-by: Marek Szyprowski <m.szyprowski@samsung.com>\nSigned-off-by: Laura Abbott <lauraa@codeaurora.org>","Vitaly Andrianov",true],["8ffa0971b922a3670c04cf29a322b4d33d3725e7","2a0259761cc3e88db42be5300c1579a67c77e65e@samsung.com","mm: cma: fix condition check when setting global cma area\n\ndev_set_cma_area incorrectly assigned cma to global area on first call\ndue to incorrect check. This patch fixes this issue.\n\nChange-Id: I24f410bb08c1419e1f8408f30536d82886e104e0\nSigned-off-by: Marek Szyprowski <m.szyprowski@samsung.com>\nSigned-off-by: Laura Abbott <lauraa@codeaurora.org>","Marek Szyprowski",true],["c9b3d7231e794f93b8612424f8aaa4a7a3f5ae59","605208d9b4c769ca62e9f9f8b592c9cd465fe6d7@mina86.com","drivers: dma-contiguous: refactor dma_alloc_from_contiguous()\n\nThe dma_alloc_from_contiguous() function returns either a valid pointer\nto a page structure or NULL, the error code set when pageno >= cma->count\nis not used at all and can be safely removed.\n\nThis commit also changes the function to avoid goto and have only one exit\npath and one place where mutex is unlocked.\n\nChange-Id: I6de94bd6fbe2288382ca9b5e5a1f691aabe0bae5\nSigned-off-by: Michal Nazarewicz <mina86@mina86.com>\n[fixed compilation break caused by missing semicolon]\nSigned-off-by: Marek Szyprowski <m.szyprowski@samsung.com>\nSigned-off-by: Laura Abbott <lauraa@codeaurora.org>","Michal Nazarewicz",true],["1442cc64e398773e490d89c37b591e58b8be6b32","2a0259761cc3e88db42be5300c1579a67c77e65e@samsung.com","drivers: dma-contiguous: clean source code and prepare for device tree\n\nThis patch cleans the initialization of dma contiguous framework. The\nall-in-one dma_declare_contiguous() function is now separated into\ndma_contiguous_reserve_area() which only steals the the memory from\nmemblock allocator and dma_contiguous_add_device() function, which\nassigns given device to the specified reserved memory area. This improves\nthe flexibility in defining contiguous memory areas and assigning device\nto them, because now it is possible to assign more than one device to\nthe given contiguous memory area. This split in initialization is also\nrequired for upcoming device tree support.\n\nChange-Id: Ibddd1c9abc6550ee62b09645e7a3355256838bfe\nSigned-off-by: Marek Szyprowski <m.szyprowski@samsung.com>\nAcked-by: Kyungmin Park <kyungmin.park@samsung.com>\nSigned-off-by: Laura Abbott <lauraa@codeaurora.org>","Marek Szyprowski",true],["89e348bcde23133384cd83399fec688bd1983e72","2a0259761cc3e88db42be5300c1579a67c77e65e@samsung.com","drivers: dma-contiguous: add initialization from device tree\n\nAdd device tree support for contiguous memory regions defined in device\ntree. Initialization is done in 2 steps. First, the contiguous memory is\nreserved, what happens very early, when only flattened device tree is\navailable. Then on device initialization the corresponding cma regions are\nassigned to device structures.\n\nChange-Id: Ic242499b64875ee57a346d7cbc8a34ebd64e68d2\nSigned-off-by: Marek Szyprowski <m.szyprowski@samsung.com>\nAcked-by: Kyungmin Park <kyungmin.park@samsung.com>\nSigned-off-by: Laura Abbott <lauraa@codeaurora.org>","Marek Szyprowski",true],["d15467c46f9994873e86578e08ff4326018d25db","e7b4910f4742918f5926c991d8a2cd122ac7e295@codeaurora.org","cma: Remove __init annotations from data structures\n\nSeveral of the CMA data structures are used after initialization\nremove the __init annotations from them.\n\nChange-Id: Iff48ed88eef7b8fffdfba4b868cc69ded3c6df42\nSigned-off-by: Laura Abbott <lauraa@codeaurora.org>","Laura Abbott",true],["437b65558ccee02bbd0c8efffdd9756b78232514","e7b4910f4742918f5926c991d8a2cd122ac7e295@codeaurora.org","cma: Fix up devicetree bindings\n\nThe correct binding for regions is linux,contiguous-regions.\nFix it.\n\nChange-Id: I4bbb4cd3e880c75d917b5a5a081861b3197adfa3\nSigned-off-by: Laura Abbott <lauraa@codeaurora.org>","Laura Abbott",true],["e5b374508b49698d20e7c5e948f0f542627d9feb","e7b4910f4742918f5926c991d8a2cd122ac7e295@codeaurora.org","cma: Add support for associating regions by name\n\nCurrently, the devicetree lookup code assumes that all\nCMA regions are present at a fixed address and uses the\nfixed address for associating CMA regions to devices.\nThis presents a problem for dynamically assigning regions.\nDevice names get mangled/changed between flattened and\npopulated devicetree so relying on that is unworkable.\nAdd a separate name binding to allow lookup later between\ndevices.\n\nChange-Id: Iaacd9888ea708d7293f1120e2b8c473c5c601f3d\nSigned-off-by: Laura Abbott <lauraa@codeaurora.org>","Laura Abbott",true],["8c86e9034a593ee7bf5d07d33067b6018c53a0dd","e7b4910f4742918f5926c991d8a2cd122ac7e295@codeaurora.org","cma: Remove restriction on region names\n\nCMA currently restricts region names to 'region@x'. Devicetree\ndoes not support the same value of x to be used multiple times.\nThis means that the devicetree cannot have multiple regions\nbe dynamically placed (x = 0). Remove the naming restriction\nfor CMA regions.\n\nChange-Id: If647f8d7e6323497952431ae5b8cae05ba17af50\nSigned-off-by: Laura Abbott <lauraa@codeaurora.org>\n\nConflicts:\n\n\tarch/arm/boot/dts/msm8974.dtsi","Laura Abbott",true],["fa6aad8ea80ee361ca36946fce1c8c17a287388b","e7b4910f4742918f5926c991d8a2cd122ac7e295@codeaurora.org","cma: use MEMBLOCK_ALLOC_ANYWHERE for placing CMA regions\n\nMEMBLOCK_ALLOC_ANYWHERE allocates blocks from anywhere,\nincluding highmem. Use this flag to allow CMA regions to\nbe placed in highmem as opposed to lowmem.\n\nChange-Id: Id5fa36a96e46d60f0e898d764a1f4c8a0a37f5f8\nSigned-off-by: Laura Abbott <lauraa@codeaurora.org>","Laura Abbott",true],["21d86fee2ec0c8a855f5f8e8f953aa1705df44a7","d743fabf68972021b40d6c2990e30885564a88d9@gmail.com","drivers: dma-contiguous: fix compile error when CONFIG_OF not defined","cb",true],["d8a569d15b6ae25d8e4610572337bceab89c8d83","2a0259761cc3e88db42be5300c1579a67c77e65e@samsung.com","mm: vmalloc: use const void * for caller argument\n\n'const void *' is a safer type for caller function type. This patch\nupdates all references to caller function type.\n\nChange-Id: If950cfcfc63911756ac3709c8bf6da10c8b98f1b\nSigned-off-by: Marek Szyprowski <m.szyprowski@samsung.com>\nReviewed-by: Kyungmin Park <kyungmin.park@samsung.com>\nReviewed-by: Minchan Kim <minchan@kernel.org>\nGit-commit: 5e6cafc83e30f0f70c79a2b7aef237dc57e29f02\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\nSigned-off-by: Laura Abbott <lauraa@codeaurora.org>","Marek Szyprowski",true],["bf7e2d1b084417e93d289811965b547091bfbf36","f6aa0246ff943bfa8602cdf60d40c481b38ed232@arm.linux.org.uk","ARM: DMA: Fix struct page iterator in dma_cache_maint() to work with sparsemem\n\nSubhash Jadavani reported this partial backtrace:\n  Now consider this call stack from MMC block driver (this is on the ARMv7\n  based board):\n\n  [<c001b50c>] (v7_dma_inv_range+0x30/0x48) from [<c0017b8c>] (dma_cache_maint_page+0x1c4/0x24c)\n  [<c0017b8c>] (dma_cache_maint_page+0x1c4/0x24c) from [<c0017c28>] (___dma_page_cpu_to_dev+0x14/0x1c)\n  [<c0017c28>] (___dma_page_cpu_to_dev+0x14/0x1c) from [<c0017ff8>] (dma_map_sg+0x3c/0x114)\n\nThis is caused by incrementing the struct page pointer, and running off\nthe end of the sparsemem page array.  Fix this by incrementing by pfn\ninstead, and convert the pfn to a struct page.\n\nChange-Id: I52966616d710420aa28529ba650e9177dcb0e731\nCc: <stable@vger.kernel.org>\nSuggested-by: James Bottomley <JBottomley@Parallels.com>\nTested-by: Subhash Jadavani <subhashj@codeaurora.org>\nSigned-off-by: Russell King <rmk+kernel@arm.linux.org.uk>\nSigned-off-by: Subhash Jadavani <subhashj@codeaurora.org>\nPatch-mainline: v3.8\nGit-commit: 15653371c67c3fbe359ae37b720639dd4c7b42c5\nSigned-off-by: Stephen Boyd <sboyd@codeaurora.org>","Russell King",true],["7103111b4b25fdac8e7d8c49f98eb8dd7dc87b9e","2a0259761cc3e88db42be5300c1579a67c77e65e@samsung.com","ARM: dma-mapping: add support for CMA regions placed in highmem zone\n\nThis patch adds missing pieces to correctly support memory pages served\nfrom CMA regions placed in high memory zones. Please note that the default\nglobal CMA area is still put into lowmem and is limited by optional\narchitecture specific DMA zone. One can however put device specific CMA\nregions in high memory zone to reduce lowmem usage.\n\nChange-Id: I92ae4a772f24e0ca90c5560a826207850618b506\nSigned-off-by: Marek Szyprowski <m.szyprowski@samsung.com>\n[lauraa@codeaurora.org: Context fixups]\nSigned-off-by: Laura Abbott <lauraa@codeaurora.org>","Marek Szyprowski",true],["8ca79fee842125fc10965b1b2f6335b925721e12","e7b4910f4742918f5926c991d8a2cd122ac7e295@codeaurora.org","ARM: dma-mapping: Allow highmem pages to not have a mapping\n\nThe DMA_ATTR_NO_KERNEL_MAPPING is used to make sure that CMA\npages have no kernel mapping. Add support to make sure that\nhighmem pages have no mapping.\n\nChange-Id: Ife76df126ecfedf0dba81a35e0de8a1787355b3d\nSigned-off-by: Laura Abbott <lauraa@codeaurora.org>","Laura Abbott",true],["ada433328eaab4b441d8cbd7ba86ee93a52ab9fa","2a0259761cc3e88db42be5300c1579a67c77e65e@samsung.com","ARM: mm: fix type of the arm_dma_limit global variable\n\narm_dma_limit stores physical address of maximal address accessible by DMA,\nso the phys_addr_t type makes much more sense for it instead of u32. This\npatch fixes the following build warning:\n\narch/arm/mm/init.c:380: warning: comparison of distinct pointer types lacks a cast\n\nChange-Id: Iaba492cb9d35692b0830239b044f9c4e32d7ac16\nReported-by: Russell King <linux@arm.linux.org.uk>\nSigned-off-by: Marek Szyprowski <m.szyprowski@samsung.com>\nSigned-off-by: Stepan Moskovchenko <stepanm@codeaurora.org>","Marek Szyprowski",true],["ee66b50c198d76e11f83ee16ff2c643926889b16","f6aa0246ff943bfa8602cdf60d40c481b38ed232@arm.linux.org.uk","ARM: fix warning caused by wrongly typed arm_dma_limit\n\narch/arm/mm/init.c: In function 'arm_memblock_init':\narch/arm/mm/init.c:380: warning: comparison of distinct pointer types lacks a cast\n\nby fixing the typecast in its definition when DMA_ZONE is disabled.\nThis was missed in 4986e5c7c (ARM: mm: fix type of the arm_dma_limit\nglobal variable).\n\nChange-Id: Id076f2bebe307609265afdd4229181d2004c5f9c\nSigned-off-by: Russell King <rmk+kernel@arm.linux.org.uk>\nSigned-off-by: Stepan Moskovchenko <stepanm@codeaurora.org>","Russell King",true],["79e153028791b35521eb2cca1330e0891754e503","fac1ee8d9953f745793eb48675579af79bf364d7@broadcom.com","ARM: mm: fix MMU mapping of CMA regions\n\nFix dma_contiguous_remap() so that it continues through all the\nregions, even after encountering one that is outside lowmem.\nWithout this change, if you have two CMA regions, the first outside\nlowmem and the seocnd inside lowmem, only the second one will get\nset up in the MMU. Data written to that region then doesn't get\nautomatically flushed from the cache into memory.\n\nChange-Id: I5f15fd4c01e1743e83e1067e2fca6a6411ea6e08\nSigned-off-by: Chris Brand <cbrand@broadcom.com>\n[extended patch subject with 'fix' word]\nSigned-off-by: Marek Szyprowski <m.szyprowski@samsung.com>\nGit-commit: 39f78e70567a07a6fc0d7a4ca9e3331e44dd400d\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\nSigned-off-by: Laura Abbott <lauraa@codeaurora.org>","Chris Brand",true],["9c89451ee82fdffb2134335d00dca7a7cf22fcbf","2a0259761cc3e88db42be5300c1579a67c77e65e@samsung.com","ARM: dma-mapping: remove custom consistent dma region\n\nThis patch changes dma-mapping subsystem to use generic vmalloc areas\nfor all consistent dma allocations. This increases the total size limit\nof the consistent allocations and removes platform hacks and a lot of\nduplicated code.\n\nAtomic allocations are served from special pool preallocated on boot,\nbecause vmalloc areas cannot be reliably created in atomic context.\n\nChange-Id: Ibb2230e80249598a81122083bf3fa2f050a0a71e\nSigned-off-by: Marek Szyprowski <m.szyprowski@samsung.com>\nReviewed-by: Kyungmin Park <kyungmin.park@samsung.com>\nReviewed-by: Minchan Kim <minchan@kernel.org>\nGit-commit: e9da6e9905e639b0f842a244bc770b48ad0523e9\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\n[lauraa@codeaurora.org: Context fixups and tweaking of some prototypes]\nSigned-off-by: Laura Abbott <lauraa@codeaurora.org>","Marek Szyprowski",true]],"size":41,"ref":"refs/heads/android-msm-sony-fuji-3.4-lollipop","head":"0ed0d943525d40d723b7573b826ec7fbc57ac920"}