<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div><br>
</div>
<div>On Thu, 2023-03-23 at 08:35 +0000, Tvrtko Ursulin wrote:</div>
<blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<pre>On 23/03/2023 00:27, Teres Alexis, Alan Previn wrote:</pre>
<blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<pre>On Fri, 2023-03-17 at 13:37 +0200, Tamminen, Eero T wrote:</pre>
<blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<pre>Hi,</pre>
<pre><br></pre>
<pre>On 16.3.2023 10.50, Tvrtko Ursulin wrote:</pre>
<blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<pre>[ 11.674183] i915 0000:00:02.0: PXP init-arb-session-15 failed due</pre>
<pre>to BIOS/SOC:0x0000101a:ERR_PLATFORM_CONFIG</pre>
</blockquote>
</blockquote>
<pre>...</pre>
<blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<pre>Alan - is this expected during normal operation on some parts, or it's</pre>
<pre>something truly unexpected/unexplained? If the former then I think it</pre>
<pre>would be good to downgrade away from drm_WARN so it is less scary.</pre>
<pre><br></pre>
<pre>Commit message talks about "HW/platform gaps" - if it is like a missing</pre>
<pre>BIOS support or so then I think WARN_ON is too much.</pre>
</blockquote>
<pre><br></pre>
<pre>Note that this was on pre-production TGL-H HW with BIOS from April 2021.</pre>
<pre><br></pre>
<pre>(I don't know where to get update, nor interested to update it.)</pre>
<pre><br></pre>
<pre><br></pre>
<pre> - Eero</pre>
</blockquote>
<pre><br></pre>
<pre>Alan: Hi Tvrtko, thanks for the feedback -i shall change from WARN_ONCE to drm_info_once.</pre>
</blockquote>
<pre><br></pre>
<pre>Maybe it deserves to be a warning? Or a notice? I was just thinking it </pre>
<pre>does not need a call trace and all since it is not a driver issue. Your </pre>
<pre>call on the level and whether or not there is any chance for it to </pre>
<pre>happen in the field to make the discussion relevant or not.</pre>
</blockquote>
<div><br>
</div>
<div>I agree we don't need a call trace. I can't say how often this can happen in the field as it would depend on</div>
<div>when the platform was purchased, whether the owner had been updating the firwmware releases and whether</div>
<div>the bios settings were configured correctly. I'm okay with the drm_info_once - it could be ignored which is fine.</div>
<div><br>
</div>
<div>If customers seeing protected rendering/decoding fail when they actually DO need it, I am expecting they will</div>
<div>provide the dmesg that shows above new message at compositor startup (mesa attempting to establish caps)</div>
<div>along with more serious complaints such as their application getting a failure when attempting to create a</div>
<div>protected context via I915 ioctl (which aligns with existing PXP UAPI behavior).</div>
<div><br>
</div>
<div>Any chance for an r-b? :)</div>
<div><span></span></div>
</body>
</html>