05 Apr, 2022
1 commit
14 Dec, 2021
1 commit
26 Mar, 2021
1 commit
-
Add terminated list for keeping descriptor so that it could be freed in
worker without any potential involving next descriptor raised up before
this descriptor freed, because vchan_get_all_descriptors get all
descriptors including the last terminated descriptor and the next
descriptor, hence, the next descriptor maybe freed unexpectly when it's
done in worker without this patch.
https://www.spinics.net/lists/dmaengine/msg23367.htmlChange-Id: Iece434f55f3c6b5cf861fc23e4076fd4aa670ac4
Signed-off-by: Robin Gong
Reported-by: Richard Leitner
23 Mar, 2021
1 commit
-
Add support for frame format update using the atomic_update call.
Android, for example, changes the frame format after the atomic_enable
call, so without this, the colors are not right.Change-Id: I98a516b1ed3e50661d09c83dcc349e22080b7141
Signed-off-by: Robert Chiras
22 Mar, 2021
1 commit
-
The config for lcdif should be removed, and need to add vpu
qos setting by default. this patch is just to add back the
vpu qos config that is missed when resolving cherry-pick
conflict for patch:
3a3f54750294: MLK-19380 driver: soc: update the noc QoS setting on imx8mqChange-Id: I47767aeb3bd0a828ceddd3b3882fabd9a21b1b77
Signed-off-by: Jacky Bai
Reviewed-by: Anson Huang
18 Mar, 2021
13 commits
-
The IPIs will be handled in a new way which introduced by
commit "ANDROID: trusty-irq: specify IPIs in new way". This
commit will sync the dts change after switching to the new
approach.Signed-off-by: Ji Luo
Change-Id: I178682465f30b835269c8cb1ee34637df2a6bbd3 -
Some IRQs that are received by Linux need to be intercepted by the
Trusty driver and forwarded to Trusty. For this to work, the
device-tree node for the trusty-irq "device" needs to specify which
Linux IRQs correspond to which secure IRQs.Some of these IRQs are IPIs ("inter-processor interrupts"). But since
IPIs previously weren't normal Linux IRQs, the Trusty kernel branches
have been carrying a patch "ANDROID: arm64: smp: Add support for custom
ipi interrupt handlers" (http://aosp/1343165) to expose specific IPIs
via a "CustomIPI" irq_chip.This approach for specifying IPIs is being replaced with one based on
the patchset "arm/arm64: Turning IPIs into normal interrupts"
(https://lkml.kernel.org/lkml/20200901144324.1071694-1-maz@kernel.org),
which hopefully will make it into Linux 5.10.Make the changes needed to use the new approach.
Bug: 140053385
Change-Id: Ie68af0477db4e19a67a2db3522d17480aab7e3f5
Signed-off-by: Eric Biggers -
This commit breaks GKI compatibility and it's not needed any more.
Change-Id: Ibe12fd6b1345d70b81b8b97123558eded0f95dc2
-
Revert this commit because it will break GKI compatibility, the
trusty IPIs will be handled in a new way.Change-Id: I348d4a10e038f9b7eb8606ed1b1dde04b40ab01f
-
This reverts commit d7f4afdd682ab498258a6c832f482d736e0d4224.
Change-Id: I1c0d7ef7a1cd874eae79709710ab0b5fd53fb866
-
The SCU will handle the rproc fw load & kick so the A core
should not try to load the fw, we should returns 0 in
imx_rproc_elf_load_segments() for such case.And in rproc crash flow, the 'rproc->table_ptr' will be set
to 'rproc->cached_table' which is "NULL" in our case. And thus
panic would heppen when restarting virtio devices. We can't
use the 'rproc->cached_table' to record the address of the
resource table because a valid 'rproc->cached_table' would be
regarded as invalid state in "RPROC_DETACHED" state.This commit adds a pointer to record the resource table address
and will update the 'rproc->table_ptr' in each start.Callstack of the rproc panic is like below:
mek_8q:/ # [ 104.444095] remoteproc remoteproc0: crash detected in imx-rproc: type watchdog
[ 104.451529] Patition3 reset!
[ 104.454548] remoteproc remoteproc0: handling crash #1 in imx-rproc
[ 104.461011] remoteproc remoteproc0: recovering imx-rproc
[ 104.467197] i2c-rpmsg virtio0.rpmsg-i2c-channel.-1.1: i2c rpmsg driver is removed
[ 104.481395] remoteproc remoteproc0: stopped remote processor imx-rproc
[ 104.541342] remoteproc0#vdev0buffer: assigned reserved memory node vdevbuffer
[ 104.548693] Unable to handle kernel write to read-only memory at virtual address 0000000000000030
[ 104.558140] Mem abort info:
[ 104.561063] ESR = 0x96000044
[ 104.564154] EC = 0x25: DABT (current EL), IL = 32 bits
[ 104.569537] SET = 0, FnV = 0
[ 104.572695] EA = 0, S1PTW = 0
[ 104.576110] Data abort info:
[ 104.579053] ISV = 0, ISS = 0x00000044
[ 104.582901] CM = 0, WnR = 1
[ 104.585919] user pgtable: 4k pages, 48-bit VAs, pgdp=00000008ab09a000
[ 104.592470] [0000000000000030] pgd=0000000000000000, p4d=0000000000000000
[ 104.599522] Internal error: Oops: 96000044 [#1] PREEMPT SMP
[ 104.605119] Modules linked in: moal(O) mlan(O)
[ 104.609607] CPU: 0 PID: 89 Comm: kworker/0:2 Tainted: G O 5.10.9-00018-g4afaa96ef8e4-dirty #52
[ 104.619536] Hardware name: Freescale i.MX8QXP MEK (DT)
[ 104.624711] Workqueue: events rproc_crash_handler_work
[ 104.629869] pstate: 60400005 (nZCv daif +PAN -UAO -TCOBTYPE=--)
[ 104.635890] pc : rproc_virtio_reset+0x18/0x24
[ 104.640259] lr : register_virtio_device+0x84/0x104
[ 104.645056] sp : ffff80001297bc60
[ 104.648376] x29: ffff80001297bc60 x28: 0000000000000402
[ 104.653701] x27: ffff00083cf917a0 x26: 000000003cf95905
[ 104.659026] x25: 0000000000000000 x24: ffff000810a68c10
[ 104.664353] x23: ffff00082beffc00 x22: ffff000816098000
[ 104.669681] x21: 0000000000000000 x20: ffff00082beffc10
[ 104.675014] x19: ffff00082beffc00 x18: ffff800012951048
[ 104.680349] x17: 0000000000000041 x16: ffff8000106b5bec
[ 104.685682] x15: ffff80001196c077 x14: 0000000000000050
[ 104.691017] x13: ffff0000ffffff00 x12: ffff0a00ffffff0f
[ 104.696349] x11: 0000000000000030 x10: ffff80001297b980
[ 104.701678] x9 : 0000000000000000 x8 : 000000000000001c
[ 104.707011] x7 : 0000000000000003 x6 : ffff000822b0d586
[ 104.712345] x5 : 0000000000000040 x4 : ffff0a00ffffff0f
[ 104.717680] x3 : ffff0a00ffffff0f x2 : 0000000000000000
[ 104.723013] x1 : ffff80001027b914 x0 : ffff00082beffc00
[ 104.728349] Call trace:
[ 104.730818] rproc_virtio_reset+0x18/0x24
[ 104.734845] rproc_add_virtio_dev+0x17c/0x220
[ 104.739221] rproc_vdev_do_start+0x1c/0x2c
[ 104.743339] rproc_start+0xf0/0x210
[ 104.746842] rproc_trigger_recovery+0x158/0x1c4
[ 104.751394] rproc_crash_handler_work+0x94/0xa0
[ 104.755951] process_one_work+0x278/0x48c
[ 104.759978] worker_thread+0x280/0x4e0Signed-off-by: Ji Luo
Change-Id: I1f185b792c0a3c9cfa3db9108ba7179c799b73bf -
As the GKI requires not breaking the ABI compatibility,
this commit uses the 'autonomous' flag as Workaround to
skip the fw load.Signed-off-by: Ji Luo
Change-Id: Ifdd9c4e4bca9466f160aef76f4713bebfbd65b89 -
The elf will be loaded to TCM area on i.MX and the region
will be ioremapped. Setting the 'is_iomem' to avoid alignment
error in memory operations.Test: Boots on imx8mp.
Signed-off-by: Ji Luo
Change-Id: I52e4b3b8bc3761f0c17e8f0742c745333294027e -
Introduce an extra parameter is_iomem to da_to_va, then the caller
could take the memory as normal memory or io mapped memory.Reviewed-by: Bjorn Andersson
Reviewed-by: Mathieu Poirier
Reported-by: kernel test robot
Signed-off-by: Peng Fan
Change-Id: I1de7640f769e9a04eae6aef6abad292fde637531 -
Introduce is_iomem to indicate this piece memory is iomem or not.
Reviewed-by: Bjorn Andersson
Signed-off-by: Peng Fan
Reviewed-by: Mathieu Poirier
Change-Id: I5861e6068366101ed3d883fe049022975a869023 -
This reverts commit 8db3e678296398fc789fd9b7b648ca0966716ed4.
Change-Id: I0897f5277137133c43bd022dead73b168557d764
-
PTN5110 has an issue on start drp toggling begins with Rp
if the remote end always provides VBUS and presents Rp too,
possibly it can't generate CC change events after detection,
workaround it by starting drp toggling begins with Rd.Change-Id: I6e554d7c7b089cbd38531cea0929e0279a8bfa4d
Signed-off-by: Li Jun -
CL335550 [KERNEL SPACE] dev64x_234062: fix a cache refresh bug when import user logical(pfn map).
Change-Id: I98b54b94b87251f9e3a20bf446d8fbb1130b27eb
Signed-off-by: Richard Liu
15 Mar, 2021
1 commit
-
Thread genpd_power_off_work_fn will hold genpd->mlock in genpd_power_off_work_fn,
Then try to acquire prepare_lock in clk_unprepare.
Initcall clk_disable_unused will hold prepare_lock in clk_disable_unused firstly,
then try to acquire genpd->mlock in genpd_runtime_resume.
The deadlock happen in case that genpd_power_off_work hold genpd->mlock and
clk_disable_unused hold prepare_lock, And trying to hold each other.clk_disable_unused:
[ 11.667711][ T108] -> #1 (&genpd->mlock){+.+.}-{3:3}:
[ 11.675041][ T108] __lock_acquire+0xae4/0xef8
[ 11.680093][ T108] lock_acquire+0xfc/0x2f8
[ 11.684888][ T108] __mutex_lock+0x90/0x870
[ 11.689685][ T108] mutex_lock_nested+0x44/0x50
[ 11.694826][ T108] genpd_lock_mtx+0x18/0x24
[ 11.699706][ T108] genpd_runtime_resume+0x90/0x214 (hold genpd->mlock)
[ 11.705194][ T108] __rpm_callback+0x80/0x2c0
[ 11.710160][ T108] rpm_resume+0x468/0x650
[ 11.714866][ T108] __pm_runtime_resume+0x60/0x88
[ 11.720180][ T108] clk_pm_runtime_get+0x28/0x9c
[ 11.725410][ T108] clk_disable_unused_subtree+0x8c/0x144
[ 11.731420][ T108] clk_disable_unused_subtree+0x124/0x144
[ 11.737518][ T108] clk_disable_unused+0xa4/0x11c (hold prepare_lock)
[ 11.742833][ T108] do_one_initcall+0x98/0x178
[ 11.747888][ T108] do_initcall_level+0x9c/0xb8
[ 11.753028][ T108] do_initcalls+0x54/0x94
[ 11.757736][ T108] do_basic_setup+0x24/0x30
[ 11.762614][ T108] kernel_init_freeable+0x70/0xa4
[ 11.768014][ T108] kernel_init+0x14/0x18c
[ 11.772722][ T108] ret_from_fork+0x10/0x18genpd_power_off_work_fn:
[ 11.777512][ T108] -> #0 (prepare_lock){+.+.}-{3:3}:
[ 11.784749][ T108] check_noncircular+0x134/0x13c
[ 11.790064][ T108] validate_chain+0x590/0x2a04
[ 11.795204][ T108] __lock_acquire+0xae4/0xef8
[ 11.800258][ T108] lock_acquire+0xfc/0x2f8
[ 11.805050][ T108] __mutex_lock+0x90/0x870
[ 11.809841][ T108] mutex_lock_nested+0x44/0x50
[ 11.814983][ T108] clk_unprepare+0x5c/0x100 ((hold prepare_lock))
[ 11.819864][ T108] imx8m_pd_power_off+0xac/0x110
[ 11.825179][ T108] genpd_power_off+0x1b4/0x2dc
[ 11.830318][ T108] genpd_power_off_work_fn+0x38/0x58 (hold genpd->mlock)
[ 11.835981][ T108] process_one_work+0x270/0x444
[ 11.841208][ T108] worker_thread+0x280/0x4e4
[ 11.846176][ T108] kthread+0x13c/0x14c
[ 11.850621][ T108] ret_from_fork+0x10/0x18This patch is one workarround that break the lock in clk_disable_unused.
Block runtime PM of audio-blk, media-blk and hdmi-blk. so that it can not
be suspended at run time. We can change the runtime_PM status of
audio-blk, media-blk and hdmi-blk in user space.Change-Id: Iab70469936883696dafe4a90047949d2ca7fddf2
Signed-off-by: zhipeng.wang
12 Mar, 2021
1 commit
-
Change-Id: Ia7930d28149c46959fba613106fba545fae99d27
09 Mar, 2021
3 commits
-
- M865SW-692: VSI V4L2 Engineer release package 20210307
M865SW-543: [VPU/V4L2] decode: some MJPEG decoded frames have mosaic
M865SW-597: [VPU/V4L2] Easy to met hang issue when handle errors or exceptions
M865SW-650: [VPU/V4L2] Calculate h264 level before encoding since ctrl sw will check it
M865SW-675: [VPU/V4L2] Need to implement different ctrls based on encoder or decoder
M865SW-677: [VPU/V4L2] DTRC: need to report rfc luma/chroma offset of output buffer to app
M865SW-685: [VPU/V4L2] decoder: 8MQ: adding new format for DTRC & RFC
M865SW-419: [VPU/V4L2] Pass stress test for resolution change stream
M865SW-523: [VPU/V4L2] decoder: correctly handle stream file that contained codec data only
M865SW-571: [VPU/V4L2] decoder： input has 240 frames, output only get 239 pictures
M865SW-658: [VPU/V4L2] encoder: support resolution change stream transcoding.
M865SW-662: [VPU/V4l2] H264EncSetRateCtrl return error if GOP length is larger than 300Signed-off-by: Zhou Peng
Change-Id: Ifd78246208056de2d72a7a82d39bb62887828e1e -
Release all resources before returning error exit ioctl_dma_map by using goto out label
Signed-off-by: Florinel Iordache
-
Clear all string buffers memory locations in ioctl_compat before using strncpy to copy the string name
Signed-off-by: Florinel Iordache
08 Mar, 2021
1 commit
-
ISI has DMA overwrite issue on some format. To workaround it, allocate
max size of the format that ISI supported, which is w*h*4.For multi-planes, w*h*4 maybe a lilttle large. But on android, only YUV422I
or RGB888 are used, they are just 1 plan. And we don't know how far is the
overwrite, better to use max size for each plan.Note: The change is not suitable for memory type V4L2_MEMORY_MMAP. Need
carefully refine code, or may imapct realted registers.
On android, memory type is V4L2_MEMORY_DMABUF, the pending queue buffer size
can be controled in userspace.Change-Id: If3d7387f4ec03dc032046bb95fcfbacc532783ba
Signed-off-by: fang hui
06 Mar, 2021
1 commit
-
After reduce the panel RM67191's pixel clock from 132MHz to
121MHz by 'commit 4193a9c3254b ("MLK-3056-2 drm/panel: rm67191:
change clock rate to 121MHz for default mod")', the disp_apb
clock rate needs to be configured properly to avoid the issue
described in LF-33886 ticket with currrent disp_apb clock config
like below:sys1_pll_out 5 5 0 800000000 0 0 50000
sys1_pll_800m 5 5 0 800000000 0 0 50000
disp_apb 1 1 0 133333334 0 0 50000
disp_apb_root_clk 2 2 0 133333334 0 0 50000And configure disp_apb rate to 25MHz like below can solve this
issue:sys1_pll_out 5 5 0 800000000 0 0 50000
sys1_pll_800m 5 5 0 800000000 0 0 50000
disp_apb 1 1 0 25000000 0 0 50000
disp_apb_root_clk 2 2 0 25000000 0 0 50000Signed-off-by: Fancy Fang
Reviewed-by: Robby Cai
Acked-by: Jason Liu
05 Mar, 2021
2 commits
-
After reduce the panel RM67191's pixel clock from 132MHz to
121MHz by 'commit 4193a9c3254b ("MLK-3056-2 drm/panel: rm67191:
change clock rate to 121MHz for default mod")', the disp_apb
clock rate needs to be configured properly to avoid the issue
described in LF-33886 ticket with currrent disp_apb clock config
like below:sys1_pll_out 5 5 0 800000000 0 0 50000
sys1_pll_800m 5 5 0 800000000 0 0 50000
disp_apb 1 1 0 133333334 0 0 50000
disp_apb_root_clk 2 2 0 133333334 0 0 50000And configure disp_apb rate to 25MHz like below can solve this
issue:sys1_pll_out 5 5 0 800000000 0 0 50000
sys1_pll_800m 5 5 0 800000000 0 0 50000
disp_apb 1 1 0 25000000 0 0 50000
disp_apb_root_clk 2 2 0 25000000 0 0 50000Signed-off-by: Fancy Fang
Reviewed-by: Robby Cai -
Change-Id: I9dd6b8dd4ff1d25608a9264ecc1facb2df649818
04 Mar, 2021
5 commits
-
On 8DXL, the LCDIF IRQ number is different from 8QXP, so fix it in the
specific 8dxl dts file.Signed-off-by: Robert Chiras
Reviewed-by: Laurentiu Palcu
Acked-by: Jason Liu -
Without this patch, G_REC601_NTSC and NL_REC709 are used by opipe
with 480/576/240/288 height for default colorimetry. However, for those
kinds of opipe configurations, there is no valid entry to be found in
dcss_cfg_table[] if ipipe uses framebuffer in 32bit RGB pixel formats and
YUV pixel formats, which eventually leads to atomic check failure.
To make those cases work, this patch uses G_REC709 and NL_REC709 for
opipe as a workaround.Signed-off-by: Laurentiu Palcu
Reviewed-by: Liu Ying
Acked-by: Jason Liu -
Initialize to zero all ioctl_compat converted structures in fsl_usdpaa
Signed-off-by: Florinel Iordache
-
Initialize to zero ceetm sp_set_lni configuration structure in qman_high
Signed-off-by: Florinel Iordache
-
According to the latest DC ADD(DisplayControllerSubsystem_MX8_B0_v0.58),
the DPR burst length of GPU standard tile should be 256byte or 512byte
in case of underrun with 256byte.Based on tests done by Android team, 256byte works without DC underrun
issue(tracked by errata "ERR050183: DC: 4Kp60 performance limitations")
on both i.MX8qm and i.MX8qxp, while with the underrun issue by using
the original 128byte burst length.So, this patch uses 256byte burst length first for GPU standard tile
since there should be only improvement and no downgrade or regression
(subject to change to 512byte in case of underrun).Signed-off-by: Liu Ying
Tested-by: Richard Liu
03 Mar, 2021
1 commit
-
On the remove path, there is a need to teardown the IRQs and disconnect
from the PHY only if the DPMAC is not in TYPE_FIXED.
Update the remove path so that we do not end up accesing an invalid MC
portal.Signed-off-by: Ioana Ciornei
02 Mar, 2021
2 commits
-
android display hal has refined the logic to use block commit when
there is overlay but without android out fence. This android out
fence patch can be reverted now.Revert "MA-14133 Enable android out fence and normal out fence simultaneously"
This reverts commit d5d94e0e13b5bdf8b3ab4f60341e00898bbaf3c2.
Change-Id: I8ef48ba46350324965e055e5314c837472aead6d
Signed-off-by: Richard Liu -
…s wrong and text becomes unreadable if use user build images
don't re-init the console port when resume from suspend if have no sh.
Don't startup the console port when user space has no bash environment
than getty service cannot start up.This patch save the early console configure to tty->termios.c_cflag.
reset the uart according the saved info when startup.Change-Id: I62ece4f6fc866d59e557722144e49b07de6b4179
Signed-off-by: Fugang Duan <fugang.duan@nxp.com>
Tested-by: zhang sanshan <sanshan.zhang@nxp.com>
01 Mar, 2021
1 commit
-
- M865SW-681: VSI V4L2 Engineer release package 20210226
M865SW-595: [VPU/V4L2] report hdr10 metadata to userspace
M865SW-608: [VPU/V4L2] decoder: enumerate CAPTURE formats according to the currently established coded format
M865SW-655: [VPU/V4l2] Refine assert reference for Android build
M865SW-663: [VPU/V4L2] decoder： app can't receive codec error event
M865SW-668: [VPU/V4L2] daemon: update vsidaemon ts manager to fix Android GTS issue
M865SW-671: [VPU/V4L2] decoder： seek a resolution changed vp9 stream meet decoding error
M865SW-676: [VPU/V4L2] decoder: please add new formats into verfiyPlanesize()
M865SW-678: [VPU/V4L2] decoder: please add 10bit depth into vsiv4l2_decidepixeldepth()
M865SW-572: [VPU/V4L2] decoder/encoder： one frame stream can't receive EOS
M865SW-674: [VPU/V4L2] the dtrc and dtrx output is incorrect when decoding 10bit streamSigned-off-by: Zhou Peng
Change-Id: I61a196742dade4255c806b0549da77d9d261d32e
26 Feb, 2021
1 commit
-
Initialize to zero all ceetm configuration and query structures in qman_high
Signed-off-by: Florinel Iordache
25 Feb, 2021
1 commit
-
This patch adds "sai1","sai2" and "arm_m4_core" related to LPA clock skips registering the root slice
of gate ops, if M4 is enabled. The added clock is required for 8mm LPA.After testing and adding these clocks, the power consumption did not increase significantly.
Change-Id: Ib61df341631d1353fada91353af301487ffeec41
Signed-off-by: zhipeng.wang
23 Feb, 2021
2 commits
-
Move media, hdmi and audio blk ctrl data from clk-imx8mp
to clk-blk-ctrl driver to fix below kernel dump met when built as module:[ 1.909525][ T1] init: Loading module /lib/modules/clk-blk-ctrl.ko with args ""
[ 1.918640][ T1] Unable to handle kernel paging request at virtual address ffffffc0118a9b54
[ 1.927265][ T1] Mem abort info:
[ 1.930764][ T1] ESR = 0x96000007
[ 1.934528][ T1] EC = 0x25: DABT (current EL), IL = 32 bits
[ 1.940542][ T1] SET = 0, FnV = 0
[ 1.944299][ T1] EA = 0, S1PTW = 0
[ 1.948142][ T1] Data abort info:
[ 1.951719][ T1] ISV = 0, ISS = 0x00000007
[ 1.956256][ T1] CM = 0, WnR = 0
[ 1.959927][ T1] swapper pgtable: 4k pages, 39-bit VAs, pgdp=0000000041de3000
[ 1.967329][ T1] [ffffffc0118a9b54] pgd=00000001bffff003, p4d=00000001bffff003, pud=00000001bffff003, pmd=00000001bfffc003, pte=0000000000000000
[ 1.980570][ T1] Internal error: Oops: 96000007 [#1] PREEMPT SMP
[ 1.986840][ T1] Modules linked in: clk_blk_ctrl(+) imx2_wdt imx gpio_mxc pinctrl_imx8mp pinctrl_imx irq_imx_irqsteer busfreq_imx8mq timer_imx_sysctr
[ 2.000527][ T1] CPU: 3 PID: 1 Comm: init Not tainted 5.10.9-00012-g9da899adc4fd #10
[ 2.008530][ T1] Hardware name: NXP i.MX8MPlus EVK board (DT)
[ 2.014542][ T1] pstate: 20400005 (nzCv daif +PAN -UAO -TCO BTYPE=--)
[ 2.021254][ T1] pc : imx_blk_ctrl_probe+0x68/0x414 [clk_blk_ctrl]
[ 2.027702][ T1] lr : imx_blk_ctrl_probe+0x68/0x414 [clk_blk_ctrl]
[ 2.034142][ T1] sp : ffffffc011b6b860
[ 2.038153][ T1] x29: ffffffc011b6b890 x28: ffffffc011b6bda0
[ 2.044164][ T1] x27: 0000000000000100 x26: ffffffc008f05190
[ 2.050175][ T1] x25: ffffff80c3a5e430 x24: 0000000000000010
[ 2.056187][ T1] x23: ffffffc011b15000 x22: ffffffc0119fc510
[ 2.062198][ T1] x21: ffffff80c3b23e80 x20: ffffff80c0915400
[ 2.068211][ T1] x19: ffffff80c0915410 x18: ffffffc011b550a0
[ 2.074225][ T1] x17: 0000000000000031 x16: ffffffc012361000
[ 2.080238][ T1] x15: ffffffc012350000 x14: 0000000000000086
[ 2.086249][ T1] x13: 0000000000000042 x12: 0000000000000000
[ 2.092260][ T1] x11: fffffffefe6880a1 x10: fffffffefe6880a0
[ 2.098271][ T1] x9 : 0000000100000000 x8 : 0000000100000000
[ 2.104282][ T1] x7 : 01fefefefefefeff x6 : 8080808080808000
[ 2.110293][ T1] x5 : 0080808080808080 x4 : 6e6f63737973ffff
[ 2.116305][ T1] x3 : 6701000008000000 x2 : 0300000000000000
[ 2.122319][ T1] x1 : 0000000000000000 x0 : ffffffc0118a9b40
[ 2.128332][ T1] Call trace:
[ 2.131480][ T1] imx_blk_ctrl_probe+0x68/0x414 [clk_blk_ctrl]
[ 2.137579][ T1] platform_drv_probe+0x94/0xbc
[ 2.142285][ T1] really_probe+0x1d4/0x4b4
[ 2.146646][ T1] driver_probe_device+0x64/0xb8
[ 2.151439][ T1] device_driver_attach+0x6c/0xacSigned-off-by: Jindong Yue
Change-Id: Ib7e00602734cfe3465641f7d37ebd4e59b7ea563 -
Allow i.mx8m power domain driver to be loaded as module.
Do not select IMX8M_PM_DOMAINS by default after enable ARCH_MXC.Signed-off-by: Jindong Yue
Change-Id: I19c9978762136d1a6314ffcb3545536ae2598faa
