Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp1307773pxu; Fri, 16 Oct 2020 08:51:33 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzgmFmUCEif9Bpxskk8dJ5Fk0MySxxJwa+PURSUlregpc2mBv4RXJZSu6RT9S6lMKXMpNt5 X-Received: by 2002:aa7:c915:: with SMTP id b21mr4712610edt.25.1602863493449; Fri, 16 Oct 2020 08:51:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1602863493; cv=none; d=google.com; s=arc-20160816; b=b3JFR/cteKUqz0RMRW5GYLiMIP7iU+ml9yU1KblbR6FpADGjJQMg7VxAx7ZTKDLi55 +PJ3scbxp6hAuqILr/EQU/RhqhKeOvr5w/yWUbi82sSHohV89CAp1rxGqpRpIdwEhYms 8SRKPO8Wf6kAYb3OAhv2oplsnmoOuw8u9bO7cqoHbj4ul4augsIQMxcGo+8La1s5ru45 x8ODNqmuJBdf19lJSZVA1I9y1VK8FveoXCy2xrXVHQuop0Nzr/v4RBukYI9kFXUHmCa6 F1tR2OP0I4hs2QeFUXuflUXfXITwGDJvGzKjDy7cFtBKdF8nHuDvea02U/f15ptInJzC cJvw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=tnzanQtl10UFt+rFcqNJjXL8Kqr/Pjj6PJakFG4ukjI=; b=h3bjetJ0R16im1I6ZnMO/93XbffeOm7+4YCUGBkxvi59M29yo8E4RTfESxw4zhnetn KgKtJe6RVcfA+fsw1sxXeoj3NWC4havlw8Sv2KQyHR+3F42O48AP88m0DQmLoFYsXmbQ hPxtjm2aNen+/OayPBqAgyPOsOn/qlYJs0NiOYpmmFP87JJocSfBB2chnLl/IOGuq1Qn Dw+jInZxwWmwdZFRcTRIoZx9anaydyFXvhDrsOT1mcDMAqC8skS2rC7yPn67HoJu23hI n/EQvBLa3IUHaz4yqZhHYXUs9yJX6Bv3xKcEPSJmVwo7ptsNOliYqtGNHEbNPwgid8Mn 6XHA== 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 v10si1914640edw.363.2020.10.16.08.51.11; Fri, 16 Oct 2020 08:51:33 -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 S2408824AbgJPO3W (ORCPT + 99 others); Fri, 16 Oct 2020 10:29:22 -0400 Received: from asavdk4.altibox.net ([109.247.116.15]:53274 "EHLO asavdk4.altibox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2408814AbgJPO3V (ORCPT ); Fri, 16 Oct 2020 10:29:21 -0400 Received: from ravnborg.org (unknown [188.228.123.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by asavdk4.altibox.net (Postfix) with ESMTPS id ABB1E80699; Fri, 16 Oct 2020 16:29:17 +0200 (CEST) Date: Fri, 16 Oct 2020 16:29:16 +0200 From: Sam Ravnborg To: Guido =?iso-8859-1?Q?G=FCnther?= Cc: Thierry Reding , David Airlie , Daniel Vetter , Rob Herring , dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 0/3] drm/panel: mantix panel reset fixes Message-ID: <20201016142916.GA1184974@ravnborg.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-CMAE-Score: 0 X-CMAE-Analysis: v=2.3 cv=fu7ymmwf c=1 sm=1 tr=0 a=S6zTFyMACwkrwXSdXUNehg==:117 a=S6zTFyMACwkrwXSdXUNehg==:17 a=8nJEP1OIZ-IA:10 a=VwQbUJbxAAAA:8 a=pGLkceISAAAA:8 a=e5mUnYsNAAAA:8 a=4K8JB3y5jV4O36iYuCkA:9 a=wPNLvfGTeEIA:10 a=AjGcO6oz07-iQ99wixmX:22 a=Vxmtnl_E_bksehYqCbjh:22 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Guido. On Tue, Oct 13, 2020 at 12:32:45PM +0200, Guido G?nther wrote: > > The first patch in this series fixes dereferencing a NULL mode in the error > path. The second one extends the resets to not only reset RESX but also TP_RSTN > since otherwise the display will stay completely blank. I didn't spot that > before initial submission since the reset line was bound to the touch > controller and although that failed to probe it came far enough to deassert the > reset line (at an arbitrary point in time during boot) and hence we got a > picture. Since touch and panel are on the same IC they're not completely > independent and i might have to turn the whole thing into an MFD at some point > but this series gets the panel to a reliably working state on boot and on fb > blank/unblank. > > Since the reset-gpios are active low we can deassert in prepare and assert in > unprepare simplifying the code making sure lines are kept low when the > panel is off. > > The binding were not part of a stable kernel so I hope it's okay to not worry > about backward compatibility. > > Changes from v1: > - As per review comments by Fabio Estevam > https://lore.kernel.org/dri-devel/CAOMZO5B5ECcConvKej=RcaF8wvOxgq7nUzKJ-ad0aSAOzUqtbQ@mail.gmail.com/ > - Fix typo in commit messages > - As per review comments by Rob Herring > https://lore.kernel.org/dri-devel/20200929174624.GA832332@bogus/ > - Don't use an array of reset lines > > Guido G?nther (3): > drm/panel: mantix: Don't dereference NULL mode > drm/panel: mantix: Fix panel reset > dt-binding: display: Require two resets on mantix panel All applied to drm-misc-next and pushed out. And then I remembered you had commit right - sigh. Sam > > .../display/panel/mantix,mlaf057we51-x.yaml | 4 +++ > .../gpu/drm/panel/panel-mantix-mlaf057we51.c | 25 +++++++++++++------ > 2 files changed, 21 insertions(+), 8 deletions(-) > > -- > 2.28.0 > > _______________________________________________ > dri-devel mailing list > dri-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel