Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp10871703ybi; Thu, 11 Jul 2019 12:28:27 -0700 (PDT) X-Google-Smtp-Source: APXvYqw16jLnx44gzGRFeNfhE45FZ59sw1ucpJGskyrV9WKO1HpIWEVLsUm0lwiKf6jOscXexzzt X-Received: by 2002:a17:902:1e6:: with SMTP id b93mr6437834plb.295.1562873307715; Thu, 11 Jul 2019 12:28:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1562873307; cv=none; d=google.com; s=arc-20160816; b=HppK0U/0aV3+4jAec11NfFPpDU0VcUdatz3KFTaKW/4cPjs3UfFaBQf61C3U5zEXJh tzwE+HVz2QdIEV/ZSO9yuRlCL6je/g54rfHXFhxBY5uHv+iuHFhbgYqMkgA/dcpfCuMv 1S/Ta1640wL1jLGCiQA1/n8bUjTpm/GZC1p6d37he3jQECXHNq+iyZJbX4fwLG+nIRsK zCvqihMTRqB4nOOiZT9WD2ZwROct5ESaVCFDran8/icz/7N1dcu6GDFEleKHOSwiYNRX sSUCSBmj+IVZvXcK1k7PqMgOxi7S3WXlLAyCoqXghYuar6aZcDd3sQ+c6Dp4ZLn9twKH eqpw== 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 :in-reply-to:references:mime-version:dkim-signature; bh=eUSi3tY9WQJoS1EY1aQXpWympsTqMdn0wVqqZqVdQVk=; b=exlsS0ZF6ngBRvj0jgoYfIgPsJKCO2BkDyb/Qa87ktV/mlhi6caYH2IWZMAjaKgZd2 Uma56oHFoWDoLQcf0d0JufUJaaZ7HJe4iEnezWIegxm4GGLI4alDF4TLyJlFG90ALMfB oDA5jIcKGKQow563MMfof5Jj2aWLFX7buJZufcwxfodalm79pNLBJ37yIEUedywF1NmA z6bO4mP2BCsCKNgwCSh5Qhg8PN+ZOpciGC4pe1r93TNEi4XfMRk44DGiruWvdgTi9qTD Z+Am78cuQWrrhNEFtIaMIi3hKPiibWdEgOW8uckX6cPqSufHR2Is08pDPFjNoQhMim5W VZPA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b="camATY/N"; 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=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e5si1880991pgc.29.2019.07.11.12.28.11; Thu, 11 Jul 2019 12:28:27 -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=@chromium.org header.s=google header.b="camATY/N"; 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=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726889AbfGKTRD (ORCPT + 99 others); Thu, 11 Jul 2019 15:17:03 -0400 Received: from mail-ot1-f67.google.com ([209.85.210.67]:36923 "EHLO mail-ot1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726181AbfGKTRC (ORCPT ); Thu, 11 Jul 2019 15:17:02 -0400 Received: by mail-ot1-f67.google.com with SMTP id s20so6991326otp.4 for ; Thu, 11 Jul 2019 12:17:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eUSi3tY9WQJoS1EY1aQXpWympsTqMdn0wVqqZqVdQVk=; b=camATY/NzLRiATqzHBSW98RoE1F6AG2h2nePD+8Gk0Wz6ld60tDwdfxnWllAlmsPC7 gJvgepZ+57xnsETY8vt58D4GWCUEFDBocuGs4tVA5m/lyEVEiVpjJJ5HTFryb0qLF467 hp15q3BDSM1b8agHxbKLbt1CgRB79eLzxHwwQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eUSi3tY9WQJoS1EY1aQXpWympsTqMdn0wVqqZqVdQVk=; b=B/uJOGW+Qg2NEzdCcBklxz2YuYERfyJww5VyZubQc6RpG1UG6VCk3HG5QZEueYUUB9 kYAPNIbwS0XEBJnhqJfs+bP10HDNuqvOiwuArHfnljw5a8oQrwQvfYmRyM22w2mO0lr3 25w4BcV+rRpgMOCMuCpn2FolgIvAdulMkVU/TIggYLnVj2GW5zURR13ETcnpObukXDAJ +LZA/9sniDOfXDzaVA77xKIzybakLcNScvk2xwZc/JttCpgEqnLjWY1hkgplcTa/4Iwq 95d7Js3Or9QvhCxRUWD5BdRskJF6NE/srl9HnuzVo9SXYGVDSNEjRLBz5/x1/S5YDrY6 +eyw== X-Gm-Message-State: APjAAAVikeLusS47cPPBYkykuFlMWeAAU0RBzpj7CKKiAxnW5XzMtglW uxW7q4Q1kDS30QMX9RcrQBBmVuga1vqmfAW00mTJPQ== X-Received: by 2002:a9d:27c3:: with SMTP id c61mr4626820otb.291.1562872621393; Thu, 11 Jul 2019 12:17:01 -0700 (PDT) MIME-Version: 1.0 References: <20190401171724.215780-1-dianders@chromium.org> <20190401171724.215780-3-dianders@chromium.org> <20190630202246.GB15102@ravnborg.org> <20190630205514.GA17046@ravnborg.org> <20190708175606.GB3511@ravnborg.org> In-Reply-To: From: Sean Paul Date: Thu, 11 Jul 2019 15:16:50 -0400 Message-ID: Subject: Re: [PATCH v5 2/7] drm/panel: simple: Add ability to override typical timing To: Doug Anderson Cc: Sam Ravnborg , devicetree@vger.kernel.org, David Airlie , Jeffy Chen , LKML , Rob Herring , "open list:ARM/Rockchip SoC..." , Thierry Reding , dri-devel , Boris Brezillon , =?UTF-8?Q?Enric_Balletb=C3=B2?= , =?UTF-8?Q?St=C3=A9phane_Marchesin?= , Ezequiel Garcia , Matthias Kaehlcke , Laurent Pinchart 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 Wed, Jul 10, 2019 at 6:56 PM Doug Anderson wrote: > > Hi, > > On Mon, Jul 8, 2019 at 10:56 AM Sam Ravnborg wrote: > > > > On Mon, Jul 01, 2019 at 09:39:06AM -0700, Doug Anderson wrote: > > > Hi, > > > > > > On Sun, Jun 30, 2019 at 1:55 PM Sam Ravnborg wrote: > > > > > > > > Hi Douglas. > > > > > > > > > > + > > > > > > + /* Only add timings if override was not there or failed to validate */ > > > > > > + if (num == 0 && panel->desc->num_timings) > > > > > > + num = panel_simple_get_timings_modes(panel); > > > > > > + > > > > > > + /* > > > > > > + * Only add fixed modes if timings/override added no mode. > > > > > > > > > > This part I fail to understand. > > > > > If we have a panel where we in panel-simple have specified the timings, > > > > > and done so using display_timing so with proper {min, typ, max} then it > > > > > should be perfectly legal to specify a more precise variant in the DT > > > > > file. > > > > > Or what did I miss here? > > > > > > > > Got it now. > > > > If display_mode is used for timings this is what you call "fixed mode". > > > > Hmm, if I got confused someone else may also be confused by this naming. > > > > > > The name "fixed mode" comes from the old code, though I guess in the > > > old code it used to refer to a mode that came from either the > > > display_timing or the display_mode. > > > > > > How about if I call it "panel_simple_get_from_fixed_display_mode"? > > > ...or if you have another suggestion feel free to chime in. > > What we really want to distingush here is the use of display_mode > > and display_timings (if I got the names right). > > That display_mode specify a fixed timing and display_timing specify > > a valid range is something in the semantics of the two types. > > So naming that refer to display_mode versus display_timing will make the > > code simpler to understand. and then a nice comment that when > > display_mode > > is used one looses the possibility to use override_mode. > > That would be fine to have in the struct in the driver. > > OK, I can change the names here and try to find a good place to add a comment. > > > > > NOTE: Since this feedback is minor and this patch has been outstanding > > > for a while (and is blocking other work), I am assuming that the best > > > path forward is for Heiko to land this patch with Thierry's Ack and > > > I'll send a follow-up. Please yell if you disagree. > > Let's give the patches a spin more as we have passed the possibility for > > the current merge window. > > Any way I can convince you to change your mind here? There are no > functional changes requested so far in your feedback and no bugs--it's > just a few variable names and comments. By landing the existing > patches as-is: > > 1. We stop spamming all the people CCed on this whole series (which > includes device tree patches) that might be interested in the series > as a whole but aren't interested in details. > > 2. We can debate the bikeshed-type issues on their own merit and I > don't have to debate removing existing Acks / Reviewed-by / Tested-by > tags as I make changes. > > 3. Even if it's not a good time to land the patches right now we know > that these patches will be ready to land as soon as the window opens. > As I mentioned earlier these patches are blocking other work [1] and > landing that patch is actually preventing Matthias from submitting > another series of patches to add support for rk3288-veyron-tiger and > rk3288-veyron-fievel. Certainly I know that upstream doesn't make a > policy of landing things just to suit the timelines of a downstream > project, but in this case there seems very little downsides to landing > the existing patches and taking a later cleanup patch. > [sending from my @chromium.org address so any appearance of bias is explicit :) ] Agree with Doug here, the naming and casting discussion is pretty subjective and non-functional. We've got an Ack from Thierry and a Review from Boris (both seasoned drm_panel'ers), this patch has been sitting in review for a while. Let's not let the perfect be the enemy of the good. Sean > > > I am on vacation at the moment and thus slow in responses, but will be back > > at the home office next week and will be more responsive again. > > > > Sam - who is enjoying the alps in Austria > > Hope you have had a great vacation! > > [1] https://lkml.kernel.org/r/20190625222629.154619-1-mka@chromium.org > > -Doug