msm: logo: update from shinano (z2)

* From 17.1.F.0.60

Change-Id: I87b8e74ef1053b837be00c53ad6fba669257f628
msm: mdss: update to shinano (z2)

* From 17.1.F.0.60

Change-Id: I6956641f70ec3d4ae7bb75f2b7876a734f188570
backlight: update LP855x driver

* From 17.F.1.0.60

Change-Id: I10e800e57ca624eddc07b8ce7958b96485af9df4
vm: add vm_iomap_memory() helper function

Various drivers end up replicating the code to mmap() their memory
buffers into user space, and our core memory remapping function may be
very flexible but it is unnecessarily complicated for the common cases
to use.

Our internal VM uses pfn's ("page frame numbers") which simplifies
things for the VM, and allows us to pass physical addresses around in a
denser and more efficient format than passing a "phys_addr_t" around,
and having to shift it up and down by the page size.  But it just means
that drivers end up doing that shifting instead at the interface level.

It also means that drivers end up mucking around with internal VM things
like the vma details (vm_pgoff, vm_start/end) way more than they really
need to.

So this just exports a function to map a certain physical memory range
into user space (using a phys_addr_t based interface that is much more
natural for a driver) and hides all the complexity from the driver.
Some drivers will still end up tweaking the vm_page_prot details for
things like prefetching or cacheability etc, but that's actually
relevant to the driver, rather than caring about what the page offset of
the mapping is into the particular IO memory region.

Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
fbmem: update from 17.1.F.0.60

Change-Id: I02b2b293a492fa7415da9b2aaf145cb1f04e59f1