Received: by 10.223.148.5 with SMTP id 5csp6092351wrq; Wed, 17 Jan 2018 09:15:16 -0800 (PST) X-Google-Smtp-Source: ACJfBovBDgaXOqKnjVOSII/4enkb47DNld4qB5oKjLYwtmDsnyfcAEzzmMNcCBsyKhh7lTaQkzPp X-Received: by 10.99.157.13 with SMTP id i13mr34715968pgd.309.1516209316186; Wed, 17 Jan 2018 09:15:16 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516209316; cv=none; d=google.com; s=arc-20160816; b=BeysXpICobQDY3/vF1jQImFjU15B+7DKRg/snGp6verWZoUtkawd1zf2+K53kphrif a7U0qzAz/DBHT27tzhWvZlNiHgb4lq/fNfl1ZxXLmdUceoz/lDG7OVS6zhJT4uqiX5k1 7BGUKfk0jePRkRhpMkxB+dYf4Ltv61d/4Xd+DlRDwHD6WEi2gxxVB2r4fw1UBxZtURyU HccZDZZD1pW5n8jUJo9lHBNquYxYWkk4YoNowqEZ3w9Y8ZvVUrvQETDae1VKXhtBqN1S gHoiNafSH/WuAsAyeeNgY1onJb2lRRKeF30kozrITiD7SEiWPG3dijslSQXbW0aOtqmt 0fig== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date:dkim-signature :arc-authentication-results; bh=2aT01l4Zhfld+Xo9J52H3lD9gTCT8XmR6a+Kd1/X9zM=; b=fT1hZqRVDEaDNg0hzgUjjnvXJPsIO09VrKjZ86BAPso3zhQZfCmzaI0EZNcraYHH2N J12LQW23BV/AFByl2I/rf6/fAp2Y9IV6Dsvte6BYnMbX/8aCJWNzb36ALTVr9cw/RoKi wwQ03ef21k+8Ivst/Ec2RrTkepke1bH/6rHcVplLWjDkwf20Cy5k4ouI39uEOPBsxgx0 Cb+Md2gjWSKQq272WLTbBCr5ktA6fiaZ0wUkE6PIHZ8Rkvq0ajfj/kOGkPiNlN7BPgzp 2Lpgbsw2qSiW4At745i4QxQyaiup2jBdUcQqe/HEB2By+z88KKhOXmHN9Z1Kt8/wJy3C C1Lw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@ffwll.ch header.s=google header.b=MPLHcs8S; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m184si4181550pgm.698.2018.01.17.09.15.00; Wed, 17 Jan 2018 09:15:16 -0800 (PST) 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=fail header.i=@ffwll.ch header.s=google header.b=MPLHcs8S; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752806AbeAQRNr (ORCPT + 99 others); Wed, 17 Jan 2018 12:13:47 -0500 Received: from mail-wm0-f66.google.com ([74.125.82.66]:44685 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752648AbeAQRNp (ORCPT ); Wed, 17 Jan 2018 12:13:45 -0500 Received: by mail-wm0-f66.google.com with SMTP id t74so16769446wme.3 for ; Wed, 17 Jan 2018 09:13:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=2aT01l4Zhfld+Xo9J52H3lD9gTCT8XmR6a+Kd1/X9zM=; b=MPLHcs8SuGkAZGZfQViEeIZioTblCzCZ9ktEWLnYupnuQsQK1m9QFMcMtpzwUYuYlE GjPFqPU/nzzZAbb3LrXdmVp0dZCAShNo5epydoNdwCIuhfp4letT+fsBmOYMo6BFDLT6 AOYL4x42jZo87Msxd/LaQca2MlLQcZNI/4/MU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=2aT01l4Zhfld+Xo9J52H3lD9gTCT8XmR6a+Kd1/X9zM=; b=ki7YIJgsFe/Rh320M+FSbjPRJcqBg9fjxUbSjch1jaNSEt3MU3E3nFXmjDphnNC4eo 4vVBkbQmEWpIKscjpsfQxghCiYdk6bdiD/OtvorWWKiEaAGmahckPAxBTSQEhweTTg+e pHfiT2/KgF8uOA/cuM5omgw28umvAh4/wsTgEqiIqSrv6ONEJELeuVgKX7NDxiQyAFfv rnl0jf5ye3sC8v9rqxWfUuLTRZdnN/dQABSp1xoRoKCEsKA+IsZ+ztJbzQ4R+JXqjb3w r5ZlAEqQTEz9HrMPm17HbFGDS3R/F2xLPKGSgGy01kgcZwPAdDTofTtV1iUP1Ekoi92C 30hQ== X-Gm-Message-State: AKwxytf8FDxqM1VmC2v2HQwo4i2r0+cyeIXolVWwuZryxPeEkU+AZlFJ kN3jebtelAgMSVE7GpD3SNR3IQ== X-Received: by 10.80.213.138 with SMTP id v10mr3958284edi.170.1516209224096; Wed, 17 Jan 2018 09:13:44 -0800 (PST) Received: from phenom.ffwll.local ([2a02:168:56e6:0:e4bc:76a0:8042:669e]) by smtp.gmail.com with ESMTPSA id 30sm3534401edz.63.2018.01.17.09.13.42 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 17 Jan 2018 09:13:43 -0800 (PST) Date: Wed, 17 Jan 2018 18:13:40 +0100 From: Daniel Vetter To: Daniel Thompson Cc: Daniel Vetter , DRI Development , LKML , Lee Jones , Jingoo Han , Daniel Vetter Subject: Re: [PATCH 2/6] backlight/generic-bl: remove DRIVER1 state Message-ID: <20180117171340.GZ2759@phenom.ffwll.local> Mail-Followup-To: Daniel Thompson , DRI Development , LKML , Lee Jones , Jingoo Han , Daniel Vetter References: <20180117140159.27611-1-daniel.vetter@ffwll.ch> <20180117140159.27611-2-daniel.vetter@ffwll.ch> <9cbcb5d4-1e7c-5df6-a73c-f93b1d2fdbee@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9cbcb5d4-1e7c-5df6-a73c-f93b1d2fdbee@linaro.org> X-Operating-System: Linux phenom 4.14.0-1-amd64 User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 17, 2018 at 04:44:00PM +0000, Daniel Thompson wrote: > On 17/01/18 14:01, Daniel Vetter wrote: > > Nothing in the entire tree ever sets this, which means this is dead > > code. Remove it. > > > > Cc: Lee Jones > > Cc: Daniel Thompson > > Cc: Jingoo Han > > Signed-off-by: Daniel Vetter > > Not sure whether to ack this one or not. > > There is nothing wrong with the change but having taken a closer look the > driver seems like it exists mostly to allow mach-XXX code to plug in > function pointers and we don't do that sort of thing any more. > > I think the entire driver is dead code! Well I can also supply a patch to outright nuke the code, but figuring out whether that's the right thing to do is definitely way above may pay grade :-) I only really stitched these together after a long discussion with Meghana about why backlight seems to have 3+ different ways to enable/disable a backlight. Just trying to help a bit with getting the backlight_enable/disable stuff going, so that long-term, at least for newer drivers, we have one blessed way to do that. btw that kind of display pm simplification matches what we've done when implementing atomic modesetting about 3 years ago: We've smashed all the various power states drm (and fbdev/fbcon) knew about into a simple "is it on?" boolean. Todays digital hw doesn't really know anything in-between. Ofc there's tons of components to switch on/off to get the entire display pipe up, and they might want different autosuspend delays to optimize the overall system, but that's orthogonal (well, driver internal implementation detail) really. Cheers, Daniel > > > Daniel. > > > > --- drivers/video/backlight/generic_bl.c | 5 ----- 1 file changed, 5 > > deletions(-) > > > > diff --git a/drivers/video/backlight/generic_bl.c > > b/drivers/video/backlight/generic_bl.c index > > 67dfb939a514..4dea91acea13 100644 --- > > a/drivers/video/backlight/generic_bl.c +++ > > b/drivers/video/backlight/generic_bl.c @@ -21,9 +21,6 @@ static int > > genericbl_intensity; static struct backlight_device > > *generic_backlight_device; static struct generic_bl_info *bl_machinfo; > > -/* Flag to signal when the battery is low */ -#define > > GENERICBL_BATTLOW BL_CORE_DRIVER1 - static int > > genericbl_send_intensity(struct backlight_device *bd) { int intensity > > = bd->props.brightness; @@ -34,8 +31,6 @@ static int > > genericbl_send_intensity(struct backlight_device *bd) intensity = 0; > > if (bd->props.state & BL_CORE_SUSPENDED) intensity = 0; - if > > (bd->props.state & GENERICBL_BATTLOW) - intensity &= > > bl_machinfo->limit_mask; bl_machinfo->set_bl_intensity(intensity); > > -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch