PD#SWPL-58477

Problem:
VPP code style modify

Solution:
VPP code style modify

Verify:
t3

Signed-off-by: yao liu <yao.liu@amlogic.com>
Change-Id: Ifc5bd9222d48c24de435745e9379d8bfe3dede69

PD#SWPL-58477

Problem:
fix error in last commit eac4

Solution:
fix error

Verify:
ohm

Signed-off-by: yao liu <yao.liu@amlogic.com>
Change-Id: I57affad1484c29d29a84eedcf4bc27da6d5fecb3

PD#SWPL-58477

Problem:
coding style issue

Solution:
coding style modify and code clean up

Verify:
Newton

Signed-off-by: yao liu <yao.liu@amlogic.com>
Change-Id: I92d3d3ce091a21178b1bc0d3205716e70a3aa7a7

PD#SWPL-61729
BUG=203412562

Problem:
Release 52 MB of unused memory allocated in "ion-dev"

Solution:
Release 52 MB of unused memory allocated in "ion-dev"

Verify:
adt3-S

Signed-off-by: Liang Ji <liang.ji@amlogic.com>
Change-Id: I87a24212cbf5b6ffac39fff94d52c498b226bb65

PD#SWPL-61507
BUG=202208062

commit 17839856fd588f4ab6b789f482ed3ffd7c403e1f upstream.

Doing a "get_user_pages()" on a copy-on-write page for reading can be
ambiguous: the page can be COW'ed at any time afterwards, and the
direction of a COW event isn't defined.

Yes, whoever writes to it will generally do the COW, but if the thread
that did the get_user_pages() unmapped the page before the write (and
that could happen due to memory pressure in addition to any outright
action), the writer could also just take over the old page instead.

End result: the get_user_pages() call might result in a page pointer
that is no longer associated with the original VM, and is associated
with - and controlled by - another VM having taken it over instead.

So when doing a get_user_pages() on a COW mapping, the only really safe
thing to do would be to break the COW when getting the page, even when
only getting it for reading.

At the same time, some users simply don't even care.

For example, the perf code wants to look up the page not because it
cares about the page, but because the code simply wants to look up the
physical address of the access for informational purposes, and doesn't
really care about races when a page might be unmapped and remapped
elsewhere.

This adds logic to force a COW event by setting FOLL_WRITE on any
copy-on-write mapping when FOLL_GET (or FOLL_PIN) is used to get a page
pointer as a result.

The current semantics end up being:

 - __get_user_pages_fast(): no change. If you don't ask for a write,
   you won't break COW. You'd better know what you're doing.

 - get_user_pages_fast(): the fast-case "look it up in the page tables
   without anything getting mmap_sem" now refuses to follow a read-only
   page, since it might need COW breaking.  Which happens in the slow
   path - the fast path doesn't know if the memory might be COW or not.

 - get_user_pages() (including the slow-path fallback for gup_fast()):
   for a COW mapping, turn on FOLL_WRITE for FOLL_GET/FOLL_PIN, with
   very similar semantics to FOLL_FORCE.

If it turns out that we want finer granularity (ie "only break COW when
it might actually matter" - things like the zero page are special and
don't need to be broken) we might need to push these semantics deeper
into the lookup fault path.  So if people care enough, it's possible
that we might end up adding a new internal FOLL_BREAK_COW flag to go
with the internal FOLL_COW flag we already have for tracking "I had a
COW".

Alternatively, if it turns out that different callers might want to
explicitly control the forced COW break behavior, we might even want to
make such a flag visible to the users of get_user_pages() instead of
using the above default semantics.

But for now, this is mostly commentary on the issue (this commit message
being a lot bigger than the patch, and that patch in turn is almost all
comments), with that minimal "enable COW breaking early" logic using the
existing FOLL_WRITE behavior.

[ It might be worth noting that we've always had this ambiguity, and it
  could arguably be seen as a user-space issue.

  You only get private COW mappings that could break either way in
  situations where user space is doing cooperative things (ie fork()
  before an execve() etc), but it _is_ surprising and very subtle, and
  fork() is supposed to give you independent address spaces.

  So let's treat this as a kernel issue and make the semantics of
  get_user_pages() easier to understand. Note that obviously a true
  shared mapping will still get a page that can change under us, so this
  does _not_ mean that get_user_pages() somehow returns any "stable"
  page ]

[surenb: backport notes
	Replaced (gup_flags | FOLL_WRITE) with write=1 in gup_pgd_range.
	Removed FOLL_PIN usage in should_force_cow_break since it's missing in
	the earlier kernels.
        Since gup_pgd_range does not exist, made appropriate changes on
        the the gup_huge_pgd, gup_huge_pd and gup_pud_range calls]

Reported-by: Jann Horn <jannh@google.com>
Tested-by: Christoph Hellwig <hch@lst.de>
Acked-by: Oleg Nesterov <oleg@redhat.com>
Acked-by: Kirill Shutemov <kirill@shutemov.name>
Acked-by: Jan Kara <jack@suse.cz>
Cc: Andrea Arcangeli <aarcange@redhat.com>
Cc: Matthew Wilcox <willy@infradead.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
[surenb: backport to 4.9 kernel]
Signed-off-by: Suren Baghdasaryan <surenb@google.com>

Signed-off-by: yao zhang1 <yao.zhang1@amlogic.com>
Change-Id: I877999f7b789aee6078ccade2ae54b827d88368f

PD#SWPL-54808
BUG=197895076

Problem:
CtsMediaTestCases 44 DecodeAccuracyTest cases failed

Solution:
add extend column and row for special resolution cts
add dump yuv data interface
add debug flag for cts workaround

Verify:
adt3

Change-Id: Ie461422fddab008d4d905930f5f40a612bb1a98b
Signed-off-by: binqi zhang <binqi.zhang@amlogic.com>
Signed-off-by: Pengfei Zhao <pengfei.zhao@amlogic.com>

SWPL-59636

Problem:
cma shrinker is not standard implement, which may cause
app being unexpected killed

Solution:
use lmkd to kill app.
disable cma shrinker

Signed-off-by: Shuide Chen <shuide.chen@amlogic.com>
Change-Id: I9e510f837047fdb2c8617efb3ba403c69d8f1b9c

* changes:
  ionvideo: support no drop i for cts [1/1]
  v4lvideo: set field V4L2_FIELD_INTERLACED when video is interlace [1/2]

PD#SWPL-54823

Problem:
ionvideo drop i cause cts fail

Solution:
ionvideo not drop i

Verify:
U221

Change-Id: Icbfcb56b69a657a43aaee26428568a5140836167
Signed-off-by: jintao xu <jintao.xu@amlogic.com>

PD#SWPL-32080

Problem:
omx need know interlace or not

Solution:
v4lvideo sent interlace info to omx

Verify:
AH212

Change-Id: I4ce4c5e8aeafe5ed920855cc5e1f3f2245eec9ce
Signed-off-by: jintao xu <jintao.xu@amlogic.com>

debug_fs should be disable in release build and pass XTS

Change-Id: Ica01a743a9ad64dab3c79ff00edea5d92202fd8e

PD#SWPL-57172

Problem:
hal can't receive suspend/resume uevent
on android S + 4.9-q

Solution:
add extra uevents to supplement extcon;
on android S, it will only listen to uevent
on android Q, it will only listen to extcon

Verify:
u221

Change-Id: I52fbe9756a824d6876753ae3ff36c7bb7b9b6f97
Signed-off-by: hang cheng <hang.cheng@amlogic.com>

PD#SWPL-49008

Problem:
hdmi early suspend uevent is not received by sysctl

Solution:
correct hdmipwr uevent init state

Verify:
AC214

Change-Id: I91f4e1643a58d54a8d0ca0f8cf50bd9ab6e1bd13
Signed-off-by: hang cheng <hang.cheng@amlogic.com>

PD#SWPL-56597

Problem:
Current the hdmi resume power uevent is early and before reading
edid, and this will make application can't get sink capability and
set the 480p as default

Solution:
Adjust the hdmi resume power uevent after reading edid

Verify:
g12/u212

Change-Id: I20acd118762d167ccfbf790c8fbace3171b0fda3
Signed-off-by: Zongdong Jiao <zongdong.jiao@amlogic.com>

PD#SWPL-55323

Problem:
the hdmi_pwr is too late in resume

Solution:
head the hdmi_pwr in resume

Verify:
G12/U212

Change-Id: I86bd4dfd0c6b51578cb09fd4fc8902b858de9eae
Signed-off-by: Zongdong Jiao <zongdong.jiao@amlogic.com>

PD#SWPL-57980

Problem:
after the device is powered on
plug in the HDMI cable a few seconds
then OSD panic

Solution:
avoid color_info NULL

Verify:
g12a

Change-Id: I69202bc06d889e59a391b50b609237689eb29d31
Signed-off-by: jian.cao <jian.cao@amlogic.com>

PD#SWPL-57714

Problem:
can't open DEBUG_FS by Kconfig

Solution:
CONFIG_DEBUG_FS=y

Verify:
local

Change-Id: Idc201854cb819c23059f981eab6f7341273ba58e
Signed-off-by: song.han <song.han@amlogic.com>

PD#SWPL-47101

Problem:
CONFIG_AMLOGIC_MEDIA_FB_OSD_SYNC_FENCE depends on CONFIG_DEBUG_FS
and is not enabled in arm32 user version

Solution:
fix depend error

Verify:
s4 ap222

Change-Id: I5ff794630ca933cb33c523b49b83f6185c18182d
Signed-off-by: jian.cao <jian.cao@amlogic.com>
(cherry picked from commit 8e8cabbd2b8a20ce4e06d7898682b2665187012c)

PD#SWPL-57714

Problem:
can't close DEBUG_FS by config

Solution:
modify Kconfig about TRACING

Verify:
local

Change-Id: I6b926143fd94f952214e0f1fff2551fb891b1020
Signed-off-by: song.han <song.han@amlogic.com>

PD#SWPL-57735

Problem:
close DEBUG_FS then clkmsr crash.

Solution:
adjust register debugfs

Verify:
g12a_u212

Change-Id: I7988c6d4a9508dad26a6f886289ec3509c0af1df
Signed-off-by: Bichao Zheng <bichao.zheng@amlogic.com>

PD#SWPL-56548

Problem:
may block during spinlock cause crash

Solution:
move block outside of spinlock

Verify:
AB311

Change-Id: If0086cf3dd53b3426c8c2132e4718e36d06cb866
Signed-off-by: hang cheng <hang.cheng@amlogic.com>

PD#GH-1202
BUG=190485198

Problem:
Increase framebuffer memory pool so it can hold 6 framebuffers

Solution:
Increase framebuffer memory pool so it can hold 6 framebuffers

Verify:
adt3

Signed-off-by: Liang Ji <liang.ji@amlogic.com>
Change-Id: I2711107539efacdb810e8e10ca1f14f3e3d14533

PD#SWPL-54362

Problem:
The physical size is cm, while the screen size is mm.
Need unify the unit.

Solution:
Correct the unit of physical size as mm.

Verify:
g12/u212

Change-Id: I0c1f3d71f2df4930d8a91f692b713ad537133a55
Signed-off-by: Zongdong Jiao <zongdong.jiao@amlogic.com>

PD#SWPL-49147

Problem:
Bluetooth wakes up device unexpectedly

Solution:
kernel get BT-WAKE,do not send power key

Verify:
local

Signed-off-by: lele.liu <lele.liu@amlogic.com>
Change-Id: I8ccc0a719f8b54537b932c66f29a52c4a956d69b
Signed-off-by: lele.liu <lele.liu@amlogic.com>

Merge "picdec: skip putting vframe if current buffer is being in used [1/1]" into android-tv-deadpool-4.9-android12

Merge "STR: fix suspend abort cause system resume by powerkey event [1/1]" into android-tv-deadpool-4.9-android12

PD#SWPL-52256

Problem:
CONFIG_AMLOGIC_HDMITX macro is not defined on
TV platform, cause complie issue

Solution:
fix complie issue

Verify:
am301

Change-Id: Ib9bcfe3d613f8affe2469adcce4383b315eee3fc
Signed-off-by: hang cheng <hang.cheng@amlogic.com>

PD#SWPL-52333

Problem:
hdmitx audio setting function is called on TV
platform and cause crash

Solution:
if hdmitx driver is not enabled, export function
just return

Verify:
pb

Signed-off-by: jintao xu <jintao.xu@amlogic.com>
Change-Id: Ic87135d8621a2a37e74c2ac8ddc6d7096e3d75d1