Interrupts on are non-reentrant on linux. This is just an ancient
leftover from radeon where irq processing was kicked of from different
places.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 1 -
drivers/gpu/drm/amd/amdgpu/amdgpu_ih.c | 5 -
drivers/gpu/
On Fri, Mar 12, 2021 at 02:59:06PM +0100, Christian König wrote:
> Interrupts on are non-reentrant on linux. This is just an ancient
> leftover from radeon where irq processing was kicked of from different
> places.
>
> Signed-off-by: Christian König
Man you tricked me into grepping this on rade
On Wed, Feb 03, 2021 at 04:40:38PM +0100, Christian König wrote:
> Am 03.02.21 um 16:29 schrieb Daniel Vetter:
> > Recently there was a fairly long thread about recoreable hardware page
> > faults, how they can deadlock, and what to do about that.
> >
> > While the discussion is still fresh I figu
On Wed, Mar 10, 2021 at 06:55:30PM +, Matthew Wilcox (Oracle) wrote:
> There's no need to give the page an address_space. Leaving the
> page->mapping as NULL will cause the VM to handle set_page_dirty()
> the same way that it's handled now, and that was the only reason to
> set the address_spa
On Thu, Mar 11, 2021 at 10:31:33PM -0600, Jason Ekstrand wrote:
>
> On March 11, 2021 20:26:06 "Dixit, Ashutosh" wrote:
>
> > On Wed, 10 Mar 2021 13:00:49 -0800, Jason Ekstrand wrote:
> > >
> > > libdrm has supported the newer execbuffer2 ioctl and using it by default
> > > when it exists since
On Thu, 11 Mar 2021 12:16:33 +
Steven Price wrote:
> Also the current code completely ignores PANFROST_BO_REF_READ. So either
> that should be defined as 0, or even better we support 3 modes:
>
> * Exclusive ('write' access)
> * Shared ('read' access)
> * No fence - ensures the BO is
On Thu, Mar 11, 2021 at 12:57:25PM -0600, Jason Ekstrand wrote:
> On Thu, Mar 11, 2021 at 12:20 PM Zbigniew Kempczyński
> wrote:
> >
> > On Thu, Mar 11, 2021 at 11:18:11AM -0600, Jason Ekstrand wrote:
> > > On Thu, Mar 11, 2021 at 10:51 AM Zbigniew Kempczyński
> > > wrote:
> > > >
> > > > On Thu,
On Fri, Mar 12, 2021 at 11:46:27AM +0100, Dmitry Vyukov wrote:
> On Fri, Mar 12, 2021 at 11:26 AM syzbot
> wrote:
> >
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:f78d76e7 Merge tag 'drm-fixes-2021-03-12-1' of git://anong..
> > git tree: upstream
> > consol
On Fri, Mar 12, 2021 at 07:43:05PM +0800, Tian Tao wrote:
> After this patch cbe16f35bee68 genirq: Add IRQF_NO_AUTOEN for
> request_irq/nmi() is merged. request_irq() after setting
> IRQ_NOAUTOEN as below
>
> irq_set_status_flags(irq, IRQ_NOAUTOEN);
> request_irq(dev, irq...);
> can be replaced by
Am 12.03.21 um 15:04 schrieb Daniel Vetter:
On Fri, Mar 12, 2021 at 02:59:06PM +0100, Christian König wrote:
Interrupts on are non-reentrant on linux. This is just an ancient
leftover from radeon where irq processing was kicked of from different
places.
Signed-off-by: Christian König
Man yo
On Fri, Mar 12, 2021 at 03:27:58PM +0100, Christian König wrote:
>
>
> Am 12.03.21 um 15:04 schrieb Daniel Vetter:
> > On Fri, Mar 12, 2021 at 02:59:06PM +0100, Christian König wrote:
> > > Interrupts on are non-reentrant on linux. This is just an ancient
> > > leftover from radeon where irq proc
On Fri, Mar 12, 2021 at 03:35:50PM +0100, Daniel Vetter wrote:
> On Fri, Mar 12, 2021 at 03:27:58PM +0100, Christian König wrote:
> >
> >
> > Am 12.03.21 um 15:04 schrieb Daniel Vetter:
> > > On Fri, Mar 12, 2021 at 02:59:06PM +0100, Christian König wrote:
> > > > Interrupts on are non-reentrant
Am 12.03.21 um 15:36 schrieb Daniel Vetter:
On Fri, Mar 12, 2021 at 03:35:50PM +0100, Daniel Vetter wrote:
On Fri, Mar 12, 2021 at 03:27:58PM +0100, Christian König wrote:
Am 12.03.21 um 15:04 schrieb Daniel Vetter:
On Fri, Mar 12, 2021 at 02:59:06PM +0100, Christian König wrote:
Interrupts
On 2021-03-12 1:50 a.m., Jack Zhang wrote:
re-insert Bailing jobs to avoid memory leak.
Usually we put a v2:"Blha blha blha" here to explain
what was modified in v2
Also - since you make changes to another driver you should
add their maintainer and mailing list probably
(use ./scripts/get_m
On Fri, Mar 12, 2021 at 1:31 AM Boris Brezillon
wrote:
>
> On Thu, 11 Mar 2021 12:11:48 -0600
> Jason Ekstrand wrote:
>
> > > > > > > 2/ Queued jobs might be executed out-of-order (unless they have
> > > > > > > explicit/implicit deps between them), and Vulkan asks that
> > > > > > > the out
From: Tvrtko Ursulin
"Watchdog" aka "restoring hangcheck" aka default request/fence expiry - first
post of a somewhat controversial feature so may be somewhat rough in commit
messages, commentary and implementation. So only RFC for now.
I parenthesise the "watchdog" becuase in classical sense wa
From: Chris Wilson
Currently, we cancel outstanding requests within a context when the
context is closed. We may also want to cancel individual requests using
the same graceful preemption mechanism.
v2 (Tvrtko):
* Cancel waiters carefully considering no timeline lock and RCU.
* Fixed selftests
From: Tvrtko Ursulin
Prepares the plumbing for setting request/fence expiration time. All code
is put in place but is never activeted due yet missing ability to actually
configure the timer.
Outline of the basic operation:
A timer is started when request is ready for execution. If the request
c
From: Tvrtko Ursulin
Disallow sentinel requests follow previous sentinels to make request
cancellation work better when faced with a chain of requests which have
all been marked as in error.
Signed-off-by: Tvrtko Ursulin
---
drivers/gpu/drm/i915/gt/intel_execlists_submission.c | 2 +-
1 file c
From: Tvrtko Ursulin
Idea here is to make the watchdog mechanism more useful than for just
default request/fence expiry.
To this effect a new context param I915_CONTEXT_PARAM_WATCHDOG is added
where the value fields allows passing in a timeout in micro-seconds.
This allows userspace to set a li
From: Tvrtko Ursulin
A new Kconfig option CONFIG_DRM_I915_REQUEST_TIMEOUT is added, defaulting
to 10s, and this timeout is applied to _all_ contexts using the previously
added watchdog facility.
Result of this is that any user submission will simply fail after this
time, either causing a reset (
From: Tvrtko Ursulin
Module parameter is added (request_timeout_ms) to allow configuring the
default request/fence expiry.
Default value is inherited from CONFIG_DRM_I915_REQUEST_TIMEOUT.
Signed-off-by: Tvrtko Ursulin
Cc: Daniel Vetter
---
drivers/gpu/drm/i915/gem/i915_gem_context.c | 8
https://bugzilla.kernel.org/show_bug.cgi?id=210321
--- Comment #5 from Tristen Hayfield (tristen.hayfi...@gmail.com) ---
I did some more digging into this. I put some logging inside the if block to
see if that branch is ever taken:
if (voltage_supported && dummy_pstate_supported) {
On Thu, 11 Mar 2021 at 21:00, Daniel Gomez wrote:
> On Thu, 11 Mar 2021 at 17:10, Alex Deucher wrote:
> >
> > On Thu, Mar 11, 2021 at 10:02 AM Alexandre Desnoyers
> wrote:
> > >
> > > On Thu, Mar 11, 2021 at 2:49 PM Daniel Gomez wrote:
> > > >
> > > > On Thu, 11 Mar 2021 at 10:09, Daniel Gomez
On 2021-03-11 08:26, Christoph Hellwig wrote:
On Wed, Mar 10, 2021 at 06:39:57PM +, Robin Murphy wrote:
Actually... Just mirroring the iommu_dma_strict value into
struct iommu_domain should solve all of that with very little
boilerplate code.
Yes, my initial thought was to directly replace
On Friday, March 12, 2021 3:03:46 AM EST Thomas Zimmermann wrote:
> Hi
>
> Am 12.03.21 um 04:49 schrieb nerdopolis:
> > On Wednesday, March 10, 2021 4:10:35 AM EST Thomas Zimmermann wrote:
> >> Hi
> >>
> >> Am 10.03.21 um 03:50 schrieb nerdopolis:
> >>> On Friday, September 2, 2016 4:22:38 AM EST
https://bugzilla.kernel.org/show_bug.cgi?id=212255
Bug ID: 212255
Summary: WARNING: at arch/x86/kernel/fpu/core.c:129
kernel_fpu_begin_mask
Product: Drivers
Version: 2.5
Kernel Version: 5.11.3
Hardware: x86-64
https://bugzilla.kernel.org/show_bug.cgi?id=212255
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC||alexdeuc...@gmail.c
On Wed 2021-03-10 13:56:29, Peiyong Lin wrote:
> On Mon, Dec 21, 2020 at 12:10 PM Peiyong Lin wrote:
> >
> > Historically there is no common trace event for GPU frequency, in
> > downstream Android each different hardware vendor implements their own
> > way to expose GPU frequency, for example as
On Fri, 12 Mar 2021 09:37:49 -0600
Jason Ekstrand wrote:
> On Fri, Mar 12, 2021 at 1:31 AM Boris Brezillon
> wrote:
> >
> > On Thu, 11 Mar 2021 12:11:48 -0600
> > Jason Ekstrand wrote:
> >
> > > > > > > > 2/ Queued jobs might be executed out-of-order (unless they have
> > > > > > > > expl
https://bugzilla.kernel.org/show_bug.cgi?id=212255
--- Comment #2 from Felice Tufo (i...@felicetufo.com) ---
Thanks Alex,
it seems that Linus merged those patches (just today) for the next -rc release,
am I right?
If so, I'll do a quick test and let you know as soon as Ubuntu team will
release the
https://bugzilla.kernel.org/show_bug.cgi?id=212255
--- Comment #3 from Alex Deucher (alexdeuc...@gmail.com) ---
(In reply to Felice Tufo from comment #2)
> Thanks Alex,
> it seems that Linus merged those patches (just today) for the next -rc
> release, am I right?
correct.
--
You may reply to t
On Fri, 12 Mar 2021 19:25:13 +0100
Boris Brezillon wrote:
> > So where does this leave us? Well, it depends on your submit model
> > and exactly how you handle pipeline barriers that sync between
> > engines. If you're taking option 3 above and doing two command
> > buffers for each VkCommandBu
> > 3. Each VkCommandBuffer is two command buffers: one for compute and
> > one for binning, and you use some sort of HW synchronization mechanism
> > to handle the dependencies as you ping-pong between them.
>
> I didn't consider that option. We have a DOORBELL instruction on Bifrost
> to wake u
Kernel test robot throws below warning ->
drivers/gpu/drm/amd/amdgpu/mmhub_v1_7.c:56:6: warning: no previous
prototype for 'mmhub_v1_7_setup_vm_pt_regs' [-Wmissing-prototypes]
Mark mmhub_v1_7_setup_vm_pt_regs() as static.
Reported-by: kernel test robot
Signed-off-by: Souptick Joarder
---
driv
[AMD Official Use Only - Internal Distribution Only]
Thank you Joarder for the fix. But this has already been fixed in our Alex's
drm-next branch.
Regards,
Oak
On 2021-03-12, 5:19 PM, "Souptick Joarder" wrote:
Kernel test robot throws below warning ->
drivers/gpu/drm/amd/amdgpu/mm
On Fri, Mar 12, 2021 at 09:36:42AM +0100, Greg Kroah-Hartman wrote:
> On Fri, Mar 12, 2021 at 04:14:21PM +0800, Du Cheng wrote:
> > add null-check on function pointer before dereference on ops->cursor
> >
> > Reported-by: syzbot+b67aaae8d3a927f68...@syzkaller.appspotmail.com
> > Signed-off-by: Du
Common pattern of handling deferred probe can be simplified with
dev_err_probe(). Less code and also it prints the error value.
Signed-off-by: Tian Tao
---
drivers/gpu/host1x/mipi.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/host1x/mipi.c b/drivers/gp
From: Junlin Yang
Fixes coccicheck warnings:
./drivers/gpu/drm/kmb/kmb_dsi.c:284:3-4: Unneeded semicolon
./drivers/gpu/drm/kmb/kmb_dsi.c:304:3-4: Unneeded semicolon
./drivers/gpu/drm/kmb/kmb_dsi.c:321:3-4: Unneeded semicolon
./drivers/gpu/drm/kmb/kmb_dsi.c:340:3-4: Unneeded semicolon
./drivers/gp
https://bugzilla.kernel.org/show_bug.cgi?id=212259
Bug ID: 212259
Summary: Entire graphics stack locks up when running SteamVR
and sometimes Sway; is sometimes unrecoverable
Product: Drivers
Version: 2.5
Kernel Version: 5.11.0
platform_get_irq() has already checked and printed the return value,
the printing here is nothing special, it is not necessary at all.
Signed-off-by: Wang Qing
---
drivers/gpu/drm/mediatek/mtk_dpi.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/mediatek/
On Sun, Mar 07, 2021 at 07:28:30PM +, Paul Cercueil wrote:
> The NT39016 panel is a fun beast, even though the documentation states
> that the CS line is active-low, it will work just fine if the CS line is
> configured as active-high, but it won't work if the CS line is forced
> low or forced
On Sun, Mar 07, 2021 at 07:28:29PM +, Paul Cercueil wrote:
> The NT39016 panel is a fun beast, even though the documentation states
> that the CS line is active-low, it will work just fine if the CS line is
> configured as active-high, but it won't work if the CS line is forced
> low or forced
Hi
Am 12.03.21 um 04:49 schrieb nerdopolis:
On Wednesday, March 10, 2021 4:10:35 AM EST Thomas Zimmermann wrote:
Hi
Am 10.03.21 um 03:50 schrieb nerdopolis:
On Friday, September 2, 2016 4:22:38 AM EST David Herrmann wrote:
Hey
On request of Noralf, I picked up the patches and prepared v5. W
Am 12.03.21 um 00:02 schrieb Zack Rusin:
On Mar 11, 2021, at 17:35, Thomas Hellström (Intel)
wrote:
Hi, Zack
On 3/11/21 10:07 PM, Zack Rusin wrote:
On Mar 11, 2021, at 05:46, Thomas Hellström (Intel)
wrote:
Hi,
I tried latest drm-fixes today and saw a lot of these: Fallout from ttm r
add null-check on function pointer before dereference on ops->cursor
Reported-by: syzbot+b67aaae8d3a927f68...@syzkaller.appspotmail.com
Signed-off-by: Du Cheng
---
drivers/video/fbdev/core/fbcon.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/video/fbdev/core/fbcon.c b/drivers/v
On Fri, Mar 12, 2021 at 04:14:21PM +0800, Du Cheng wrote:
> add null-check on function pointer before dereference on ops->cursor
>
> Reported-by: syzbot+b67aaae8d3a927f68...@syzkaller.appspotmail.com
> Signed-off-by: Du Cheng
> ---
> drivers/video/fbdev/core/fbcon.c | 3 +++
> 1 file changed, 3
This is the sixth version of a series to add support to Nouveau for atomic
memory operations on OpenCL shared virtual memory (SVM) regions.
There are no significant changes for version six other than correcting a
minor s390 build and bisectability issue and removing a redundant call to
compound_pa
Remove the migration and device private entry_to_page() and
entry_to_pfn() inline functions and instead open code them directly.
This results in shorter code which is easier to understand.
Signed-off-by: Alistair Popple
Reviewed-by: Ralph Campbell
---
v6:
* Removed redundant compound_page() ca
Both migration and device private pages use special swap entries that
are manipluated by a range of inline functions. The arguments to these
are somewhat inconsitent so rework them to remove flag type arguments
and to make the arguments similar for both read and write entry
creation.
Signed-off-by
The behaviour of try_to_unmap_one() is difficult to follow because it
performs different operations based on a fairly large set of flags used
in different combinations.
TTU_MUNLOCK is one such flag. However it is exclusively used by
try_to_munlock() which specifies no other flags. Therefore rather
Migration is currently implemented as a mode of operation for
try_to_unmap_one() generally specified by passing the TTU_MIGRATION flag
or in the case of splitting a huge anonymous page TTU_SPLIT_FREEZE.
However it does not have much in common with the rest of the unmap
functionality of try_to_unma
Adds some selftests for exclusive device memory.
Signed-off-by: Alistair Popple
Acked-by: Jason Gunthorpe
Tested-by: Ralph Campbell
Reviewed-by: Ralph Campbell
---
lib/test_hmm.c | 124 ++
lib/test_hmm_uapi.h| 2 +
tools/testing/selfte
Call mmu_interval_notifier_insert() as part of nouveau_range_fault().
This doesn't introduce any functional change but makes it easier for a
subsequent patch to alter the behaviour of nouveau_range_fault() to
support GPU atomic operations.
Signed-off-by: Alistair Popple
---
drivers/gpu/drm/nouve
Some devices require exclusive write access to shared virtual
memory (SVM) ranges to perform atomic operations on that memory. This
requires CPU page tables to be updated to deny access whilst atomic
operations are occurring.
In order to do this introduce a new swap entry
type (SWP_DEVICE_EXCLUSIV
Some NVIDIA GPUs do not support direct atomic access to system memory
via PCIe. Instead this must be emulated by granting the GPU exclusive
access to the memory. This is achieved by replacing CPU page table
entries with special swap entries that fault on userspace access.
The driver then grants th
From: "Carlis"
Document support for the Waveshare 2inch LCD module display, which is a
240x320 2" TFT display driven by a Sitronix ST7789V TFT Controller.
Signed-off-by: Carlis
---
v2:change compatible name.
---
.../display/sitronix,st7789v-dbi.yaml | 72 +++
1 file cha
Support IEC958 encoded PCM format for ADV7511 so that ADV7511 HDMI
audio driver can accept the IEC958 data from the I2S input.
Signed-off-by: Sia Jee Heng
---
drivers/gpu/drm/bridge/adv7511/adv7511.h | 1 +
drivers/gpu/drm/bridge/adv7511/adv7511_audio.c | 6 ++
2 files changed, 7 inser
From: "Carlis"
This adds a new module for the ST7789V controller with parameters for
the Waveshare 2inch LCD module.
Signed-off-by: Carlis
---
v2:change compatible value.
---
MAINTAINERS| 7 +
drivers/gpu/drm/tiny/Kconfig | 14 ++
drivers/gpu/drm/tiny/Makefile | 1 +
On Fri, Mar 12, 2021 at 09:36:42AM +0100, Greg Kroah-Hartman wrote:
> On Fri, Mar 12, 2021 at 04:14:21PM +0800, Du Cheng wrote:
> > add null-check on function pointer before dereference on ops->cursor
> >
> > Reported-by: syzbot+b67aaae8d3a927f68...@syzkaller.appspotmail.com
> > Signed-off-by: Du
We seem to have some more driver bugs than thought.
Signed-off-by: Christian König
---
include/drm/ttm/ttm_bo_api.h | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/include/drm/ttm/ttm_bo_api.h b/include/drm/ttm/ttm_bo_api.h
index 4fb523dfab32..df9fe596e7c5 100644
--- a/
On Thu, Mar 11, 2021 at 05:11:36AM +1000, Dave Airlie wrote:
> On Wed, 10 Mar 2021 at 17:48, Maxime Ripard wrote:
> >
> > Hi Dave,
> >
> > On Wed, Mar 10, 2021 at 09:50:29AM +1000, Dave Airlie wrote:
> > > I'm mostly sending this to the -misc maintainers because
> > > drm-misc-fixes is based on rc
On 3/12/21 12:02 AM, Zack Rusin wrote:
On Mar 11, 2021, at 17:35, Thomas Hellström (Intel)
wrote:
Hi, Zack
On 3/11/21 10:07 PM, Zack Rusin wrote:
On Mar 11, 2021, at 05:46, Thomas Hellström (Intel)
wrote:
Hi,
I tried latest drm-fixes today and saw a lot of these: Fallout from ttm rewo
From: Colin Ian King
There is a spelling mistake in an assert message. Fix it.
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/amd/pm/powerplay/hwmgr/smu7_hwmgr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/pm/powerplay/hwmgr/smu7_hwmgr.c
b/driver
On Fri, 12 Mar 2021 at 09:38, Christian König
wrote:
>
> We seem to have some more driver bugs than thought.
>
> Signed-off-by: Christian König
Acked-by: Matthew Auld
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.
(Adding back James again - did you use get_maintainer.pl?)
On Thu, Mar 11, 2021 at 12:08:46PM +, carsten.haitz...@foss.arm.com wrote:
> From: Carsten Haitzler
>
> When setting up a readback connector that writes data back to memory
> rather than to an actual output device (HDMI etc.), roundi
Hello,
syzbot found the following issue on:
HEAD commit:f78d76e7 Merge tag 'drm-fixes-2021-03-12-1' of git://anong..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11c16ba2d0
kernel config: https://syzkaller.appspot.com/x/.config?x=dc02c6afcb046874
das
On Fri, 12 Mar 2021 at 06:33, Viresh Kumar wrote:
>
> On 11-03-21, 22:20, Dmitry Osipenko wrote:
> > +struct opp_table *devm_pm_opp_set_clkname(struct device *dev, const char
> > *name)
> > +{
> > + struct opp_table *opp_table;
> > + int err;
> > +
> > + opp_table = dev_pm_opp_set_clk
After this patch cbe16f35bee68 genirq: Add IRQF_NO_AUTOEN for
request_irq/nmi() is merged. request_irq() after setting
IRQ_NOAUTOEN as below
irq_set_status_flags(irq, IRQ_NOAUTOEN);
request_irq(dev, irq...);
can be replaced by request_irq() with IRQF_NO_AUTOEN flag.
Signed-off-by: Tian Tao
---
Le jeu. 11 mars 2021 à 12:28, Christoph Hellwig a
écrit :
On Sun, Mar 07, 2021 at 08:28:34PM +, Paul Cercueil wrote:
+ drm_atomic_for_each_plane_damage(&iter, &clip) {
+ for (i = 0; i < finfo->num_planes; i++) {
+ daddr = drm_fb_cma_get_gem_addr
Le jeu. 11 mars 2021 à 12:30, Christoph Hellwig a
écrit :
On Sun, Mar 07, 2021 at 08:28:35PM +, Paul Cercueil wrote:
With the module parameter ingenic-drm.cached_gem_buffers, it is
possible
to specify that we want GEM buffers backed by non-coherent memory.
Shouldn't there be a way
Le jeu. 11 mars 2021 à 12:36, Christoph Hellwig a
écrit :
On Thu, Mar 11, 2021 at 12:32:27PM +, Paul Cercueil wrote:
> dma_to_phys must not be used by drivers.
>
> I have a proper helper for this waiting for users:
>
>
http://git.infradead.org/users/hch/misc.git/commitdiff/96a546e
Den 12.03.2021 05.32, skrev Peter Stuge:
> Ilia Mirkin wrote:
>> XRGB means that the memory layout should match a 32-bit integer,
>> stored as LE, with the low bits being B, next bits being G, etc. This
>> translates to byte 0 = B, byte 1 = G, etc. If you're on a BE system,
>> and you're han
https://bugzilla.kernel.org/show_bug.cgi?id=212229
--- Comment #3 from Yauheni Saldatsenka (eugen...@gmail.com) ---
Created attachment 295809
--> https://bugzilla.kernel.org/attachment.cgi?id=295809&action=edit
/sys/kernel/debug/dri/0/state
--
You may reply to this email to add a comment.
You
https://bugzilla.kernel.org/show_bug.cgi?id=210321
Tristen Hayfield (tristen.hayfi...@gmail.com) changed:
What|Removed |Added
CC||tristen.ha
12.03.2021 08:26, Viresh Kumar пишет:
> On 11-03-21, 22:20, Dmitry Osipenko wrote:
>> From: Yangtao Li
>>
>> Add devres wrapper for dev_pm_opp_register_notifier() to simplify driver
>> code.
>>
>> Signed-off-by: Yangtao Li
>> Signed-off-by: Dmitry Osipenko
>> ---
>> drivers/opp/core.c | 38
12.03.2021 13:36, Ulf Hansson пишет:
> On Fri, 12 Mar 2021 at 06:33, Viresh Kumar wrote:
>>
>> On 11-03-21, 22:20, Dmitry Osipenko wrote:
>>> +struct opp_table *devm_pm_opp_set_clkname(struct device *dev, const char
>>> *name)
>>> +{
>>> + struct opp_table *opp_table;
>>> + int err;
>>> +
This is a note to let you know that I've just added the patch titled
drm/fb-helper: only unmap if buffer not null
to the 5.11-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
drm-fb-he
78 matches
Mail list logo
