Received: by 10.192.165.148 with SMTP id m20csp320544imm; Thu, 19 Apr 2018 22:48:45 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+wcnkS3FC87v8z1eHVPwqa11eMW8IRzBhFW++Vgkh5BGpS7j222+/dblL8akM4OOaICm1n X-Received: by 10.99.121.6 with SMTP id u6mr7610662pgc.112.1524203325228; Thu, 19 Apr 2018 22:48:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524203325; cv=none; d=google.com; s=arc-20160816; b=sUczqBovQHNNeqb4gv++1F+SUoy+92lUYatY4UxDRuz2taM17b0xyYSHVDm5w6rUC5 UI9jYqBvjnsc/gxjXsRp2Df88kpNI58QbueDVfMA6KXm/peEk5Pxube3lwTX5SnySI8Q RjLo4L1fDma3Vpe3+JWMqpCjTGfahpzZcIn5jEI7NiONnkf+vofQjCTy1Im1DjtSV/S5 uk4BINb3nFsj+J+l/UwDwScsATKq12u+0E5Oy6Dw0J3NpWj0ElDxwSPP4iHgFrFhn0pe Pj/lIbISxK4WMPye8viplu8/Eu/kbYmGO96QTGhjm36wF0waRpW4ntm6yXz0obacDJ35 2exw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=iVbxfeeWkennfMMt4G/fRidWFkDN4TP3SELjHNa0AeQ=; b=HmNlma3DSUlHM/HjO7fRYnV0ucsDj9M0JUrB4CA/Uj9ob4SnNmFwvtd/0fJM0FTOXJ +i2ecgdMXFMkTu0mKwkO58SZKVWqkP2EXn4byXQ/TAreUfP78cF31US+BoaRaYUgy0kM GLvCEoJFm4dAckm+3C6rZccajvymDZXa3jxJvvoE8z/OWphpbxICNN80ssrkRWoBi9YV G7Kn6vbViFHerY2y5vx7ifAJDWoOfs4dR5U6J5NKp8LUGjvNCeUBaBH7bmSYLspFIz3n BbyVB+l/whtVJ3q1IIrmVRvAUVjYifBcyyNA6KsLtymj3i9nFp15F7zSvpza01fXkKky I4EQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=ovi3DIu2; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d24-v6si4964006plr.225.2018.04.19.22.48.30; Thu, 19 Apr 2018 22:48:45 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=ovi3DIu2; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753669AbeDTFrT (ORCPT + 99 others); Fri, 20 Apr 2018 01:47:19 -0400 Received: from mail-wr0-f174.google.com ([209.85.128.174]:44956 "EHLO mail-wr0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751467AbeDTFrR (ORCPT ); Fri, 20 Apr 2018 01:47:17 -0400 Received: by mail-wr0-f174.google.com with SMTP id o15-v6so19590278wro.11; Thu, 19 Apr 2018 22:47:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=iVbxfeeWkennfMMt4G/fRidWFkDN4TP3SELjHNa0AeQ=; b=ovi3DIu2eSXiipY9NNzvHqwqCXWRXxFykaHbtWupwg+zZncali/+OZX7oFHwMOIH0s wDP++yXc1kQKPCySAcoVH1t5A7MshDoVrKytPQaq53CnbKj2sclML5Emp8quzFjoueme cCGCAoGK6Za1bcwFHRBWnBI3OlWD2kSYYe1zyAw2ywK84Mi5GHoY9bDrY/+nWAWVZ9df vIysZEmUqij7jaJmPcOJazMXoA6WkW9MaJbGx+DbKpmGLVf8vyr0pC8JZ5JcYZ4nbXcR A1Y5Y5xgWN3Odo3v7OTCuc3cpF3Xxj762Fmzwgv27MI3lFeMNLpyNKO87TeXEpHqlp9k 1jVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=iVbxfeeWkennfMMt4G/fRidWFkDN4TP3SELjHNa0AeQ=; b=eiQgCLcytgvAQxfDSrbPKddsqqWShu23W7ewfMO0GuxEBGQFydDFAkD7979OJZyLy4 7pEKJdtBlBHK/rCHjd9eKWYMUZ2V2C4s0ACAgD6RVROc/kDhp16yDh++3OHpEQda2WiM r7XRTs1XGZfJuPaSpbYZdW2kFRkLlIWQcum+5Wrihp2udFHE2VpU6MADXqa41O46N1oO /+RJGZBG7sSls7Nm24o4iPRYuobYhjYEltbCKxfUfarcFEyfjbKFp0AFWCrbx23UuPBF O+3K7NdNSbpC9d9Fuh5XCmCjx79JePp+qx0SjkjPXHzXjVK1VO4pHdvJQja5ha1H8+Ok c4rg== X-Gm-Message-State: ALQs6tBXF+PwehDEVyydB88ltdD71nHae6iBvDX8XY0Yr6aSSriMdxMs mClTb0GtWPsr8axolM3lRNiy/CtCZC97hECJAuk= X-Received: by 10.80.235.65 with SMTP id z1mr12047662edp.154.1524203236119; Thu, 19 Apr 2018 22:47:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.225.199 with HTTP; Thu, 19 Apr 2018 22:47:15 -0700 (PDT) In-Reply-To: <152397448099.13647.3490065625139821046@jlahtine-desk.ger.corp.intel.com> References: <20180411044213.383-1-ianwmorrison@gmail.com> <871sfmhz88.fsf@intel.com> <87lgdugc85.fsf@intel.com> <83F5C7385F545743AD4FB2A62F75B073338FD128@ORSMSX108.amr.corp.intel.com> <87r2nefbnn.fsf@intel.com> <152397448099.13647.3490065625139821046@jlahtine-desk.ger.corp.intel.com> From: Ian W MORRISON Date: Fri, 20 Apr 2018 15:47:15 +1000 Message-ID: Subject: Re: [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake To: Joonas Lahtinen Cc: "Srivatsa, Anusha" , Jani Nikula , "Vivi, Rodrigo" , "Wajdeczko, Michal" , Greg KH , "airlied@linux.ie" , "linux-kernel@vger.kernel.org" , "stable@vger.kernel.org" , "intel-gfx@lists.freedesktop.org" , "dri-devel@lists.freedesktop.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 18 April 2018 at 00:14, Joonas Lahtinen wrote: > Quoting Jani Nikula (2018-04-17 12:02:52) >> On Mon, 16 Apr 2018, "Srivatsa, Anusha" wrote: >> >>-----Original Message----- >> >>From: Jani Nikula [mailto:jani.nikula@linux.intel.com] >> >>Sent: Wednesday, April 11, 2018 5:27 AM >> >>To: Ian W MORRISON >> >>Cc: Vivi, Rodrigo ; Srivatsa, Anusha >> >>; Wajdeczko, Michal >> >>; Greg KH ; >> >>airlied@linux.ie; joonas.lahtinen@linux.intel.com; linux-kernel@vger.kernel.org; >> >>stable@vger.kernel.org; intel-gfx@lists.freedesktop.org; dri- >> >>devel@lists.freedesktop.org >> >>Subject: Re: [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for >> >>Geminilake In summary so far: Jani: > NAK on indiscriminate Cc: stable. There are zero guarantees that > older kernels will work with whatever firmware you throw at them. > Who tested the firmware with v4.12 and later? We only have the CI > results against *current* drm-tip. We don't even know about v4.16. > I'm not going to ack and take responsibility for the stable backports > unless someone actually comes forward with credible Tested-bys. Anusha: > The stable kernel version is 4.12 and beyond. > It is appropriate to add the CC: stable in my opinion Joonas: > And even then, some distros will be surprised of the new MODULE_FIRMWARE > and will need to update the linux-firmware package, too. I've performed backport testing and some additional analysis as follows: The DMC firmware for GLK was initially included in 4.11 (commit: dbb28b5c3d3cb945a63030fab8d3894cf335ce19). Then the firmware version was upgraded to 1.03 in 4.12 (commit: f4a791819ed00a749a90387aa139706a507aa690). However MODULE_FIRMWARE for the GLK DMC firmware was also removed in 4.12 (commit: d9321a03efcda867b3a8c6327e01808516f0acd7) together with the firmware version being bumped to 1.04 (commit: aebfd1d37194e00d4c417e7be97efeb736cd9c04). The patch below effectively reverts commit d9321a03 because the GLK firmware is now available in the linux-firmware repository. To test stable backports I've used Ubuntu 18.04 (Beta 2) userspace with both Ubuntu (generic) and self-compiled mainline (patched) kernels. The conclusion was that the patch works across 4.12 to 4.17-rc1 kernels additionally displaying a 'Possible missing firmware' message when installing a kernel with the expected firmware missing. The following are abridged backport test results: Scenario: No DMC (glk_dmc_ver1_04.bin) firmware installed in '/lib/firmware/i915' Test:Kernel installation ('grep -i dmc' output from 'apt install'): 4.12-generic and 4.15-generic: No output # as expected 4.12 to 4.17-rc1-patched: W: Possible missing firmware /lib/firmware/i915/glk_dmc_ver1_04.bin for module i915 Result: The effect of the patch is to add a 'Possible missing firmware' message. Test: Booting ('grep -i dmc' output from 'dmesg'): 4.12-generic: No output # as expected 4.15-generic: i915 0000:00:02.0: Direct firmware load for i915/glk_dmc_ver1_04.bin failed with error -2 i915 0000:00:02.0: Failed to load DMC firmware i915/glk_dmc_ver1_04.bin. Disabling runtime power management. i915 0000:00:02.0: DMC firmware homepage: https://01.org/linuxgraphics/downloads/firmware 4.12-patched: No output # as expected 4.13 to 4.14-patched: i915 0000:00:02.0: Direct firmware load for i915/glk_dmc_ver1_04.bin failed with error -2 i915 0000:00:02.0: Failed to load DMC firmware [https://01.org/linuxgraphics/downloads/firmware], disabling runtime power management. 4.15 to 4.17-rc1-patched: i915 0000:00:02.0: Direct firmware load for i915/glk_dmc_ver1_04.bin failed with error -2 i915 0000:00:02.0: Failed to load DMC firmware i915/glk_dmc_ver1_04.bin. Disabling runtime power management. i915 0000:00:02.0: DMC firmware homepage: https://01.org/linuxgraphics/downloads/firmware Result: The effect of the patch does not change existing (non-patched kernel) messages. Scenario: DMC (glk_dmc_ver1_04.bin) firmware installed in '/lib/firmware/i915' Test:Kernel installation ('grep -i dmc' output from 'apt install') All kernels: No messages # as expected Result: The effect of the patch does not change existing messages. Test" Booting ('grep -i dmc' output from 'dmesg'): 4.12-generic: No output # as expected 4.15-generic: i915 0000:00:02.0: Direct firmware load for i915/glk_dmc_ver1_04.bin failed with error -2 i915 0000:00:02.0: Failed to load DMC firmware i915/glk_dmc_ver1_04.bin. Disabling runtime power management. i915 0000:00:02.0: DMC firmware homepage: https://01.org/linuxgraphics/downloads/firmware 4.12-patched: No output # as expected 4.13 to 4.17-rc1-patched: [drm] Finished loading DMC firmware i915/glk_dmc_ver1_04.bin (v1.4) Result: The effect of the patch is to remove the 'Failed to load' message. Regards, Ian