nvidia-tegra-modules.git/drivers/platform/tegra/rtcpu/ivc-bus.c, branch rtss22-ae NVIDIA's kernel modules to support tegra chips (used in Jetson boards) tegra: rtcpu: fix IVC synchronization 2018-09-14T22:34:22+00:00 Pekka Pessi ppessi@nvidia.com 2018-09-11T13:30:44+00:00 c662725996835f843f5a42e42d2c5e1fe0e90f85 Always synchronize the IVC channels. The IVC channels were left unsynchronized after reboot on VDK. Use the camrtc device as IVC peer device. The IVC memory is allocated via camrtc device, the cache management needs to use same device. Bug 2031890 Bug 2375767 Change-Id: I1cd3831416af4e6ca1d0d048d86f96d31f60c418 Signed-off-by: Pekka Pessi <ppessi@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/1819894 Reviewed-by: Automatic_Commit_Validation_User GVS: Gerrit_Virtual_Submit Reviewed-by: Bhanu Murthy V <bmurthyv@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Always synchronize the IVC channels. The IVC channels were left
unsynchronized after reboot on VDK.

Use the camrtc device as IVC peer device. The IVC memory is allocated
via camrtc device, the cache management needs to use same device.

Bug 2031890
Bug 2375767

Change-Id: I1cd3831416af4e6ca1d0d048d86f96d31f60c418
Signed-off-by: Pekka Pessi <ppessi@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1819894
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Bhanu Murthy V <bmurthyv@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
tegra: rtcpu: ivc-bus: do not stop if setup fails 2018-09-13T00:47:37+00:00 Pekka Pessi ppessi@nvidia.com 2018-08-20T21:59:21+00:00 878766f45381183822b9ef0f40be959cd7c8724f The bus stopping does not hop through all the hoops and ivc-bus remains unremoved. Bug 2305627 Change-Id: I2309b212708447ce572d0f2f58671e200f184833 Signed-off-by: Pekka Pessi <ppessi@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/1803898 Reviewed-by: Semi Malinen <smalinen@nvidia.com> Reviewed-by: Bhanu Murthy V <bmurthyv@nvidia.com> GVS: Gerrit_Virtual_Submit Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
The bus stopping does not hop through all the hoops and ivc-bus
remains unremoved.

Bug 2305627

Change-Id: I2309b212708447ce572d0f2f58671e200f184833
Signed-off-by: Pekka Pessi <ppessi@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1803898
Reviewed-by: Semi Malinen <smalinen@nvidia.com>
Reviewed-by: Bhanu Murthy V <bmurthyv@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
tegra: camera: rtcpu: tone down logging 2018-09-13T00:47:33+00:00 Pekka Pessi ppessi@nvidia.com 2018-08-20T21:52:23+00:00 a277218541aa81b31f1eceb0f6e79cac8cf10603 Reduce kernel log spam. Bug 2305627 Change-Id: I9e7c34f631e5e4c5a7aba348664aa8c8cbe6e881 Signed-off-by: Pekka Pessi <ppessi@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/1803896 Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Reduce kernel log spam.

Bug 2305627

Change-Id: I9e7c34f631e5e4c5a7aba348664aa8c8cbe6e881
Signed-off-by: Pekka Pessi <ppessi@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1803896
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Bullseye: RTCPU driver mod for code coverage. 2018-02-01T00:41:50+00:00 Matthew Lazarowitz mlazarowitz@nvidia.com 2017-09-27T21:13:22+00:00 8ceca013844c0d0b361ba66ef9287d18df28ab04 Bug 2001937 This change creates a communication channel between the RTCPU and the kernel driver so that an RTCPU image built to obtain Bullseye coverage data can return that data to the CCPLEX and the kernel can make it available in a file in the debug file system. If during the boot sync the kernel driver does not detect an RTCPU firmware built with Bullseye support all allocated resources will be freed and the driver will behave as though this change does not exist. Change-Id: I9b9bca11229489c3ae802bb20bbddac203a3f6dd Signed-off-by: Matthew Lazarowitz <mlazarowitz@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/1569666 GVS: Gerrit_Virtual_Submit Reviewed-by: Bhanu Murthy V <bmurthyv@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Bug 2001937

This change creates a communication channel between the
RTCPU and the kernel driver so that an RTCPU image
built to obtain Bullseye coverage data can return
that data to the CCPLEX and the kernel can make it
available in a file in the debug file system.
If during the boot sync the kernel driver does not
detect an RTCPU firmware built with Bullseye support
all allocated resources will be freed and the driver
will behave as though this change does not exist.

Change-Id: I9b9bca11229489c3ae802bb20bbddac203a3f6dd
Signed-off-by: Matthew Lazarowitz <mlazarowitz@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1569666
GVS: Gerrit_Virtual_Submit
Reviewed-by: Bhanu Murthy V <bmurthyv@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
tegra: camera: rtcpu: track ivc-bus state changes 2017-12-25T17:42:08+00:00 Pekka Pessi ppessi@nvidia.com 2017-11-27T19:39:39+00:00 ac6b586b1323ce7933a258366a8677c0d3459f7b The kernel tasks handling the ivc-channel notification may miss the online->offline->online change during the RTCPU reboot. Add a simple interface for tracking the IVC bus resets. Jira CAMC-513 Change-Id: Idb174b777af710295542d420251e6b0f2181e0d4 Signed-off-by: Pekka Pessi <ppessi@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/1620009 Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com> GVS: Gerrit_Virtual_Submit Reviewed-by: Amit Purwar <apurwar@nvidia.com> Tested-by: Amit Purwar <apurwar@nvidia.com> Tested-by: Shantanu Nath <snath@nvidia.com> Reviewed-by: Shantanu Nath <snath@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
The kernel tasks handling the ivc-channel notification may miss the
online->offline->online change during the RTCPU reboot. Add a simple
interface for tracking the IVC bus resets.

Jira CAMC-513

Change-Id: Idb174b777af710295542d420251e6b0f2181e0d4
Signed-off-by: Pekka Pessi <ppessi@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1620009
Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Amit Purwar <apurwar@nvidia.com>
Tested-by: Amit Purwar <apurwar@nvidia.com>
Tested-by: Shantanu Nath <snath@nvidia.com>
Reviewed-by: Shantanu Nath <snath@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
tegra: camera: rtcpu: support ivc synchronization 2017-11-28T17:10:07+00:00 Pekka Pessi ppessi@nvidia.com 2017-11-23T14:03:48+00:00 f77bec15a62b9d557d0181af3d2c303e96e8fde7 Bump fw version and indicate support for IVC synchronization protocol. Jira CAMC-513 Change-Id: If4325a013b1f1817d0e967610bd6bdf74974f28b Signed-off-by: Pekka Pessi <ppessi@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/1604053 Reviewed-by: Automatic_Commit_Validation_User Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com> GVS: Gerrit_Virtual_Submit Reviewed-by: Mika Liljeberg <mliljeberg@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Bump fw version and indicate support for IVC synchronization protocol.

Jira CAMC-513

Change-Id: If4325a013b1f1817d0e967610bd6bdf74974f28b
Signed-off-by: Pekka Pessi <ppessi@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1604053
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Mika Liljeberg <mliljeberg@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
platform: tegra: rtcpu: refactor pm and probing 2017-05-04T08:54:44+00:00 Pekka Pessi ppessi@nvidia.com 2017-02-17T13:10:00+00:00 f7b35e10839f36b52d3c1ea35c8d3fbfcc617b28 Firmware provides now the PM features for suspend and resume. Firmware activates the WDT after boot synchronization and deactivates it when suspended. The boot synchronization and the IVC service synchronization can be redone at any time. The driver requires firmware version SM4 because the earlier firmwares can not resume gracefully from the suspended state. Reorder initialization in order to avoid accessing hardware before it is fully powered. Note that powering HW with the APE power domain during the probe() may happen when pm_runtime_get_sync() is called and both resume and runtime_resume may get invoked in the process. Add checks to avoid any premature resumes. Assert resets in the reverse order they are deasserted. Enable clocks before touching any resources, including getting interrupt resources. Fix the unbalanced early_resume/late_suspend. The power domain does not track the last busy from the children of the rtcpu device. Mark the rtcpu device last busy always when the ivc channel devices are used, too. The IVC channels are now created only after the initial boot sync and version exchange with the firmware. When the IVC sync is done the RTCPU and device are both up and ready. Do not expose boot and halt methods. Instead provide the reboot method, which will only proceed when the rtcpu device is in the active runtime state. Follow suspend procedure from APE TRM. Wait for APE WFI using an interrupt. Wait for APE L2 cache to idle. Allocate an interrupt for APE WFI. Move all register handling to core-specific functions (tegra_ape_cam*(), tegra_sce_cam*()). Do not use the ahub clock. Power off RTCPU and remove the tracer during remove. Tracer can be disabled or enabled in the device tree. Treat it as an optional feature. Jira CRTC-910 Bug 1857548 Jira CRTC-966 Bug 1864505 Bug 200269632 Bug 200292354 Change-Id: I75df878932a4307181a243261f99f0a853d395b1 Signed-off-by: Pekka Pessi <ppessi@nvidia.com> Reviewed-on: http://git-master/r/1298769 Reviewed-by: David Wang (SW-TEGRA) <davidw@nvidia.com> GVS: Gerrit_Virtual_Submit Reviewed-by: Mika Liljeberg <mliljeberg@nvidia.com> 
Firmware provides now the PM features for suspend and resume. Firmware
activates the WDT after boot synchronization and deactivates it when
suspended.  The boot synchronization and the IVC service
synchronization can be redone at any time.

The driver requires firmware version SM4 because the earlier firmwares
can not resume gracefully from the suspended state.

Reorder initialization in order to avoid accessing hardware before it
is fully powered. Note that powering HW with the APE power domain
during the probe() may happen when pm_runtime_get_sync() is called and
both resume and runtime_resume may get invoked in the process. Add
checks to avoid any premature resumes.

Assert resets in the reverse order they are deasserted. Enable clocks
before touching any resources, including getting interrupt resources.

Fix the unbalanced early_resume/late_suspend.

The power domain does not track the last busy from the children of the
rtcpu device.  Mark the rtcpu device last busy always when the ivc
channel devices are used, too.

The IVC channels are now created only after the initial boot sync and
version exchange with the firmware. When the IVC sync is done the
RTCPU and device are both up and ready.

Do not expose boot and halt methods. Instead provide the reboot
method, which will only proceed when the rtcpu device is in the active
runtime state.

Follow suspend procedure from APE TRM. Wait for APE WFI using an
interrupt. Wait for APE L2 cache to idle. Allocate an interrupt for
APE WFI.

Move all register handling to core-specific functions (tegra_ape_cam*(),
tegra_sce_cam*()).

Do not use the ahub clock.

Power off RTCPU and remove the tracer during remove. Tracer can be
disabled or enabled in the device tree. Treat it as an optional feature.

Jira CRTC-910
Bug 1857548
Jira CRTC-966
Bug 1864505
Bug 200269632
Bug 200292354

Change-Id: I75df878932a4307181a243261f99f0a853d395b1
Signed-off-by: Pekka Pessi <ppessi@nvidia.com>
Reviewed-on: http://git-master/r/1298769
Reviewed-by: David Wang (SW-TEGRA) <davidw@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Mika Liljeberg <mliljeberg@nvidia.com>
platform: tegra: rtcpu: send up/down to all channels 2017-05-04T08:54:44+00:00 Pekka Pessi ppessi@nvidia.com 2017-02-02T01:33:26+00:00 d3ab9755583a4354f49a29d8c95a777b602a3e0d Send the RTCPU up/down events to all IVC channels, not just VI notifier clients. Jira CRTC-911 Jira CRTC-726 Bug 1819170 Change-Id: Ia2a2fc941b157cd54a34e78da4e12cd3c7038d5a Signed-off-by: Pekka Pessi <ppessi@nvidia.com> Reviewed-on: http://git-master/r/1298058 GVS: Gerrit_Virtual_Submit Reviewed-by: Mika Liljeberg <mliljeberg@nvidia.com> 
Send the RTCPU up/down events to all IVC channels, not just VI notifier
clients.

Jira CRTC-911
Jira CRTC-726
Bug 1819170

Change-Id: Ia2a2fc941b157cd54a34e78da4e12cd3c7038d5a
Signed-off-by: Pekka Pessi <ppessi@nvidia.com>
Reviewed-on: http://git-master/r/1298058
GVS: Gerrit_Virtual_Submit
Reviewed-by: Mika Liljeberg <mliljeberg@nvidia.com>
tegra: ivc: camrtc: add supoort to disable ivc channel 2017-04-13T17:04:08+00:00 Ashish Singh assingh@nvidia.com 2017-04-12T23:02:00+00:00 c671aed7331b509443d62b098e9993d3f4bb3ffb IVC channel devices can now be disabled using status value. CRTC-1073 Change-Id: I5411cc2ec327f1e4295fba43ef750fa6e9b78822 Signed-off-by: Ashish Singh <assingh@nvidia.com> Reviewed-on: http://git-master/r/1461744 Reviewed-by: svccoveritychecker <svccoveritychecker@nvidia.com> Reviewed-by: Jihoon Bang <jbang@nvidia.com> GVS: Gerrit_Virtual_Submit Reviewed-by: Mika Liljeberg <mliljeberg@nvidia.com> 
IVC channel devices can now be disabled using status value.

CRTC-1073

Change-Id: I5411cc2ec327f1e4295fba43ef750fa6e9b78822
Signed-off-by: Ashish Singh <assingh@nvidia.com>
Reviewed-on: http://git-master/r/1461744
Reviewed-by: svccoveritychecker <svccoveritychecker@nvidia.com>
Reviewed-by: Jihoon Bang <jbang@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Mika Liljeberg <mliljeberg@nvidia.com>
platform: tegra: rtcpu: ivc subsys init 2017-04-07T02:24:20+00:00 Ashish Singh assingh@nvidia.com 2017-03-22T17:37:46+00:00 b316d927fcb8eecac3287d1d633c3561cb162a94 Making all ivc channel driver as subsys level init, so that drivers are registered when ivc bus is created and ivc channel devices are added. Which will make sure that ready call is made to all ivc channel drivers for them to know when RTCPU is online or offline. Also adding ready func ops to all ivc channel drivers and test if it was called by is_ready flag. CRTC-925 Change-Id: I0d91624fe3dc23cb894d59cba0a7bdcb4626d2ac Signed-off-by: Ashish Singh <assingh@nvidia.com> Reviewed-on: http://git-master/r/1326220 Reviewed-by: Automatic_Commit_Validation_User Reviewed-by: svccoveritychecker <svccoveritychecker@nvidia.com> GVS: Gerrit_Virtual_Submit Reviewed-by: Jihoon Bang <jbang@nvidia.com> 
Making all ivc channel driver as subsys level init, so that
drivers are registered when ivc bus is created and ivc channel
devices are added. Which will make sure that ready call is made
to all ivc channel drivers for them to know when RTCPU is online
or offline.

Also adding ready func ops to all ivc channel drivers and test if
it was called by is_ready flag.

CRTC-925

Change-Id: I0d91624fe3dc23cb894d59cba0a7bdcb4626d2ac
Signed-off-by: Ashish Singh <assingh@nvidia.com>
Reviewed-on: http://git-master/r/1326220
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: svccoveritychecker <svccoveritychecker@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Jihoon Bang <jbang@nvidia.com>