On 2023-11-15 11:19, Thomas Zimmermann wrote:
The ht16k33 driver operates on system memory. Mark the framebuffer
accordingly. Helpers operating on the framebuffer memory will test
for the presence of this flag.
Signed-off-by: Thomas Zimmermann
Cc: Miguel Ojeda
Cc: Robin van der Gracht
---
On 11/21/23 14:56, Boris Brezillon wrote:
On Tue, 21 Nov 2023 11:40:46 +0100
Thomas Hellström wrote:
Add the first version of the VM_BIND locking document which is
intended to be part of the xe driver upstreaming agreement.
The document describes and discuss the locking used during exec-
Allows drivers to request the Configuration image
be loaded from dma-able continuous buffer to avoid
needless memory pressure and delays due to multiple
copies.
Signed-off-by: Nava kishore Manne
---
drivers/fpga/versal-fpga.c | 13 +
1 file changed, 13 insertions(+)
diff --git
Some systems are memory constrained but they need to load very
large Configuration files. The FPGA subsystem allows drivers to
request this Configuration image be loaded from the filesystem,
but this requires that the entire configuration data be loaded
into kernel memory first before it's
Lots of embedded systems have memory constraints but they need to load
very large configuration files.The FPGA subsystem allows drivers to
request this configuration image be loaded from the filesystem,but this
requires that the entire configuration data be loaded into kernel memory
first before
For the "starry, 2081101qfh032011-53g" panel, it is stipulated in the
panel spec that MIPI needs to keep the LP11 state before the
lcm_reset pin is pulled high.
Fixes: 6069b66cd962 ("drm/panel: support for STARRY 2081101QFH032011-53G
MIPI-DSI panel")
Signed-off-by: xiazhengqiao
Reviewed-by:
On Tue, 14 Nov 2023 at 10:27, Danilo Krummrich wrote:
>
> Make use of the scheduler's credit limit and scheduler job's credit
> count to account for the actual size of a job, such that we fill up the
> ring efficiently.
For the two:
Reviewed-by: Dave Airlie
>
> Signed-off-by: Danilo Krummrich
Hi all,
On Wed, 22 Nov 2023 11:51:37 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the drm-intel tree got a conflict in:
>
> drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_helpers.c
>
> between commit:
>
> 9031e0013f81 ("drm/amd/display: Fix mst hub unplug warning")
>
>
On Tue, 14 Nov 2023 at 08:12, Danilo Krummrich wrote:
>
> GPUVM provides common infrastructure to track external and evicted GEM
> objects as well as locking and validation helpers.
>
> Especially external and evicted object tracking is a huge improvement
> compared to the current brute force
On 11/21/2023 4:27 PM, Rob Clark wrote:
On Tue, Nov 21, 2023 at 4:41 PM Abhinav Kumar wrote:
On 10/24/2023 12:01 PM, Abhinav Kumar wrote:
On 10/23/2023 4:03 PM, Dmitry Baryshkov wrote:
On Tue, 24 Oct 2023 at 01:36, Rob Clark wrote:
On Mon, Oct 23, 2023 at 3:30 PM Dmitry Baryshkov
When the power domains are missing, the call to of_count_phandle_with_args
fails with -ENOENT. The power domains are not required and there are
some device trees that do not specify them. Suppress this error to fix
devices without power domains attached to simplefb.
Fixes: 92a511a568e4
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in:
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_helpers.c
between commit:
9031e0013f81 ("drm/amd/display: Fix mst hub unplug warning")
from Linus' tree and commit:
191dc43935d1 ("drm/dp_mst: Store the MST PBN
./drivers/gpu/drm/nouveau/nvkm/engine/fifo/chan.c: chid.h is included more than
once.
Reported-by: Abaci Robot
Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=7603
Signed-off-by: Yang Li
---
drivers/gpu/drm/nouveau/nvkm/engine/fifo/chan.c | 1 -
1 file changed, 1 deletion(-)
diff
Hi all,
Today's linux-next merge of the drm tree got a conflict in:
drivers/accel/ivpu/ivpu_hw_37xx.c
between commit:
3f7c0634926d ("accel/ivpu/37xx: Fix hangs related to MMIO reset")
from the drm-misc-fixes tree and commits:
3de6d9597892 ("accel/ivpu: Pass D0i3 residency time to the
Hello,
this is v3 of the series improving life-time tracking for PWM chips. The
urgency is gone as device links now work as expected and so all
in-kernel users are fine since commit 2e84dc379200 ("driver core:
Release all resources during unbind before updating device links").
However proper
On Tue, Nov 21, 2023 at 4:41 PM Abhinav Kumar wrote:
>
>
>
> On 10/24/2023 12:01 PM, Abhinav Kumar wrote:
> >
> >
> > On 10/23/2023 4:03 PM, Dmitry Baryshkov wrote:
> >> On Tue, 24 Oct 2023 at 01:36, Rob Clark wrote:
> >>>
> >>> On Mon, Oct 23, 2023 at 3:30 PM Dmitry Baryshkov
> >>> wrote:
>
On 11/21/2023 10:55, Alan Previn wrote:
Add missing tag for "Wa_14019159160 - Case 2" (for existing
PXP code that ensures run alone mode bit is set to allow
PxP-decryption.
Signed-off-by: Alan Previn
---
drivers/gpu/drm/i915/gt/intel_lrc.c | 4 +++-
1 file changed, 3 insertions(+), 1
Hi,
I notice a regression report on Bugzilla [1]. Quoting from it:
> After upgrading from 6.5.9 to 6.6.1 on my Dell Latitude E6420 (Intel
> i5-2520M) with EndeavourOS, the boot process would hang at "loading initial
> ramdisk". The issue is present on the 6.6.1 release of both Linux and
>
On Tue, Nov 21, 2023 at 10:01:18AM +0100, Hans de Goede wrote:
> Hi,
>
> On 11/21/23 02:17, Richard Acayan wrote:
>> Hello,
>>
>> On Wed, Nov 01, 2023 at 06:20:17PM +0100, Thierry Reding wrote:
>>> From: Thierry Reding
>>>
>>> The simple-framebuffer device tree bindings document the
On Wed, Nov 15, 2023 at 11:30 AM Thomas Zimmermann wrote:
>
> + fbdev->info->flags |= FBINFO_VIRTFB;
Is the `|=` (instead of just `=`) used in case someone adds something
to the flags before (e.g. `fb_bl_default_curve`) or due to some other
reason? (One of the other patches uses `=`).
In
On Wed, Nov 15, 2023 at 11:30 AM Thomas Zimmermann wrote:
>
> Initialize the instance of struct fb_ops with fbdev initializer
> macros for framebuffers in virtual address space. Set the read/write,
> draw and mmap callbacks to the correct implementation and avoid
> implicit defaults. Also select
On Wed, Nov 15, 2023 at 11:30 AM Thomas Zimmermann wrote:
>
> Initialize the instance of struct fb_ops with fbdev initializer
> macros for framebuffers in virtual address space. Set the read/write,
> draw and mmap callbacks to the correct implementation and avoid
> implicit defaults. Also select
On Wed, Nov 15, 2023 at 11:30 AM Thomas Zimmermann wrote:
>
> The cfag12864bfb driver operates on system memory. Mark the framebuffer
> accordingly. Helpers operating on the framebuffer memory will test for
> the presence of this flag.
>
> Signed-off-by: Thomas Zimmermann
> Cc: Miguel Ojeda
On 10/24/2023 12:01 PM, Abhinav Kumar wrote:
On 10/23/2023 4:03 PM, Dmitry Baryshkov wrote:
On Tue, 24 Oct 2023 at 01:36, Rob Clark wrote:
On Mon, Oct 23, 2023 at 3:30 PM Dmitry Baryshkov
wrote:
On Tue, 24 Oct 2023 at 01:12, Rob Clark wrote:
From: Rob Clark
Seems like we need to
Use drm_gem_prime_fd_to_handle to import DMABufs for interop. This
ensures that a GEM handle is created on import and that obj->dma_buf
will be set and remain set as long as the object is imported into KFD.
Signed-off-by: Felix Kuehling
Reviewed-by: Ramesh Errabolu
Reviewed-by: Xiaogang.Chen
This reverts commit 71a7974ac7019afeec105a54447ae1dc7216cbb3.
These helper functions are needed for KFD to export and import DMABufs
the right way without duplicating the tracking of DMABufs associated with
GEM objects while ensuring that move notifier callbacks are working as
intended.
CC:
Create GEM handles for exporting DMABufs using GEM-Prime APIs. The GEM
handles are created in a drm_client_dev context to avoid exposing them
in user mode contexts through a DMABuf import.
Signed-off-by: Felix Kuehling
Reviewed-by: Ramesh Errabolu
---
drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c
Change drm_gem_prime_handle_to_fd to drm_gem_prime_handle_to_dmabuf to
export a dmabuf without creating an FD as a user mode handle. This is
more useful for users in kernel mode.
Suggested-by: Thomas Zimmermann
Signed-off-by: Felix Kuehling
---
drivers/gpu/drm/drm_prime.c | 63
tldr; Just FYI, I'm carrying this on the perf tools tree.
Full explanation:
There used to be no copies, with tools/ code using kernel headers
directly. From time to time tools/perf/ broke due to legitimate kernel
hacking. At some point Linus complained about such direct usage. Then we
adopted
Self NAK, this isn't sufficient to fix events.
On Mon, 20 Nov 2023 at 12:07, Dave Airlie wrote:
>
> From: Dave Airlie
>
> The fence code uses the total number of channel ids to allocate a
> bunch of memory for fencing. This is probably not the best way to
> do this, but it's hard to fix right
On Tue, Nov 21, 2023 at 02:37:33AM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Fix UHBR data, link M/N/TU and PBN values (rev6)
> URL : https://patchwork.freedesktop.org/series/126526/
> State : success
Thanks for the reviews and acks, the patchset is pushed to
On 11/21/23 09:16, Linux regression tracking (Thorsten Leemhuis) wrote:
On 15.11.23 07:19, Owen T. Heisler wrote:
On 10/31/23 04:18, Linux regression tracking (Thorsten Leemhuis) wrote:
On 28.10.23 04:46, Owen T. Heisler wrote:
#regzbot introduced: d386a4b54607cf6f76e23815c2c9a3abc1d66882
From: Dave Airlie
This probably isn't the ideal fix, but we ended up using chids
sparsely, and lots of things rely on indexing into the full range,
so just allocate the full range up front.
The GSP code fixes 8 channels into a userd page, but we end up using
a single userd page per channel so
On 21.11.23 19:50, Abhinav Kumar wrote:
> On 11/21/2023 9:57 AM, Linux regression tracking (Thorsten Leemhuis) wrote:
>> On 15.11.23 19:06, Abhinav Kumar wrote:
>>> On 11/15/2023 12:06 AM, Johan Hovold wrote:
On Wed, Oct 25, 2023 at 12:23:10PM +0300, Dmitry Baryshkov wrote:
> While
Add missing tag for "Wa_14019159160 - Case 2" (for existing
PXP code that ensures run alone mode bit is set to allow
PxP-decryption.
Signed-off-by: Alan Previn
---
drivers/gpu/drm/i915/gt/intel_lrc.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
On Tue, Nov 21, 2023 at 4:27 AM Christian König
wrote:
>
> Am 21.11.23 um 05:36 schrieb RutingZhang:
> > checkpatch complains that:
> >
> > WARNING: braces {} are not necessary for single statement blocks
> > +if (pool->base.irqs != NULL) {
> > +
On 11/21/2023 9:57 AM, Linux regression tracking (Thorsten Leemhuis) wrote:
On 15.11.23 19:06, Abhinav Kumar wrote:
On 11/15/2023 12:06 AM, Johan Hovold wrote:
On Wed, Oct 25, 2023 at 12:23:10PM +0300, Dmitry Baryshkov wrote:
While developing and testing the commit bfcc3d8f94f4
On Fri, 13 Oct 2023 11:25:15 +0300, Dan Carpenter wrote:
> This NULL check was required when it was added, but we shuffled the code
> around and now it's not. The inconsistent NULL checking triggers a
> Smatch warning:
>
> drivers/gpu/drm/msm/disp/mdp5/mdp5_kms.c:847 mdp5_init() warn:
>
On Wed, 25 Oct 2023 12:23:08 +0300, Dmitry Baryshkov wrote:
> Fix two failovers in the DP subconnector's patch. I didn't notice that I
> had another patch adding the property in my tree and later Abel pointed
> out that we shouldn't use subconnector type for eDP panels.
>
> Fixes since v1:
> -
On Mon, 30 Oct 2023 16:23:20 -0700, Bjorn Andersson wrote:
> During USB transfers on the SC8280XP __arm_smmu_tlb_sync() is seen to
> typically take 1-2ms to complete. As expected this results in poor
> performance, something that has been mitigated by proposing running the
> iommu in non-strict
On Tue, 07 Nov 2023 13:14:13 +0200, Dmitry Baryshkov wrote:
> It seems during rebases I have left a call to drm_kms_helper_poll_init()
> which is not guarded by the (priv->kms_init) check. This leads to the
> crash for the boards which don't have KMS output. Drop this call, as
> there is a
On Thu, 09 Nov 2023 19:02:14 -0500, Jonathan Marek wrote:
> Use the same value as the downstream driver. This change is needed for CPHY
> mode to work correctly.
>
>
Applied, thanks!
[1/1] drm/msm/dsi: use the correct VREG_CTRL_1 value for 4nm cphy
Hi,
On Mon, Nov 20, 2023 at 10:05 AM Doug Anderson wrote:
>
> Hi,
>
> On Sun, Nov 19, 2023 at 6:01 PM Cong Yang
> wrote:
> >
> > The refresh reported by modetest is 60.46Hz, and the actual measurement
> > is 60.01Hz, which is outside the expected tolerance. Adjust hporch and
> > pixel clock to
On 15.11.23 19:06, Abhinav Kumar wrote:
> On 11/15/2023 12:06 AM, Johan Hovold wrote:
>> On Wed, Oct 25, 2023 at 12:23:10PM +0300, Dmitry Baryshkov wrote:
>>> While developing and testing the commit bfcc3d8f94f4 ("drm/msm/dp:
>>> support setting the DP subconnector type") I had the patch [1] in my
On Wed, Nov 8, 2023 at 4:44 AM Krzysztof Kozlowski
wrote:
>
> Exynos850 reuses several devices from older designs, thus historically
> we kept the old (block's) compatible only. This works fine and there is
> no bug here, however guidelines expressed in
>
Hi Dave,
A few fixes for v6.7, description below
The following changes since commit b08d26dac1a1075c874f40ee02ec8ddc39e20146:
drm/msm/a7xx: actually use a7xx state registers (2023-10-16 09:38:56 -0700)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/msm.git
main driving the register bank has been disabled.
> The following diff might help validate this theory. If that works, we
> probably want to make sure we synchronize IRQs before disabling in the
> suspend path.
>
> --->8---
> diff --git a/drivers/gpu/drm/panfrost/panfrost_regs.h
> b/drivers/
On Tue, 21 Nov 2023 17:11:42 +0100
AngeloGioacchino Del Regno
wrote:
> Il 21/11/23 16:34, Krzysztof Kozlowski ha scritto:
> > On 08/11/2023 14:20, Steven Price wrote:
> >> On 02/11/2023 14:15, AngeloGioacchino Del Regno wrote:
> >>> The layout of the registers {TILER,SHADER,L2}_PWROFF_LO,
The monitors are individually connected to the same card. The Dell 34"
is connected via displayport, and the Sceptre monitor is connected via
HDMI.
Thanks,
Jeff
On Tue, 2023-11-21 at 14:13 +0100, Christian König wrote:
> Hi Jeff,
>
> first of all adding Harry from our display team.
>
> From
https://bugzilla.kernel.org/show_bug.cgi?id=218168
--- Comment #5 from Felix Kuehling (felix.kuehl...@amd.com) ---
There are two patches that didn't make it into Linux 6.6 that reduce the
stack size in kfd_topology_add_device. Can you check if those fix the
problem?
commit
There are two patches that didn't make it into Linux 6.6 that reduce the
stack size in kfd_topology_add_device. Can you check if those fix the
problem?
commit aa5a9b2ccda2fa834fddb4bd30a2ab831598f551
Author: Alex Deucher
Date: Tue Sep 26 12:00:23 2023 -0400
drm/amdkfd: drop struct
On 21/11/2023 17:11, AngeloGioacchino Del Regno wrote:
> Il 21/11/23 16:34, Krzysztof Kozlowski ha scritto:
>> On 08/11/2023 14:20, Steven Price wrote:
>>> On 02/11/2023 14:15, AngeloGioacchino Del Regno wrote:
The layout of the registers {TILER,SHADER,L2}_PWROFF_LO, used to request
From: Danylo Piliaiev
KGSL doesn't support a690 so all reg values were the same as
on a660. Now we know the values and they are different from the
windows driver.
This fixes hangs on D3D12 games and some CTS tests.
Signed-off-by: Danylo Piliaiev
Signed-off-by: Rob Clark
---
Hi,
On Tue, Nov 21, 2023 at 8:05 AM Uwe Kleine-König
wrote:
>
> Hello Doug,
>
> On Tue, Nov 21, 2023 at 07:15:51AM -0800, Doug Anderson wrote:
> > > @@ -1585,22 +1586,28 @@ static const struct pwm_ops ti_sn_pwm_ops = {
> > > static int ti_sn_pwm_probe(struct auxiliary_device *adev,
> > >
anks,
Angelo
1. exynos_defconfig
2. HW: Odroid HC1
ARMv7, octa-core (Cortex-A7+A15), Exynos5422 SoC
arm,mali-t628
Bisect log:
git bisect start
# bad: [07b677953b9dca02928be323e2db853511305fa9] Add linux-next specific files
for 20231121
git bisect ba
Hello Doug,
On Tue, Nov 21, 2023 at 07:15:51AM -0800, Doug Anderson wrote:
> > @@ -1585,22 +1586,28 @@ static const struct pwm_ops ti_sn_pwm_ops = {
> > static int ti_sn_pwm_probe(struct auxiliary_device *adev,
> >const struct auxiliary_device_id *id)
> > {
> > +
Am 17.11.23 um 09:49 schrieb Karolina Stolarek:
Add tests for ttm_bo_init_reserved() and ttm_bo_validate() that use
sys manager. Define a simple move function in ttm_device_funcs. Expose
destroy callback of the buffer object to make testing of
ttm_bo_init_reserved() behaviour easier.
g:
https://krzk.eu/#/builders/21/builds/4392/steps/11/logs/serial0
1. exynos_defconfig
2. HW: Odroid HC1
ARMv7, octa-core (Cortex-A7+A15), Exynos5422 SoC
arm,mali-t628
Bisect log:
git bisect start
# bad: [07b677953b9dca02928be323e2db853511305fa9] Add linux-next specific files
for 20231
Dear Linux folks,
Connecting a USB Type-C port replicator [1] to the only USB Type-C port
of the Dell XPS 13 9360 with Debian sid/unstable and Debian’s Linux
kernel 6.10.5, and then connecting a Philips 40PFL5206H/12 TV device,
that is powered off or in standby, to the HDMI port, Linux logs:
On 15.11.23 07:19, Owen T. Heisler wrote:
> On 10/31/23 04:18, Linux regression tracking (Thorsten Leemhuis) wrote:
>> On 28.10.23 04:46, Owen T. Heisler wrote:
>>> #regzbot introduced: d386a4b54607cf6f76e23815c2c9a3abc1d66882
>>> #regzbot link:
Hi,
On Tue, Nov 21, 2023 at 5:52 AM Uwe Kleine-König
wrote:
>
> This prepares the pwm driver of the ti-sn65dsi86 to further changes of
> the pwm core outlined in the commit introducing devm_pwmchip_alloc().
> There is no intended semantical change and the driver should behave as
> before.
>
>
Am 17.11.23 um 09:49 schrieb Karolina Stolarek:
Remove a leftover definition of page order and pass an empty flag value
in ttm_pool_pre_populated().
Signed-off-by: Karolina Stolarek
Tested-by: Amaranath Somalapuram
Acked-by: Christian König
---
drivers/gpu/drm/ttm/tests/ttm_pool_test.c
On Fri, Nov 17, 2023 at 01:06:25PM +0100, Alexander Stein wrote:
> Use dev_err_probe to simplify error paths. Also let dev_err_probe handle
> the -EPROBE_DEFER case and add an entry to
> /sys/kernel/debug/devices_deferred when deferred.
>
> Signed-off-by: Alexander Stein
Reviewed-by: Daniel
On Wed, Nov 08, 2023 at 01:58:41PM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> This function is only called locally and should always have been static:
>
> drivers/usb/host/fsl-mph-dr-of.c:291:5: error: no previous prototype for
> 'fsl_usb2_mpc5121_init' [-Werror=missing-prototypes]
Hi,
mtk_drm_find_possible_crtc_by_comp() assumed that the main path will
always have the CRTC with id 0, the ext id 1 and the third id 2. This
is only true if the paths are all available. But paths are optional
(see
also comment in mtk_drm_kms_init()), e.g. the main path might not be
enabled
On Tue, 21 Nov 2023 15:29, "Nícolas F. R. A. Prado"
wrote:
>The mtk_dp driver registers a phy device which is handled by the
>phy_mtk_dp driver and assumes that the phy probe will complete
>synchronously, proceeding to make use of functionality exposed by that
>driver right away. This assumption
The mtk_dp driver registers a phy device which is handled by the
phy_mtk_dp driver and assumes that the phy probe will complete
synchronously, proceeding to make use of functionality exposed by that
driver right away. This assumption however is false when the phy driver
is built as a module,
Am 17.11.23 um 09:49 schrieb Karolina Stolarek:
Test reservation and release of TTM buffer objects. Add tests to check
pin and unpin operations.
Signed-off-by: Karolina Stolarek
Tested-by: Amaranath Somalapuram
From the TTM side it looks good, but I can't judge if the lockdep hack
in the
Hi folks,
On Wed 25 Oct 23, 15:09, Paul Kocialkowski wrote:
> The buffer_sel, voffset and hoffset values are calculated from u32
> values and might overflow under certain conditions.
>
> Move them to u32 definitions instead of u8/u16 to avoid the issue.
Any chance to get a quick review on this
On Tue, Nov 21, 2023 at 11:59:14AM +0100, AngeloGioacchino Del Regno wrote:
> Il 20/11/23 21:28, Nícolas F. R. A. Prado ha scritto:
> > The mtk_dp driver registers a phy device which is handled by the
> > phy_mtk_dp driver and assumes that the phy probe will complete
> > synchronously, proceeding
On Mon, Nov 20, 2023 at 5:40 PM Phillip Susi wrote:
>
> Alex Deucher writes:
>
> > Yes. Those changes went into 6.7 though, not 6.6 AFAIK. Maybe I'm
> > misunderstanding what the original report was actually testing. If it
> > was 6.7, then try reverting:
> >
On Tue, 21 Nov 2023 11:40:46 +0100
Thomas Hellström wrote:
> Add the first version of the VM_BIND locking document which is
> intended to be part of the xe driver upstreaming agreement.
>
> The document describes and discuss the locking used during exec-
> functions, evicton and for userptr
On Thu, Nov 16, 2023 at 03:18:31PM +0200, Imre Deak wrote:
[...]
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_helpers.c
> b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_helpers.c
> index ed784cf27d396..63024393b516e 100644
> ---
This prepares the pwm driver of the ti-sn65dsi86 to further changes of
the pwm core outlined in the commit introducing devm_pwmchip_alloc().
There is no intended semantical change and the driver should behave as
before.
Signed-off-by: Uwe Kleine-König
---
drivers/gpu/drm/bridge/ti-sn65dsi86.c |
https://bugzilla.kernel.org/show_bug.cgi?id=218168
Artem S. Tashkinov (a...@gmx.com) changed:
What|Removed |Added
URL|
https://bugzilla.kernel.org/show_bug.cgi?id=218168
--- Comment #4 from Artem S. Tashkinov (a...@gmx.com) ---
Fixed by
https://gitlab.freedesktop.org/drm/amd/uploads/26580b07cb9c763a0b840b9d705e0338/0001-drm-amdkfd-reduce-stack-size-in-kfd_topology_add_dev.patch
--
You may reply to this email
On 2023-11-17 20:40, Rodrigo Vivi wrote:
On Fri, Nov 17, 2023 at 06:21:07PM +0200, Ville Syrjälä wrote:
On Fri, Nov 17, 2023 at 05:09:27PM +0200, Imre Deak wrote:
The current way of calculating the pbn_div value, the link BW per each
MTP slot, worked only for DP 1.4 link rates. Fix things
Am 21.11.23 um 13:20 schrieb Hans de Goede:
Hi Werner,
On 11/21/23 12:33, Werner Sembach wrote:
Hi,
Am 20.11.23 um 21:52 schrieb Pavel Machek:
Hi!
So... a bit of rationale. The keyboard does not really fit into the
LED subsystem; LEDs are expected to be independent ("hdd led") and not
a
On 21.11.2023 09:58, Jani Nikula wrote:
> On Mon, 20 Nov 2023, Heiner Kallweit wrote:
>> v4:
>> - more ack and review tags
>
> Please do not send new versions just to record the acks and
> reviews. They should be added while applying the patches.
>
Right, typically also patchwork interprets and
On Tue, 21 Nov 2023 at 04:26, Rob Clark wrote:
>
> On Wed, Nov 15, 2023 at 11:33 AM Dmitry Baryshkov
> wrote:
> >
> > On Wed, 15 Nov 2023 at 20:46, Dipam Turkar wrote:
> > >
> > > They are not outdated, my bad. I went through the locks' code and saw
> > > that they have been updated. But they
On Tue, Nov 21, 2023 at 11:40:46AM +0100, Thomas Hellström wrote:
> diff --git a/Documentation/gpu/drm-vm-bind-locking.rst
> b/Documentation/gpu/drm-vm-bind-locking.rst
> new file mode 100644
> index ..a7d08eccd50e
> --- /dev/null
> +++ b/Documentation/gpu/drm-vm-bind-locking.rst
> @@
Hi Jeff,
first of all adding Harry from our display team.
From a quick look the obvious missing information is how are your
monitors wired up? Are those individually DP or HDMI connected to the PC
or are they daisy chained through MST?
If it's daisy chained please double check that you
I have a recurring problem where my workstation tries to put the monitor
to sleep, which triggers a warning down in the depths of the video card
driver. When I return to the machine the monitor is black, but not in
powersave mode and all of the windows on my desktop have been shuffled
off to the
Il 30/07/23 20:08, Jiaxin Yu ha scritto:
Add audio support for it6505
1. Bridge to hdmi-codec to support audio feature. At the same time,
the function of automatically detecting audio is removed.
2. It is observed that some DP-to-HDMI dongles will get into bad
states if sending
Hi Werner,
On 11/21/23 12:33, Werner Sembach wrote:
> Hi,
>
> Am 20.11.23 um 21:52 schrieb Pavel Machek:
>> Hi!
>>
> So... a bit of rationale. The keyboard does not really fit into the
> LED subsystem; LEDs are expected to be independent ("hdd led") and not
> a matrix of them.
On 18.11.2023 00:01, Paz Zcharya wrote:
On Tue, Nov 14, 2023 at 10:13:59PM -0500, Rodrigo Vivi wrote:
On Sun, Nov 05, 2023 at 05:27:03PM +, Paz Zcharya wrote:
Fix the value of variable `phys_base` to be the relative offset in
stolen memory, and not the absolute offset of the GSM.
to me
Hi,
Am 20.11.23 um 21:52 schrieb Pavel Machek:
Hi!
So... a bit of rationale. The keyboard does not really fit into the
LED subsystem; LEDs are expected to be independent ("hdd led") and not
a matrix of them.
Makes sense.
We do see various strange displays these days -- they commonly have
On Tue, 21 Nov 2023 at 12:46, Bryan O'Donoghue
wrote:
>
> On 03/11/2023 23:03, Dmitry Baryshkov wrote:
> > Use the freshly defined DRM_AUX_HPD_BRIDGE instead of open-coding the
> > same functionality for the DRM bridge chain termination.
> >
> > Signed-off-by: Dmitry Baryshkov
>
> > +
Il 20/11/23 21:28, Nícolas F. R. A. Prado ha scritto:
The mtk_dp driver registers a phy device which is handled by the
phy_mtk_dp driver and assumes that the phy probe will complete
synchronously, proceeding to make use of functionality exposed by that
driver right away. This assumption however
On Tue, Nov 21, 2023 at 04:56:44PM +0800, Liu Ying wrote:
> Fix a couple of building warnings on used uninitialized 'best_m' and
> 'best_n' local variables by initializing them to zero. This makes compiler
> happy only. No functional change.
>
> Fixes: ce62f8ea7e3f ("drm/bridge: imx: Add i.MX93
On Mon, Nov 20, 2023 at 04:30:53PM +0200, Ville Syrjälä wrote:
> On Fri, Oct 13, 2023 at 04:13:58PM +0300, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > The current LUT rounding is generating weird results. Adjust
> > it to follow the OpenGL int<->float conversion rules.
> >
> > Ville
On 03/11/2023 23:03, Dmitry Baryshkov wrote:
Use the freshly defined DRM_AUX_HPD_BRIDGE instead of open-coding the
same functionality for the DRM bridge chain termination.
Signed-off-by: Dmitry Baryshkov
+ bridge_dev = drm_dp_hpd_bridge_register(tcpm->dev,
Add the first version of the VM_BIND locking document which is
intended to be part of the xe driver upstreaming agreement.
The document describes and discuss the locking used during exec-
functions, evicton and for userptr gpu-vmas. Intention is to be using the
same nomenclature as the
On Fri, 17 Nov 2023, Andy Shevchenko wrote:
> On Thu, Nov 16, 2023 at 12:15:03PM +0200, Jani Nikula wrote:
>> On Thu, 16 Nov 2023, Hans de Goede wrote:
>> > Ok, this now has been testen on both a BYT and a CHT device which
>> > actually use GPIO controls in their MIPI sequences so this
>> >
Am Dienstag, dem 21.11.2023 um 11:22 +0200 schrieb Jani Nikula:
> On Tue, 21 Nov 2023, Bert Karwatzki wrote:
> > As this simple patch fixes the problem
>
> Please use git send-email to send patches. Evolution botched up the
> whitespace here.
>
> BR,
> Jani.
>
>
Noted (actually not the first
Am 17.11.23 um 09:49 schrieb Karolina Stolarek:
Test initialization of ttm_resource using different memory domains.
Add tests for a system memory manager and functions that can be
tested without a fully-featured resource manager. Update
ttm_bo_kunit_init() to initialize BO's kref and a genuine
On Tue, 21 Nov 2023, Bert Karwatzki wrote:
> As this simple patch fixes the problem
Please use git send-email to send patches. Evolution botched up the
whitespace here.
BR,
Jani.
--
Jani Nikula, Intel
On Mon, 20 Nov 2023, Ville Syrjälä wrote:
> On Mon, Nov 20, 2023 at 10:41:18PM +0800, Edward Adam Davis wrote:
>> [Syz Log]
>> divide error: [#1] PREEMPT SMP KASAN
>> CPU: 0 PID: 5068 Comm: syz-executor357 Not tainted
>> 6.6.0-syzkaller-16039-gac347a0655db #0
>> Hardware name: Google Google
1 - 100 of 121 matches
Mail list logo
