Convert Qualcomm HDMI binding into HDMI TX and PHY yaml bindings.
Other changes:
- fixed reg-names numbering to match 0..3 instead 0,1,3,4
- phy part moved into phy/ directory
Signed-off-by: David Heidelberg
---
v2:
- move phy into phy/
- added maxItems for gpios
- simplified pinctrl-names
On Sat, 8 Jan 2022 at 22:01, David Heidelberg wrote:
>
> Update documentation compatible and checking to comprehend
> both V2 and 6G version bindings.
>
> Following this commit, there will be update for
> compatible string in chipsets dtsi.
>
> Additional changes:
> - switch to unevaluatedPropert
Update documentation compatible and checking to comprehend
both V2 and 6G version bindings.
Following this commit, there will be update for
compatible string in chipsets dtsi.
Additional changes:
- switch to unevaluatedProperties
Signed-off-by: David Heidelberg
---
Rob, I know you mentioned us
From: Rob Clark
With system suspend using pm_runtime_force_suspend() we can't rely on
the pm_runtime_get_if_in_use() trick to deal with devfreq callbacks
after (or racing with) suspend. So flush any pending idle or boost
work in the suspend path.
Signed-off-by: Rob Clark
---
drivers/gpu/drm/m
From: Rob Clark
System suspend uses pm_runtime_force_suspend(), which cheekily bypasses
the runpm reference counts. This doesn't actually work so well when the
GPU is active. So add a reasonable delay waiting for the GPU to become
idle.
Alternatively we could just return -EBUSY in this case, b
From: Rob Clark
Because system suspend uses pm_runtime_force_suspend() we can't rely
runpm refcnt's to protect us if the GPU is active, etc. Fortunately
*usually* the GPU is idle when system suspend is triggered. But that
isn't quite good enough.
The first patch attempts to block for a modest
Convert Qualcomm HDMI binding into HDMI TX and PHY yaml bindings.
Other changes:
- fixed reg-names numbering to match 0..3 instead 0,1,3,4
- phy part moved into phy/ directory
Signed-off-by: David Heidelberg
---
v2:
- move phy into phy/
- added maxItems for gpios
- simplified pinctrl-names
From: Rob Clark
With system suspend using pm_runtime_force_suspend() we can't rely on
the pm_runtime_get_if_in_use() trick to deal with devfreq callbacks
after (or racing with) suspend. So flush any pending idle or boost
work in the suspend path.
v2: s/ret/remaining [sboyd], and switch to using
From: Rob Clark
System suspend uses pm_runtime_force_suspend(), which cheekily bypasses
the runpm reference counts. This doesn't actually work so well when the
GPU is active. So add a reasonable delay waiting for the GPU to become
idle.
Alternatively we could just return -EBUSY in this case, b
From: Rob Clark
Because system suspend uses pm_runtime_force_suspend() we can't rely
runpm refcnt's to protect us if the GPU is active, etc. Fortunately
*usually* the GPU is idle when system suspend is triggered. But that
isn't quite good enough.
The first patch attempts to block for a modest
On Fri, Jan 7, 2022 at 4:27 PM Stephen Boyd wrote:
>
> Quoting Rob Clark (2022-01-06 10:14:46)
> > From: Rob Clark
> >
> > System suspend uses pm_runtime_force_suspend(), which cheekily bypasses
> > the runpm reference counts. This doesn't actually work so well when the
> > GPU is active. So ad
Avoid leaking the "out" variable if it is not possible to allocate
the "txmsg" variable.
Fixes: 09234b88ef55 ("drm/selftests/test-drm_dp_mst_helper: Move
'sideband_msg_req_encode_decode' onto the heap")
Addresses-Coverity-ID: 1475685 ("Resource leak")
Signed-off-by: José Expósito
---
v2: Impro
Avoid leaking the display mode variable if of_get_drm_display_mode
fails.
Fixes: 76ecd9c9fb24 ("drm/imx: parallel-display: check return code from
of_get_drm_display_mode()")
Addresses-Coverity-ID: 1443943 ("Resource leak")
Signed-off-by: José Expósito
---
v2: Improve commit message
---
driver
Hi All,
On 1/7/22 20:06, Benson Leung wrote:
> Hi Rajat,
>
> Thanks for your changes here.
>
> On Fri, Jan 07, 2022 at 11:02:08AM -0800, Rajat Jain wrote:
>> Add a static entry in the x86 table, to detect and wait for
>> privacy-screen on some ChromeOS platforms.
>>
>> Please note that this mea
Hi Rajat,
On Tue, Dec 21, 2021 at 04:11:26PM -0800, Rajat Jain wrote:
> +static int chromeos_privacy_screen_remove(struct acpi_device *adev)
> +{
> + struct drm_privacy_screen *drm_privacy_screen = acpi_driver_data(adev);
Please add an empty line here:
WARNING: Missing a blank line after dec
https://bugzilla.kernel.org/show_bug.cgi?id=210263
--- Comment #7 from jaromir@gmail.com ---
Related fix for resume from suspend in kernel 5.15 explained here:
https://www.phoronix.com/scan.php?page=news_item&px=AMD-S2idle-Fix-Linux-5.15
The say it could also fix an issue with brightness.
--
https://bugzilla.kernel.org/show_bug.cgi?id=215001
--- Comment #11 from The Linux kernel's regression tracker (Thorsten Leemhuis)
(regressi...@leemhuis.info) ---
(In reply to Kris Karas from comment #10)
> I didn't know whether the regression trackers were a real "bot" sort of
> thing,
Well, I'
17 matches
Mail list logo
