-Original Message-
From: Intel-gfx On Behalf Of Jesus
Narvaez
Sent: Thursday, August 8, 2024 1:50 PM
To: intel-gfx@lists.freedesktop.org
Cc: Narvaez, Jesus
Subject: [PATCH] drm/i915/guc: Change GEM_WARN_ON to guc_err to prevent taints
in CI
>
> This warning was supposed to catch a harm
On Fri, Aug 09, 2024 at 10:58:24AM GMT, Lucas De Marchi wrote:
On Fri, Aug 09, 2024 at 04:23:47PM GMT, Jani Nikula wrote:
On Fri, 09 Aug 2024, Jani Nikula wrote:
On Thu, 08 Aug 2024, Lucas De Marchi wrote:
On Thu, Aug 08, 2024 at 06:15:45PM GMT, Jani Nikula wrote:
v2 of https://patchwork.fr
On Fri, Aug 09, 2024 at 04:23:47PM GMT, Jani Nikula wrote:
On Fri, 09 Aug 2024, Jani Nikula wrote:
On Thu, 08 Aug 2024, Lucas De Marchi wrote:
On Thu, Aug 08, 2024 at 06:15:45PM GMT, Jani Nikula wrote:
v2 of https://patchwork.freedesktop.org/series/136621/
Removed "drm/xe/tests: fix drvdata
== Series Details ==
Series: video/aperture: match the pci device when calling sysfb_disable()
URL : https://patchwork.freedesktop.org/series/137088/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_15204 -> Patchwork_137088v1
On Fri, Aug 9, 2024 at 4:48 PM Jann Horn wrote:
> On Tue, Aug 6, 2024 at 2:08 PM Joonas Lahtinen
> wrote:
> > Quoting Andi Shyti (2024-08-06 12:46:07)
> > > Hi Greg,
> > >
> > > same question without the stable mailing list not to trigger the
> > > automatic reply.
> > >
> > > > Andi Shyti (2):
>
== Series Details ==
Series: video/aperture: match the pci device when calling sysfb_disable()
URL : https://patchwork.freedesktop.org/series/137088/
State : warning
== Summary ==
Error: dim checkpatch failed
8ad209af2ad1 video/aperture: match the pci device when calling sysfb_disable()
-:12:
In aperture_remove_conflicting_pci_devices(), match the pci
device determine whether or not to call sysfb_disable(). This
fixes cases where the pimary device is not VGA compatible which
leads to the following problem:
1. A PCI device with a non-VGA class is the the boot display
2. That device is
== Series Details ==
Series: drm/i915: struct intel_display conversions (rev2)
URL : https://patchwork.freedesktop.org/series/136758/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_15204 -> Patchwork_136758v2
Summary
---
On Fri, Aug 09, 2024 at 02:48:08PM +0300, Andy Shevchenko wrote:
> On Fri, Aug 09, 2024 at 11:45:25AM +0530, Raag Jadav wrote:
> > Add hwmon support for fan1_input attribute, which will expose fan speed
> > in RPM. With this in place we can monitor fan speed using lm-sensors tool.
> >
> > $ sensor
== Series Details ==
Series: drm/i915: struct intel_display conversions (rev2)
URL : https://patchwork.freedesktop.org/series/136758/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
On Tue, Aug 6, 2024 at 2:08 PM Joonas Lahtinen
wrote:
> Quoting Andi Shyti (2024-08-06 12:46:07)
> > Hi Greg,
> >
> > same question without the stable mailing list not to trigger the
> > automatic reply.
> >
> > > Andi Shyti (2):
> > > drm/i915/gem: Adjust vma offset for framebuffer mmap offset
Going forward, struct intel_display shall replace struct
drm_i915_private as the main display device data pointer type. Convert
intel_bios.[ch] to struct intel_display.
Do one drive-by conversion of unnecessary hex usage to decimal.
Reviewed-by: Imre Deak
Signed-off-by: Jani Nikula
---
drivers
Going forward, struct intel_display shall replace struct
drm_i915_private as the main display device data pointer type. Convert
intel_acpi.[ch] to struct intel_display.
Reviewed-by: Imre Deak
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/display/intel_acpi.c | 17 -
d
Going forward, struct intel_display shall replace struct
drm_i915_private as the main display device data pointer type. Convert
intel_opregion.[ch] to struct intel_display.
v2:
- Fix declarations for !CONFIG_ACPI (Imre, kernel test robot)
- Pass encoder/connector directly to intel_display() (Imre)
Prefer the short encoder/connector names for struct
intel_encoder/intel_connector variables and parameters.
Reviewed-by: Imre Deak
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/display/intel_opregion.c | 23 +--
drivers/gpu/drm/i915/display/intel_opregion.h | 4 ++--
2 fi
v2 of https://lore.kernel.org/r/cover.1722444150.git.jani.nik...@intel.com
Cc: Imre Deak
Jani Nikula (4):
drm/i915/acpi: convert to struct intel_display
drm/i915/opregion: unify intel_encoder/intel_connector naming
drm/i915/opregion: convert to struct intel_display
drm/i915/bios: convert
On Fri, 09 Aug 2024, Jani Nikula wrote:
> On Thu, 08 Aug 2024, Lucas De Marchi wrote:
>> On Thu, Aug 08, 2024 at 06:15:45PM GMT, Jani Nikula wrote:
>>>v2 of https://patchwork.freedesktop.org/series/136621/
>>>
>>>Removed "drm/xe/tests: fix drvdata usage" from v1 in favour of
>>>"drm/xe/tests: rem
Quoting Jani Nikula (2024-08-08 12:15:54-03:00)
>Use to_intel_display() instead of kdev_to_i915() in the HDCP component
>API hooks. Avoid further drive-by changes at this point, and just
>convert the display pointer to i915, and leave the struct intel_display
>conversion for later.
>
>The NULL erro
Quoting Jani Nikula (2024-08-08 12:15:51-03:00)
>Now that both xe and i915 store struct drm_device in drvdata, we can
>trivially support struct device and struct pci_dev in
>to_intel_display().
>
>We do need to check for NULL drvdata before converting it into struct
>intel_device pointer, though. D
Quoting Jani Nikula (2024-08-08 12:15:49-03:00)
>We have a helper for converting pci device to i915 device, use it.
>
>v2: Also convert i915_pci_probe() (Gustavo)
>
>Cc: Gustavo Sousa
>Signed-off-by: Jani Nikula
Reviewed-by: Gustavo Sousa
>---
> drivers/gpu/drm/i915/i915_pci.c | 6 +++---
> 1 f
Quoting Jani Nikula (2024-08-08 12:15:46-03:00)
>xe_call_for_each_device() has been unused since commit 57ecead343e7
>("drm/xe/tests: Convert xe_mocs live tests"). Remove it and the related
>dev_to_xe_device_fn() and struct kunit_test_data.
>
>Cc: Gustavo Sousa
>Cc: Lucas De Marchi
>Signed-off-by
== Series Details ==
Series: drm/i915/hdcp: Use correct cp_irq_count (rev2)
URL : https://patchwork.freedesktop.org/series/137072/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_15204 -> Patchwork_137072v2
Summary
---
Hi,
On Wed, Aug 07, 2024 at 10:10:14AM +0100, Andi Shyti wrote:
> From: Chris Wilson
>
> After we detect that mmio is returning all 0xff, we believe that the GPU
> has dropped off the pci bus and is dead. Mark the device as wedged such
> that we can propagate the failure back to userspace and wa
On Fri, Aug 09, 2024 at 02:48:08PM +0300, Andy Shevchenko wrote:
> On Fri, Aug 09, 2024 at 11:45:25AM +0530, Raag Jadav wrote:
> > Add hwmon support for fan1_input attribute, which will expose fan speed
> > in RPM. With this in place we can monitor fan speed using lm-sensors tool.
> >
> > $ sensor
On Fri, Aug 09, 2024 at 11:45:25AM +0530, Raag Jadav wrote:
> Add hwmon support for fan1_input attribute, which will expose fan speed
> in RPM. With this in place we can monitor fan speed using lm-sensors tool.
>
> $ sensors
> i915-pci-0300
> Adapter: PCI adapter
> in0: 653.00 mV
> fan1:
We are checking cp_irq_count from the wrong hdcp structure which
ends up giving timed out errors. We only increment the cp_irq_count
of the primary connector's hdcp structure but here in case of
multidisplay setup we end up checking the secondary connector's hdcp
structure, which will not have its
> -Original Message-
> From: Jani Nikula
> Sent: Friday, August 9, 2024 1:51 PM
> To: Kandpal, Suraj ; intel-
> g...@lists.freedesktop.org
> Cc: Nautiyal, Ankit K ; Kandpal, Suraj
>
> Subject: Re: [PATCH] drm/i915/hdcp: Use correct cp_irq_count
>
> On Fri, 09 Aug 2024, Suraj Kandpal
Hi,
> Series: drm/i915/gt: Mark the GT as dead when mmio is unreliable (rev5)
> URL: https://patchwork.freedesktop.org/series/136975/
> State: failure
> Details:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_136975v5/index.html
...
> Possible new issues
>
> Here are the unknown c
On 09/08/2024 10:35, Joonas Lahtinen wrote:
> Quoting Krzysztof Kozlowski (2024-08-08 21:44:39)
>> On 08/08/2024 20:35, Krzysztof Kozlowski wrote:
>>> On 08/08/2024 10:45, Tvrtko Ursulin wrote:
Hi Dave, Sima,
A small bunch of fixes for the weekly cycle:
>>>
>>> ...
>>>
Hi Sima,
On Fri, Aug 09, 2024 at 10:53:38AM +0200, Daniel Vetter wrote:
> On Wed, Aug 07, 2024 at 11:05:19AM +0100, Andi Shyti wrote:
> > This patch series concludes on the memory mapping fixes and
> > improvements by allowing partial memory mapping for the cpu
> > memory as well.
> >
> > The par
Hi Badal,
> > +static int
> > +hwm_fan_read(struct hwm_drvdata *ddat, u32 attr, long *val)
> > +{
> > + struct i915_hwmon *hwmon = ddat->hwmon;
> > + struct hwm_fan_info *fi = &ddat->fi;
> > + u32 reg_val, pulses, time, time_now;
> > + intel_wakeref_t wakeref;
> > + long rotations;
> > +
On Fri, Aug 09, 2024 at 03:03:20PM +0530, Nilawar, Badal wrote:
>
>
> On 09-08-2024 11:45, Raag Jadav wrote:
> > Add hwmon support for fan1_input attribute, which will expose fan speed
> > in RPM. With this in place we can monitor fan speed using lm-sensors tool.
> >
> > $ sensors
> > i915-pci-0
Hi Johna,
On Thu, Aug 08, 2024 at 05:06:46PM -0700, john.c.harri...@intel.com wrote:
> From: John Harrison
>
> The previous update to enable the workaround on ARL only changed two
> out of three places where the w/a needs to be enabled. That meant the
> GuC side was operational but not the KMD s
On 09-08-2024 11:45, Raag Jadav wrote:
Add hwmon support for fan1_input attribute, which will expose fan speed
in RPM. With this in place we can monitor fan speed using lm-sensors tool.
$ sensors
i915-pci-0300
Adapter: PCI adapter
in0: 653.00 mV
fan1:3833 RPM
power1:
On 8/9/2024 2:06 AM, john.c.harri...@intel.com wrote:
From: John Harrison
The previous update to enable the workaround on ARL only changed two
out of three places where the w/a needs to be enabled. That meant the
GuC side was operational but not the KMD side. And as the KMD side is
the trigger,
On Thu, 08 Aug 2024, Lucas De Marchi wrote:
> On Thu, Aug 08, 2024 at 06:15:45PM GMT, Jani Nikula wrote:
>>v2 of https://patchwork.freedesktop.org/series/136621/
>>
>>Removed "drm/xe/tests: fix drvdata usage" from v1 in favour of
>>"drm/xe/tests: remove unused leftover xe_call_for_each_device()" h
On Wed, Aug 07, 2024 at 11:05:19AM +0100, Andi Shyti wrote:
> Hi,
>
> This patch series concludes on the memory mapping fixes and
> improvements by allowing partial memory mapping for the cpu
> memory as well.
>
> The partial memory mapping by adding an object offset was
> implicitely included in
Quoting Krzysztof Kozlowski (2024-08-08 21:44:39)
> On 08/08/2024 20:35, Krzysztof Kozlowski wrote:
> > On 08/08/2024 10:45, Tvrtko Ursulin wrote:
> >>
> >> Hi Dave, Sima,
> >>
> >> A small bunch of fixes for the weekly cycle:
> >
> > ...
> >
> >>
> >>
On Fri, 09 Aug 2024, Suraj Kandpal wrote:
> We are checking cp_irq_count from the wrong hdcp structure which
> ends up giving timed out errors. Extract it from the correct
> intel_hdcp structure.
The change in the referenced commit seems natural. Please explain *why*
it's the wrong hdcp structure
On Thu, 08 Aug 2024, Arun R Murthy wrote:
> HPD is interrupt based and on runtime suspend change it to polling as
> HPD is not a wakeup event. A worker thread is scheduled for doing this
> polling and it keeps polling for HPD live status on an internval of 10s.
> On runtime resume disable polling
On 09/08/2024 09:13, Dave Airlie wrote:
> Hi Krzysztof,
>
> You might want to familiarise yourself with the drm tree development
> procedures before weighing in,
> and snarky comments like the final one are not appreciated on this
> list or in this community.
>
> The drm next trees are never reba
== Series Details ==
Series: drm/i915/guc: Fix missing enable of Wa_14019159160 on ARL
URL : https://patchwork.freedesktop.org/series/137067/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_15202_full -> Patchwork_137067v1_full
===
== Series Details ==
Series: drm/i915/gt: Mark the GT as dead when mmio is unreliable (rev5)
URL : https://patchwork.freedesktop.org/series/136975/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_15202_full -> Patchwork_136975v5_full
=
Hi Krzysztof,
You might want to familiarise yourself with the drm tree development
procedures before weighing in,
and snarky comments like the final one are not appreciated on this
list or in this community.
The drm next trees are never rebased (only in super rare emergencies),
we never rebase ne
Hi Dave, Sima,
here's a fairly small PR for drm-misc-next for this this week. The
controversial Power Saving Policy has been removed. Mgag200 finally
has good support for the BMC output. CI added some more drivers.
Best regards
Thomas
drm-misc-next-2024-08-09:
drm-misc-next for v6.12:
UAPI Chan
45 matches
Mail list logo
