Received: by 2002:a25:683:0:0:0:0:0 with SMTP id 125csp671630ybg; Tue, 9 Jun 2020 09:55:04 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxAMnVlHQn3ndmYgaxV1LDoJu9Ch0RCBdKLILt8VCqvaod6Te+8P4nR03TrSIulNwS70lhz X-Received: by 2002:a05:6402:1d29:: with SMTP id dh9mr27557494edb.269.1591721703900; Tue, 09 Jun 2020 09:55:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1591721703; cv=none; d=google.com; s=arc-20160816; b=OnkjWnKaeug7exsAouE54JFNRhJt7OTVYl9v/gcZy/MP/xvXw3R9hAnsN5B7neZWg/ wfoa7p8e6JNOH0eOTr1CK3Ds1G8xGpSnrQ28xJczu2KI1TnjjHPoB3bqIdSHSFd+mgRp b5Gcth3wkJQcxHFB7Ka7+fnLLRC+yJCgkxDGEgsV8+oun9gel0VmuxSB0p9QyWd86/L7 piRs9cviTl+CQ1XI7/miXQfx8QndHD6sCpSoqV5XgijS72sTtvj0jjJmCdTkTM1+ORlU yhaZnhC1/adHWSOo9k+O7Bod7WQ5IaK4zK6XbX04czNtGlMBeAxViz+6hjBCk0RKmyhm FXtQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=d3Vv6kNfJcX+2hWoeUOykj88lxf6ARN2d59BaySILx8=; b=OH4ttUay3z+s+9mZuUF3V5zOUJzTRlFZ36VVjwp048UEplAYBVAqGRHOrxSFhcLRtV rc0oG3FZItTYqdID8ufZpA1Z+jeutUrpACf9MnmhoMY6YOg3c7ZFjKxRvwvs24uqsBut PM/QaxRV0M04MRBF1cFZc4xftA2m8tXfTgwDUpyQfWVEmrAmIOKCqGonzDH2jbXeHRjR Fx6wE4CLDxvpDch2U3TQw0UVhTeWxvw3oJjb0xUEUu2sud6vHc92cJ4VvK4bp0ps7WXz 7JXiiBtD+H4f0+kcIa4rxc8g7vIeJEXjqbpiepfq0yko6yxJhrKhkPtqc9qwPTQxdYzH x1RQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v10si8920340edy.534.2020.06.09.09.54.41; Tue, 09 Jun 2020 09:55:03 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731226AbgFIQwk (ORCPT + 99 others); Tue, 9 Jun 2020 12:52:40 -0400 Received: from muru.com ([72.249.23.125]:57404 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729988AbgFIQwk (ORCPT ); Tue, 9 Jun 2020 12:52:40 -0400 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id DA2BC8088; Tue, 9 Jun 2020 16:53:28 +0000 (UTC) Date: Tue, 9 Jun 2020 09:52:34 -0700 From: Tony Lindgren To: Tomi Valkeinen Cc: linux-omap@vger.kernel.org, "Andrew F . Davis" , Dave Gerlach , Faiz Abbas , Greg Kroah-Hartman , Grygorii Strashko , Keerthy , Nishanth Menon , Peter Ujfalusi , Roger Quadros , Suman Anna , Tero Kristo , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, dri-devel@lists.freedesktop.org, Laurent Pinchart Subject: Re: [PATCH 1/5] drm/omap: Fix suspend resume regression after platform data removal Message-ID: <20200609165234.GM37466@atomide.com> References: <20200531193941.13179-1-tony@atomide.com> <20200531193941.13179-2-tony@atomide.com> <16ba1808-5c7f-573d-8dd0-c80cac2f476e@ti.com> <20200603140639.GG37466@atomide.com> <47e286dd-f87a-4440-5bde-1f7b53e8b672@ti.com> <20200609151943.GL37466@atomide.com> <9ed70121-2a53-d2b3-051a-88eb83e6c53f@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9ed70121-2a53-d2b3-051a-88eb83e6c53f@ti.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Tomi Valkeinen [200609 15:27]: > On 09/06/2020 18:19, Tony Lindgren wrote: > > Currently I'm only able to rmmod -f omapdrm, not sure if these issues might > > be related. > > Hmm, I always use modules, and can unload omapdrm and drm fine. But there's > a sequence that must be followed. However, the sequence starts with > unloading omapdrm... What behavior you see with rmmod? Hmm maybe it's output specific somehow? I just tried again with the following with v5.7. I see the omapdrm usage count issue happen at least on duovero, but don't seem to currently get /dev/fb0 initialized on x15 with these: modprobe omapdrm #modprobe connector_hdmi # up to v5.6 modprobe display-connector # starting with v5.7-rc1 modprobe ti-tpd12s015 # beagle-x15 modprobe omapdss # rmmod omapdrm rmmod: ERROR: Module omapdrm is in use # lsmod | grep omapdrm omapdrm 65536 1 omapdss_base 16384 2 omapdrm,omapdss drm_kms_helper 155648 3 omapdss_base,omapdrm,omapdss drm 372736 7 ti_tpd12s015,omapdss_base,display_connector,omapdrm,omapdss,drm_kms_helper On beagle-x15 I see these errors after modprobe: DSS: OMAP DSS rev 6.1 omapdss_dss 58000000.dss: bound 58001000.dispc (ops dispc_component_ops [omapdss]) omapdss_dss 58000000.dss: bound 58040000.encoder (ops hdmi5_component_ops [omapdss]) [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). omapdrm omapdrm.0: [drm] Cannot find any crtc or sizes [drm] Initialized omapdrm 1.0.0 20110917 for omapdrm.0 on minor 0 omapdrm omapdrm.0: [drm] Cannot find any crtc or sizes aic_dvdd_fixed: disabling ldousb: disabling Maybe I'm missing some related module on x15? Regards, Tony