{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":397958242,"defaultBranch":"linux-dev","name":"switch-l4t-kernel-4.9","ownerLogin":"CTCaer","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2021-08-19T13:46:25.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/3665130?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1692982450.0","currentOid":""},"activityList":{"items":[{"before":"df2b3c7f92cf30881e2e6ce52c99221de486e7df","after":"2d0059fd3167a8df756de2aa0489d4aa70a9fc15","ref":"refs/heads/linux-dev","pushedAt":"2023-08-25T13:02:30.000Z","pushType":"push","commitsCount":7,"pusher":{"login":"CTCaer","name":null,"path":"/CTCaer","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3665130?s=80&v=4"},"commit":{"message":"arm: tegra: enable usb serial CP210x as a module","shortMessageHtmlLink":"arm: tegra: enable usb serial CP210x as a module"}},{"before":"1cf063873b6f821cc7ac4d5a39fb46d90ecaab1c","after":"df2b3c7f92cf30881e2e6ce52c99221de486e7df","ref":"refs/heads/linux-dev","pushedAt":"2023-08-07T01:45:00.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"CTCaer","name":null,"path":"/CTCaer","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3665130?s=80&v=4"},"commit":{"message":"Bluetooth: Fix update of connection state in `hci_encrypt_cfm`\n\nStarting with the upgrade to v5.8-rc3, I've noticed I wasn't able to\nconnect to my Bluetooth headset properly anymore. While connecting to\nthe device would eventually succeed, bluetoothd seemed to be confused\nabout the current connection state where the state was flapping hence\nand forth. Bisecting this issue led to commit 3ca44c16b0dc (Bluetooth:\nConsolidate encryption handling in hci_encrypt_cfm, 2020-05-19), which\nrefactored `hci_encrypt_cfm` to also handle updating the connection\nstate.\n\nThe commit in question changed the code to call `hci_connect_cfm` inside\n`hci_encrypt_cfm` and to change the connection state. But with the\nconversion, we now only update the connection state if a status was set\nalready. In fact, the reverse should be true: the status should be\nupdated if no status is yet set. So let's fix the isuse by reversing the\ncondition.\n\nFixes: 3ca44c16b0dc (\"Bluetooth: Consolidate encryption handling in hci_encrypt_cfm\")\nSigned-off-by: Patrick Steinhardt \nAcked-by: Luiz Augusto von Dentz \nSigned-off-by: Marcel Holtmann ","shortMessageHtmlLink":"Bluetooth: Fix update of connection state in hci_encrypt_cfm"}},{"before":"96567b671bb84ad88a6929de83d6f344e7d4629e","after":"1cf063873b6f821cc7ac4d5a39fb46d90ecaab1c","ref":"refs/heads/linux-dev","pushedAt":"2023-07-29T16:15:26.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"CTCaer","name":null,"path":"/CTCaer","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3665130?s=80&v=4"},"commit":{"message":"soc: tegra: fix race condition on dvfs rails init\n\nFix a race condition caused by clock/dvfs mutex locking timeouts on\ninterconnected logic.\n\nIn DVFS power rail init in probe, all dvfs clocks are assigned the dvfs event\ncallback.\nDuring that time, if a clock change request happens the following can happen:\n- DVFS rail init unlocks its mutex\n- DVFS registers the clock pre/post call back\n- DVFS locks its mutex\n- Clock change request happens for a relevant device\n- Clock framework api locks its mutex and calls the event callback\n- DVFS event handler is called, tries to lock its mutex but it's already locked\n- DVFS rail init tries to register the next dvfs clock to a rail\n- DVFS tries to get a clock rate on an enabled or prepared clock\n- Clock framework tries to lock its mutex in order to fulfill the request but\nit's already locked since the clock change event is in process and waiting for\nthe dvfs mutex.\n\nSince both DVFS and Clock frameworks are now waiting for a mutex lock, both end\nup in a hang state.\n\nFix that by unlocking dvfs mutex during the dvfs clock to rails register loop.\nThe locking at that point is irrelevant since that code does not call other\ndvfs code that needs locking.\nThis allows clock framework to properly change relevant clocks during subsequent\nregulator rail init.\n\nThat marks the final fix on extremely-rare boot-time hangs.\n\nKernel log with CPU and EMC clock/dvfs requests:\n```\n[ 246.846820] INFO: task kworker/0:1:45 blocked for more than 120 seconds.\n[ 246.853513] Not tainted 4.9.140-l4t #252\n[ 246.857951] \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n[ 246.865772] kworker/0:1 D 0 45 2 0x00000000\n[ 246.871272] Workqueue: events deferred_probe_work_func\n[ 246.876411] Call trace:\n[ 246.878858] [] __switch_to+0x94/0xc0\n[ 246.883993] [] __schedule+0x228/0x5c0\n[ 246.889214] [] schedule+0x38/0xa0\n[ 246.894089] [] schedule_preempt_disabled+0x20/0x40\n[ 246.900437] [] __mutex_lock_slowpath+0xc0/0x190\n[ 246.906523] [] mutex_lock+0x40/0x60\n[ 246.911573] [] clk_prepare_lock+0x40/0xd0\n[ 246.917139] [] clk_core_get_rate+0x14/0x80\n[ 246.922794] [] clk_get_rate+0x14/0x30\n[ 246.928018] [] tegra_dvfs_probe+0x2b8/0x630\n[ 246.933760] [] platform_drv_probe+0x58/0xc0\n[ 246.939502] [] driver_probe_device+0x148/0x2a0\n[ 246.945504] [] __device_attach_driver+0x98/0xf0\n[ 246.951592] [] bus_for_each_drv+0x48/0xa0\n[ 246.957160] [] __device_attach+0xc0/0x130\n[ 246.962728] [] device_initial_probe+0x10/0x20\n[ 246.968643] [] bus_probe_device+0x90/0xa0\n[ 246.974210] [] deferred_probe_work_func+0x7c/0xc0\n[ 246.980470] [] process_one_work+0x1d8/0x370\n[ 246.986209] [] worker_thread+0x248/0x4e0\n[ 246.991691] [] kthread+0xe8/0xf0\n[ 246.996479] [] ret_from_fork+0x10/0x50\n[ 247.001791] INFO: task irq/13-6000c800:197 blocked for more than 120 seconds.\n[ 247.008917] Not tainted 4.9.140-l4t #252\n[ 247.013360] \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n[ 247.021181] irq/13-6000c800 D 0 197 2 0x00000000\n[ 247.026675] Call trace:\n[ 247.029122] [] __switch_to+0x94/0xc0\n[ 247.034257] [] __schedule+0x228/0x5c0\n[ 247.039479] [] schedule+0x38/0xa0\n[ 247.044354] [] schedule_preempt_disabled+0x20/0x40\n[ 247.050701] [] __mutex_lock_slowpath+0xc0/0x190\n[ 247.056789] [] mutex_lock+0x40/0x60\n[ 247.061835] [] clk_prepare_lock+0x40/0xd0\n[ 247.067402] [] clk_set_rate+0x24/0x90\n[ 247.072625] [] bwmgr_update_clk+0x168/0x200\n[ 247.078366] [] tegra_bwmgr_set_emc+0x1a0/0x2d0\n[ 247.084367] [] actmon_dev_set_rate+0x24/0x30\n[ 247.090195] [] actmon_dev_fn+0xac/0xd0\n[ 247.095504] [] irq_thread_fn+0x28/0x90\n[ 247.100813] [] irq_thread+0x114/0x1a0\n[ 247.106034] [] kthread+0xe8/0xf0\n[ 247.110821] [] ret_from_fork+0x10/0x50\n[ 247.116130] INFO: task sugov:0:210 blocked for more than 120 seconds.\n[ 247.122562] Not tainted 4.9.140-l4t #252\n[ 247.127001] \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n[ 247.134819] sugov:0 D 0 210 2 0x00000000\n[ 247.140313] Call trace:\n[ 247.142761] [] __switch_to+0x94/0xc0\n[ 247.147896] [] __schedule+0x228/0x5c0\n[ 247.153121] [] schedule+0x38/0xa0\n[ 247.157995] [] schedule_preempt_disabled+0x20/0x40\n[ 247.164342] [] __mutex_lock_slowpath+0xc0/0x190\n[ 247.170429] [] mutex_lock+0x40/0x60\n[ 247.175477] [] tegra_dvfs_clk_event+0x10c/0x240\n[ 247.181566] [] notifier_call_chain+0x54/0x90\n[ 247.187393] [] __srcu_notifier_call_chain+0x84/0xb0\n[ 247.193826] [] srcu_notifier_call_chain+0x14/0x20\n[ 247.200086] [] __clk_notify+0x70/0x90\n[ 247.205308] [] clk_propagate_rate_change+0xa0/0xf0\n[ 247.211655] [] clk_propagate_rate_change+0x8c/0xf0\n[ 247.218002] [] clk_core_set_rate_nolock+0x40/0x90\n[ 247.224263] [] clk_set_rate+0x58/0x90\n[ 247.229484] [] set_cpu_freq+0xc8/0x170\n[ 247.234793] [] __cpufreq_driver_target+0x160/0x530\n[ 247.241142] [] sugov_work+0x30/0x50\n[ 247.246190] [] kthread_worker_fn+0x90/0x160\n[ 247.251931] [] kthread+0xe8/0xf0\n[ 247.256718] [] ret_from_fork+0x10/0x50\n\n[ 369.726738] INFO: task kworker/0:1:45 blocked for more than 120 seconds.\n[ 369.733430] Not tainted 4.9.140-l4t #252\n[ 369.737867] \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n[ 369.745686] kworker/0:1 D 0 45 2 0x00000000\n[ 369.751184] Workqueue: events deferred_probe_work_func\n[ 369.756322] Call trace:\n[ 369.758769] [] __switch_to+0x94/0xc0\n[ 369.763904] [] __schedule+0x228/0x5c0\n[ 369.769126] [] schedule+0x38/0xa0\n[ 369.774002] [] schedule_preempt_disabled+0x20/0x40\n[ 369.780348] [] __mutex_lock_slowpath+0xc0/0x190\n[ 369.786436] [] mutex_lock+0x40/0x60\n[ 369.791483] [] clk_prepare_lock+0x40/0xd0\n[ 369.797049] [] clk_core_get_rate+0x14/0x80\n[ 369.802703] [] clk_get_rate+0x14/0x30\n[ 369.807925] [] tegra_dvfs_probe+0x2b8/0x630\n[ 369.813667] [] platform_drv_probe+0x58/0xc0\n[ 369.819408] [] driver_probe_device+0x148/0x2a0\n[ 369.825410] [] __device_attach_driver+0x98/0xf0\n[ 369.831497] [] bus_for_each_drv+0x48/0xa0\n[ 369.837065] [] __device_attach+0xc0/0x130\n[ 369.842632] [] device_initial_probe+0x10/0x20\n[ 369.848548] [] bus_probe_device+0x90/0xa0\n[ 369.854122] [] deferred_probe_work_func+0x7c/0xc0\n[ 369.860383] [] process_one_work+0x1d8/0x370\n[ 369.866124] [] worker_thread+0x248/0x4e0\n[ 369.871605] [] kthread+0xe8/0xf0\n[ 369.876392] [] ret_from_fork+0x10/0x50\n[ 369.881704] INFO: task irq/13-6000c800:197 blocked for more than 120 seconds.\n[ 369.888830] Not tainted 4.9.140-l4t #252\n[ 369.893271] \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n[ 369.901090] irq/13-6000c800 D 0 197 2 0x00000000\n[ 369.906584] Call trace:\n[ 369.909030] [] __switch_to+0x94/0xc0\n[ 369.914166] [] __schedule+0x228/0x5c0\n[ 369.919388] [] schedule+0x38/0xa0\n[ 369.924261] [] schedule_preempt_disabled+0x20/0x40\n[ 369.930608] [] __mutex_lock_slowpath+0xc0/0x190\n[ 369.936695] [] mutex_lock+0x40/0x60\n[ 369.941742] [] clk_prepare_lock+0x40/0xd0\n[ 369.947309] [] clk_set_rate+0x24/0x90\n[ 369.952531] [] bwmgr_update_clk+0x168/0x200\n[ 369.958273] [] tegra_bwmgr_set_emc+0x1a0/0x2d0\n[ 369.964275] [] actmon_dev_set_rate+0x24/0x30\n[ 369.970103] [] actmon_dev_fn+0xac/0xd0\n[ 369.975410] [] irq_thread_fn+0x28/0x90\n[ 369.980718] [] irq_thread+0x114/0x1a0\n[ 369.985940] [] kthread+0xe8/0xf0\n[ 369.990726] [] ret_from_fork+0x10/0x50\n[ 369.996034] INFO: task sugov:0:210 blocked for more than 120 seconds.\n[ 370.002467] Not tainted 4.9.140-l4t #252\n[ 370.006906] \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n[ 370.014726] sugov:0 D 0 210 2 0x00000000\n[ 370.020220] Call trace:\n[ 370.022666] [] __switch_to+0x94/0xc0\n[ 370.027800] [] __schedule+0x228/0x5c0\n[ 370.033022] [] schedule+0x38/0xa0\n[ 370.037896] [] schedule_preempt_disabled+0x20/0x40\n[ 370.044244] [] __mutex_lock_slowpath+0xc0/0x190\n[ 370.050332] [] mutex_lock+0x40/0x60\n[ 370.055380] [] tegra_dvfs_clk_event+0x10c/0x240\n[ 370.061468] [] notifier_call_chain+0x54/0x90\n[ 370.067296] [] __srcu_notifier_call_chain+0x84/0xb0\n[ 370.073729] [] srcu_notifier_call_chain+0x14/0x20\n[ 370.079989] [] __clk_notify+0x70/0x90\n[ 370.085210] [] clk_propagate_rate_change+0xa0/0xf0\n[ 370.091558] [] clk_propagate_rate_change+0x8c/0xf0\n[ 370.097905] [] clk_core_set_rate_nolock+0x40/0x90\n[ 370.104165] [] clk_set_rate+0x58/0x90\n[ 370.109386] [] set_cpu_freq+0xc8/0x170\n[ 370.114696] [] __cpufreq_driver_target+0x160/0x530\n[ 370.121043] [] sugov_work+0x30/0x50\n[ 370.126092] [] kthread_worker_fn+0x90/0x160\n[ 370.131833] [] kthread+0xe8/0xf0\n[ 370.136620] [] ret_from_fork+0x10/0x50\n```\n\nSigned-off-by: CTCaer ","shortMessageHtmlLink":"soc: tegra: fix race condition on dvfs rails init"}},{"before":"65eda9da66a035c77483184b8207264da0c05a05","after":"96567b671bb84ad88a6929de83d6f344e7d4629e","ref":"refs/heads/linux-dev","pushedAt":"2023-07-28T19:53:54.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"CTCaer","name":null,"path":"/CTCaer","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3665130?s=80&v=4"},"commit":{"message":"mmc: host: set pad calib true after resuming\n\nSuspend sequence resets the host controller settings.\nHence auto-calibration is needed to be run in the resume\npath. Enable auto-calibration during resuming.\n\nBug 3752857\n\nChange-Id: I8900e43e96ad3f0cc18261c057283335a64857b6\nSigned-off-by: Chenjian \nReviewed-on: https://git-master.nvidia.com/r/c/linux-4.9/+/2799433\nReviewed-by: svcacv \nReviewed-by: Aniruddha Tvs Rao \nReviewed-by: Bibek Basu \nGVS: Gerrit_Virtual_Submit ","shortMessageHtmlLink":"mmc: host: set pad calib true after resuming"}},{"before":"85a61a68887e5101beefda2b496c8a953bf8a3cd","after":"65eda9da66a035c77483184b8207264da0c05a05","ref":"refs/heads/linux-dev","pushedAt":"2023-07-27T20:52:00.000Z","pushType":"push","commitsCount":5,"pusher":{"login":"CTCaer","name":null,"path":"/CTCaer","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3665130?s=80&v=4"},"commit":{"message":"soc: fuse: t210: correct soc speedo 2\n\nAnd deduplicate speedo parsing for the actually used values.","shortMessageHtmlLink":"soc: fuse: t210: correct soc speedo 2"}},{"before":"6698147932554bd3c5ce89da1ea0aaf8c57fc4cf","after":"85a61a68887e5101beefda2b496c8a953bf8a3cd","ref":"refs/heads/linux-dev","pushedAt":"2023-07-27T16:32:51.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"CTCaer","name":null,"path":"/CTCaer","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3665130?s=80&v=4"},"commit":{"message":"scripts/dtc: Remove duplicate YYLOC declaration","shortMessageHtmlLink":"scripts/dtc: Remove duplicate YYLOC declaration"}},{"before":"61f9156857c27ba35dc1bf631700c9d34be6a23d","after":"6698147932554bd3c5ce89da1ea0aaf8c57fc4cf","ref":"refs/heads/linux-dev","pushedAt":"2023-06-13T16:43:57.439Z","pushType":"push","commitsCount":13,"pusher":{"login":"CTCaer","name":null,"path":"/CTCaer","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3665130?s=80&v=4"},"commit":{"message":"input: joycon: improve sio calibration\n\nThe expected calibration on `sio-stick-cal-l` and `sio-stick-cal-r`\nis now the following:\nX- range, X center, X+ range, Y- range, Y center, Y+ range.\nSo the expected raw calibration is expected.\nAdditionally, -+ denotes the stick orientation and not the actual value.\nThat is handled internally.\n\nFinally, `sio-stick-cnt-off-l` and `sio-stick-cnt-off-r` were added to move the\ncenter away from original calibration if needed.\nSio seems to have a ~0x100 offset on left Y and right X.\n\nAnd increase deadzone to 5%.","shortMessageHtmlLink":"input: joycon: improve sio calibration"}},{"before":"92edf31455357f8d5f8bf882a747f42a49746ecf","after":"61f9156857c27ba35dc1bf631700c9d34be6a23d","ref":"refs/heads/linux-dev","pushedAt":"2023-04-21T19:34:34.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"CTCaer","name":null,"path":"/CTCaer","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3665130?s=80&v=4"},"commit":{"message":"input: joycon: use a safer calibration as default\n\nWhen calibration is completely missing, use a tighter range to make sure that\nmaximum axes values can be output.\n\nAdditionally, add `sio-stick-cal-l` and `sio-stick-cal-r` dt properties for\ngetting actual calibration data.\nSince Sio gamepad calibration is stored in prodinfo if factory based and in\nsettings savedata if user based.\n\nThe properties take 6 u32: `x_min, x_center, x_max, y_min, y_center, y_max`.","shortMessageHtmlLink":"input: joycon: use a safer calibration as default"}},{"before":"ce433aa2b8367576fc6d607a1b61bc9c507eb450","after":"92edf31455357f8d5f8bf882a747f42a49746ecf","ref":"refs/heads/linux-dev","pushedAt":"2023-04-13T12:28:13.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"CTCaer","name":null,"path":"/CTCaer","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3665130?s=80&v=4"},"commit":{"message":"mmc: sdhci-tegra: add comment about UHS DDR200\n\nAnd deduplicate tuning window size and tap checks.","shortMessageHtmlLink":"mmc: sdhci-tegra: add comment about UHS DDR200"}},{"before":"55e99402dd72dc889ca5c5700d1f777fc864d020","after":"ce433aa2b8367576fc6d607a1b61bc9c507eb450","ref":"refs/heads/linux-dev","pushedAt":"2023-04-13T11:53:37.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"CTCaer","name":null,"path":"/CTCaer","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3665130?s=80&v=4"},"commit":{"message":"mmc: sdhci-tegra: add comment about UHS DDR200","shortMessageHtmlLink":"mmc: sdhci-tegra: add comment about UHS DDR200"}},{"before":"3eb000b1983eeeb7038b551b539c88458a42a1d6","after":"55e99402dd72dc889ca5c5700d1f777fc864d020","ref":"refs/heads/linux-dev","pushedAt":"2023-04-13T09:36:11.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"CTCaer","name":null,"path":"/CTCaer","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3665130?s=80&v=4"},"commit":{"message":"mmc: sdhci-tegra: enforce min window size for manual tuning\n\nCheck against minimum allowed sampling window size on manual tuning.\nThat allows DDR200 to fail if not enough and then re-init to SDR104.\nA safe window size for DDR200 is 8.","shortMessageHtmlLink":"mmc: sdhci-tegra: enforce min window size for manual tuning"}},{"before":"68e1648524c7deacc9e7346113aa2f60edadc7f2","after":"3eb000b1983eeeb7038b551b539c88458a42a1d6","ref":"refs/heads/linux-dev","pushedAt":"2023-04-11T16:21:03.000Z","pushType":"push","commitsCount":105,"pusher":{"login":"CTCaer","name":null,"path":"/CTCaer","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3665130?s=80&v=4"},"commit":{"message":"arm: tegra: enable xpad neo hid module","shortMessageHtmlLink":"arm: tegra: enable xpad neo hid module"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"startCursor":"Y3Vyc29yOnYyOpK7MjAyMy0wOC0yNVQxMzowMjozMC4wMDAwMDBazwAAAANyg0xV","endCursor":"Y3Vyc29yOnYyOpK7MjAyMy0wNC0xMVQxNjoyMTowMy4wMDAwMDBazwAAAAMWcx7U"}},"title":"Activity ยท CTCaer/switch-l4t-kernel-4.9"}