{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":692887248,"defaultBranch":"lineage-21","name":"android_kernel_xiaomi_sm8250","ownerLogin":"umi-development","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2023-09-17T21:59:53.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/145296475?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1714812797.0","currentOid":""},"activityList":{"items":[{"before":"c8be21430ce58d322cfde99aee68bf58bd9314ca","after":"381b39faff2067d637ff57655444d67ba1f8dfaf","ref":"refs/heads/lineage-21","pushedAt":"2024-05-04T08:53:38.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"przekichane","name":"Bartłomiej Rudecki","path":"/przekichane","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34240873?s=80&v=4"},"commit":{"message":"scsi: ufs: Guard `ufs_qcom_parse_lpm` for UMI\n\n- This is what Xiaomi did on cmi-r-oss [1][2].\n- Disable LPM modes results in abnormal power consumption on UMI.\n\nRef:\n[1]: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/blob/cmi-r-oss/drivers/scsi/ufs/ufs-qcom.c#L2033-L2038\n[2]: https://github.com/MiCode/kernel_devicetree/blob/cmi-r-oss/qcom/umi-sm8250.dtsi#L11\n\n* Thanks @TheVoyager0777 for found out this particular change\n\nChange-Id: I78d1fd5936cdd871a2ca2626d4a6e0d335a96c83","shortMessageHtmlLink":"scsi: ufs: Guard <code>ufs_qcom_parse_lpm</code> for UMI"}},{"before":null,"after":"c8be21430ce58d322cfde99aee68bf58bd9314ca","ref":"refs/heads/lineage-21-04052024","pushedAt":"2024-05-04T08:53:17.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"przekichane","name":"Bartłomiej Rudecki","path":"/przekichane","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34240873?s=80&v=4"},"commit":{"message":"techpack: camera-xiaomi-cas: Define missing type specifier\n\nChange-Id: Ic465f22e04572a52c3e5b77eb7ed7dc5b8aa6be2","shortMessageHtmlLink":"techpack: camera-xiaomi-cas: Define missing type specifier"}},{"before":"04085cfda4dd793425500b4f8ea11024310e6483","after":"c8be21430ce58d322cfde99aee68bf58bd9314ca","ref":"refs/heads/lineage-21","pushedAt":"2024-03-04T16:28:13.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"przekichane","name":"Bartłomiej Rudecki","path":"/przekichane","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34240873?s=80&v=4"},"commit":{"message":"techpack: camera-xiaomi-cas: Define missing type specifier\n\nChange-Id: Ic465f22e04572a52c3e5b77eb7ed7dc5b8aa6be2","shortMessageHtmlLink":"techpack: camera-xiaomi-cas: Define missing type specifier"}},{"before":"4b6d18289ddcf5e94f0a891ae5dcad4ab9667705","after":null,"ref":"refs/heads/uno","pushedAt":"2024-02-17T10:21:38.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"przekichane","name":"Bartłomiej Rudecki","path":"/przekichane","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34240873?s=80&v=4"}},{"before":null,"after":"04085cfda4dd793425500b4f8ea11024310e6483","ref":"refs/heads/lineage-21","pushedAt":"2024-02-16T20:55:59.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"przekichane","name":"Bartłomiej Rudecki","path":"/przekichane","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34240873?s=80&v=4"},"commit":{"message":"scsi: ufs: Guard `ufs_qcom_parse_lpm` for UMI\n\n- This is what Xiaomi did on cmi-r-oss [1][2].\n- Disable LPM modes results in abnormal power consumption on UMI.\n\nRef:\n[1]: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/blob/cmi-r-oss/drivers/scsi/ufs/ufs-qcom.c#L2033-L2038\n[2]: https://github.com/MiCode/kernel_devicetree/blob/cmi-r-oss/qcom/umi-sm8250.dtsi#L11\n\n* Thanks @TheVoyager0777 for found out this particular change\n\nChange-Id: I78d1fd5936cdd871a2ca2626d4a6e0d335a96c83","shortMessageHtmlLink":"scsi: ufs: Guard <code>ufs_qcom_parse_lpm</code> for UMI"}},{"before":"4b14739b58f49bc172c3d387eedb2d872c8fa749","after":"4b6d18289ddcf5e94f0a891ae5dcad4ab9667705","ref":"refs/heads/uno","pushedAt":"2024-02-07T20:13:09.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"przekichane","name":"Bartłomiej Rudecki","path":"/przekichane","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34240873?s=80&v=4"},"commit":{"message":"input: touchscreen: goodix_driver_gt9886: Register fod_status node\n\nChange-Id: Ifc0b43d531c762a43ee4d9798352dff9d0c3289e","shortMessageHtmlLink":"input: touchscreen: goodix_driver_gt9886: Register fod_status node"}},{"before":"639c91818a659930695dbe2c311e8c7f82dcbb11","after":"4b14739b58f49bc172c3d387eedb2d872c8fa749","ref":"refs/heads/uno","pushedAt":"2024-01-02T09:29:18.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"przekichane","name":"Bartłomiej Rudecki","path":"/przekichane","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34240873?s=80&v=4"},"commit":{"message":"drm/msm: fix brightness level mapping\n\nThe current brightness level mapping does not correctly map the\nbrightness level range from user space to the range supported by the\npanel.\n\nFor example if the max user brightness reported is 4095, and panel\nbacklight range is 0-255. Then user is expected to be able to set\nbrightness in range from 0-4095, but current logic truncates at\nbl-max (255). Moreover it doesn't take into account bl-min.\n\nFix logic such that the brightness range set by user correctly scales to\nthe backlight level from panel.\n\nBug: 139263611\nChange-Id: Ic70909af63fb5b66ebc1434477f2fc41a785ce1f\nSigned-off-by: Adrian Salido <salidoa@google.com>","shortMessageHtmlLink":"drm/msm: fix brightness level mapping"}},{"before":"afb09ee9df4bcecc93b85b92e4d648d5f598e722","after":null,"ref":"refs/heads/uno-staging","pushedAt":"2023-12-18T13:41:48.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"przekichane","name":"Bartłomiej Rudecki","path":"/przekichane","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34240873?s=80&v=4"}},{"before":null,"after":"afb09ee9df4bcecc93b85b92e4d648d5f598e722","ref":"refs/heads/uno-staging","pushedAt":"2023-12-01T23:43:27.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"przekichane","name":"Bartłomiej Rudecki","path":"/przekichane","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34240873?s=80&v=4"},"commit":{"message":"input: touchscreen: fts_521: Report fp_state to sysfs\n\nSigned-off-by: chaptsand <chaptsand@gmail.com>\nChange-Id: I095918071458a1dd42951927a8c0f90187127a76","shortMessageHtmlLink":"input: touchscreen: fts_521: Report fp_state to sysfs"}},{"before":null,"after":"639c91818a659930695dbe2c311e8c7f82dcbb11","ref":"refs/heads/uno","pushedAt":"2023-11-19T12:32:28.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"przekichane","name":"Bartłomiej Rudecki","path":"/przekichane","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34240873?s=80&v=4"},"commit":{"message":"drm/msm: fix brightness level mapping\n\nThe current brightness level mapping does not correctly map the\nbrightness level range from user space to the range supported by the\npanel.\n\nFor example if the max user brightness reported is 4095, and panel\nbacklight range is 0-255. Then user is expected to be able to set\nbrightness in range from 0-4095, but current logic truncates at\nbl-max (255). Moreover it doesn't take into account bl-min.\n\nFix logic such that the brightness range set by user correctly scales to\nthe backlight level from panel.\n\nBug: 139263611\nChange-Id: Ic70909af63fb5b66ebc1434477f2fc41a785ce1f\nSigned-off-by: Adrian Salido <salidoa@google.com>","shortMessageHtmlLink":"drm/msm: fix brightness level mapping"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"Y3Vyc29yOnYyOpK7MjAyNC0wNS0wNFQwODo1MzozOC4wMDAwMDBazwAAAARBV36N","startCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wNS0wNFQwODo1MzozOC4wMDAwMDBazwAAAARBV36N","endCursor":"Y3Vyc29yOnYyOpK7MjAyMy0xMS0xOVQxMjozMjoyOC4wMDAwMDBazwAAAAOyn1oG"}},"title":"Activity · umi-development/android_kernel_xiaomi_sm8250"}