{"push_id":2106849318,"size":7,"distinct_size":0,"ref":"refs/heads/caf/3.10/caf/chromium-googlesource-kernel-next/chromeos-4.14-media","head":"8695978347c65df4ee3c1f818e74a80c85880997","before":"207292f2ce37c8c968e59d7a328baf89363d6ad8","commits":[{"sha":"33f6d57a169fef4550630a497ec5b50ed07443f9","author":{"name":"John Sheu","email":"36f42bdfd5f5571254c2219874db1f8cc8512335@chromium.org"},"message":"CHROMIUM: v4l2-mem2mem: allow reqbufs(0) with \"in use\" MMAP buffers\n\nv4l2-mem2mem presently does not allow VIDIOC_REQBUFS to destroy\noutstanding buffers if the queue is of type V4L2_MEMORY_MMAP, and if the\nbuffers are considered \"in use\".  This is different behavior than for\nother memory types, and prevents us for deallocating buffers in a few\ncases:\n\n* In the case that there are outstanding mmap()ed views on the buffer,\n  refcounting on the videobuf2 buffer backing the vm_area will track\n  lifetime appropriately,\n* In the case that the buffer has been exported as a DMABUF, refcounting\n  on the videobuf2 bufer backing the DMABUF will track lifetime\n  appropriately.\n\nRemove the specific check for type V4L2_MEMOMRY_MMAP when freeing all\nbuffers through VIDIOC_REQBUFS.\n\nSigned-off-by: John Sheu <sheu@google.com>\n\nBUG=chromium:167417\nTEST=local build, run on snow\n\nReviewed-on: https://chromium-review.googlesource.com/177691\nReviewed-by: Pawel Osciak <posciak@chromium.org>\nCommit-Queue: John Sheu <sheu@chromium.org>\nTested-by: John Sheu <sheu@chromium.org>\n(cherry picked from commit fb7d83cf51eb4781bbe429d9974ea5ae3e2f1185)\nSigned-off-by: Pawel Osciak <posciak@chromium.org>\n\nOriginal-Change-Id: Ia3ee651473cc790cdafad574f8b0fd85cc1d2685\nReviewed-on: https://chromium-review.googlesource.com/238673\nReviewed-by: Tomasz Figa <tfiga@chromium.org>\nTested-by: Tomasz Figa <tfiga@chromium.org>\nTested-by: Pawel Osciak <posciak@chromium.org>\nCommit-Queue: Pawel Osciak <posciak@chromium.org>\n(cherry picked from commit 79636e25fb6d84883bb89fe813f3a488c6cb368d)\nSigned-off-by: Pawel Osciak <posciak@chromium.org>\n\nChange-Id: I4e29a4e8ef4a771e4c7efb4c925010c1e30ab536\nReviewed-on: https://chromium-review.googlesource.com/302512\nCommit-Ready: Pawel Osciak <posciak@chromium.org>\nTested-by: Pawel Osciak <posciak@chromium.org>\nReviewed-by: Duncan Laurie <dlaurie@chromium.org>\n\nConflicts:\n\tdrivers/media/v4l2-core/videobuf2-core.c\n\n[rebase44(groeck): Resolved conflicts]\nSigned-off-by: Guenter Roeck <groeck@chromium.org>\n\nConflicts:\n\tdrivers/media/v4l2-core/videobuf2-core.c\n\n[rebase412(groeck): Resolved conflicts]\nSigned-off-by: Guenter Roeck <groeck@chromium.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/33f6d57a169fef4550630a497ec5b50ed07443f9"},{"sha":"9031a7163ab3179965fee8190834fa5b667d0bc9","author":{"name":"Pawel Osciak","email":"7a533dace243b399ce28deb7520adefd3a31efb7@chromium.org"},"message":"CHROMIUM: vb2: Don't reuse USERPTR buffers.\n\nThe logic in vb2 USERPTR implementation assumes that userspace will always\nuse the same V4L2 buffer index with one virtual address for the duration\nof its usage. Based on that, it does not release a pinned buffer, even when\nit is returned to userspace, until a different address is queued for the\nsame index, because it assumes that when that happens, the userspace has\nchanged the working set of buffers and the old set is not in use anymore.\n\nHowever, if userspace does not maintain a constant address to index\nrelationship, vb2 will release the previous buffer pinned for that index\nat the time of queuing the new one, which is after the old buffer has been\nreturned to the userspace. That may be destructive if that buffer is\nalready in use elsewhere at that time, as userspace expects that kernel\ndisclaimed the old buffer before it was dequeued.\n\nSigned-off-by: Pawel Osciak <posciak@chromium.org>\n\nTEST=corruption test with V4L2VEA\nBUG=chrome-os-partner:35860\n\nOriginal-Change-Id: I10c67f89aaea7fb5247a223aad4ac9728817af7a\nReviewed-on: https://chromium-review.googlesource.com/246970\nReviewed-by: Tomasz Figa <tfiga@chromium.org>\nTested-by: Pawel Osciak <posciak@chromium.org>\nCommit-Queue: Pawel Osciak <posciak@chromium.org>\n(cherry picked from commit f0ce3a1a20ebc892ab478b127b680ba9a305adbb)\nSigned-off-by: Pawel Osciak <posciak@chromium.org>\n\nChange-Id: I836fe0165ec08a78d6b9cb91e03e994163035e23\nReviewed-on: https://chromium-review.googlesource.com/302513\nCommit-Ready: Pawel Osciak <posciak@chromium.org>\nTested-by: Pawel Osciak <posciak@chromium.org>\nReviewed-by: Duncan Laurie <dlaurie@chromium.org>\n\nConflicts:\n\tdrivers/media/v4l2-core/videobuf2-core.c\n\n[rebase44(groeck): Resolved conflicts]\nSigned-off-by: Guenter Roeck <groeck@chromium.org>\n\nConflicts:\n\tdrivers/media/v4l2-core/videobuf2-core.c\n\n[rebase412(groeck): Resolved conflicts]\nSigned-off-by: Guenter Roeck <groeck@chromium.org>\n\n[rebase414(lannm): Resolved conflicts]\nSigned-off-by: Lann Martin <lannm@chromium.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/9031a7163ab3179965fee8190834fa5b667d0bc9"},{"sha":"fd12d62dea7ab6dd40a795334d2c5b1a17a569e6","author":{"name":"Pawel Osciak","email":"7a533dace243b399ce28deb7520adefd3a31efb7@chromium.org"},"message":"CHROMIUM: v4l: Add V4L2_CID_MPEG_VIDEO_H264_SPS_PPS_BEFORE_IDR\n\nWhen set, the V4L2_CID_MPEG_VIDEO_H264_SPS_PPS_BEFORE_IDR control requests\nan H.264 encoder to insert an SPS and PPS pair before each IDR.\n\nSigned-off-by: Pawel Osciak <posciak@chromium.org>\n\nBUG=chromium:639238\nTEST=veaunittest\n\nChange-Id: I17b41a8a3e228338f5c59dcdfb38ca04cfa5119b\nReviewed-on: https://chromium-review.googlesource.com/373286\nCommit-Ready: Pawel Osciak <posciak@chromium.org>\nTested-by: Pawel Osciak <posciak@chromium.org>\nReviewed-by: Tomasz Figa <tfiga@chromium.org>\n\nConflicts:\n\tdrivers/media/v4l2-core/v4l2-ctrls.c\n\tinclude/uapi/linux/v4l2-controls.h\n\n[rebase412(groeck): Context conflicts]\nSigned-off-by: Guenter Roeck <groeck@chromium.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/fd12d62dea7ab6dd40a795334d2c5b1a17a569e6"},{"sha":"46c3ad3708660ce644541e07d610b72f37045d20","author":{"name":"Pawel Osciak","email":"7a533dace243b399ce28deb7520adefd3a31efb7@chromium.org"},"message":"HACK: [media] vb2: Don't unmap a dmabuf while dequeueing\n\nThe hardware still needs to read from those buffers as reference\nframes while decoding. To solve the issue, a dmabuf cannot be\nunmapped when it was dequeued. No memory will leaked since the dmabuf\nwill still be unmapped and detached when the buffer is put.\n\nBUG=643033\nTEST=Play YT and ApiDemo on ARC\nSigned-off-by: Pawel Osciak <posciak@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/334103\nCommit-Ready: Owen Lin <owenlin@chromium.org>\nTested-by: Owen Lin <owenlin@chromium.org>\nReviewed-by: Tomasz Figa <tfiga@chromium.org>\n\nChange-Id: I863cade2732971dc9a8e1818e4e3bd8dc1f0ddb7\nReviewed-on: https://chromium-review.googlesource.com/378738\nCommit-Ready: Owen Lin <owenlin@chromium.org>\nTested-by: Owen Lin <owenlin@chromium.org>\nReviewed-by: Tomasz Figa <tfiga@chromium.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/46c3ad3708660ce644541e07d610b72f37045d20"},{"sha":"8ee16f92ed2e64265c6af9d7a69418eb348913ca","author":{"name":"Sakari Ailus","email":"20e5d1d02c2f1dd1e848b2d45f5d9cb636f7f9d6@linux.intel.com"},"message":"FROMLIST: vb2: Move cache synchronisation from buffer done to dqbuf handler\n\nThe cache synchronisation may be a time consuming operation and thus not\nbest performed in an interrupt which is a typical context for\nvb2_buffer_done() calls. This may consume up to tens of ms on some\nmachines, depending on the buffer size.\n\nSigned-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>\n\n(am from https://patchwork.kernel.org/patch/9477165/)\nSigned-off-by: Ricky Liang <jcliang@chromium.org>\n\nBUG=chrome-os-partner:60805\nTEST=build chromeos-4.4 for elm and boot\nTEST=build chromeos-4.4 for kevin and boot\n\nBUG=chrome-os-partner:43703\nTEST=Compiled and tested on Elm.\n\nReviewed-on: https://chromium-review.googlesource.com/422719\nReviewed-by: Tomasz Figa <tfiga@chromium.org>\n\nChange-Id: I6b454f461ad57d0fa80c32aa4ec45d71e881435a\nReviewed-on: https://chromium-review.googlesource.com/427575\nCommit-Ready: Daniel Kurtz <djkurtz@chromium.org>\nTested-by: Daniel Kurtz <djkurtz@chromium.org>\nReviewed-by: Ricky Liang <jcliang@chromium.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/8ee16f92ed2e64265c6af9d7a69418eb348913ca"},{"sha":"15a5c5840c17cb37622adff8acba02253f8bcd88","author":{"name":"Sakari Ailus","email":"20e5d1d02c2f1dd1e848b2d45f5d9cb636f7f9d6@linux.intel.com"},"message":"FROMLIST: vb2: Anticipate queue specific DMA attributes for USERPTR buffers\n\nThe DMA attributes were available for the memop implementation for MMAP\nbuffers but not for USERPTR buffers. Do the same for USERPTR. This patch\nmakes no functional changes.\n\nSigned-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>\n(am from https://patchwork.kernel.org/patch/9716359/)\nSigned-off-by: Alexandre Courbot <acourbot@chromium.org>\nSigned-off-by: Guenter Roeck <groeck@chromium.org>\n\nChange-Id: Idc36180652a332ba2f55dfa00c69c6d512c50507","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/15a5c5840c17cb37622adff8acba02253f8bcd88"},{"sha":"8695978347c65df4ee3c1f818e74a80c85880997","author":{"name":"Sakari Ailus","email":"20e5d1d02c2f1dd1e848b2d45f5d9cb636f7f9d6@linux.intel.com"},"message":"FROMLIST: vb2: dma-sg: Let drivers decide DMA attrs of MMAP and USERPTR bufs\n\nThe desirable DMA attributes are not generic for all devices using\nVideobuf2 scatter-gather DMA ops. Let the drivers decide.\n\nAs a result, also the DMA-BUF exporter must provide ops for\nsynchronising\nthe cache. This adds begin_cpu_access and end_cpu_access ops to\nvb2_dc_dmabuf_ops.\n\nSigned-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>\n(am from https://patchwork.kernel.org/patch/9716353/)\nSigned-off-by: Alexandre Courbot <acourbot@chromium.org>\nSigned-off-by: Guenter Roeck <groeck@chromium.org>\n\nChange-Id: If5ee12376c148745f7686c955a68cee40d00c14e","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/8695978347c65df4ee3c1f818e74a80c85880997"}]}
{"actor":{"display_login":"akhilnarang"}}