Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id EB1B4C7618A for ; Mon, 20 Mar 2023 11:54:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231314AbjCTLyn (ORCPT ); Mon, 20 Mar 2023 07:54:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38822 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231300AbjCTLyj (ORCPT ); Mon, 20 Mar 2023 07:54:39 -0400 Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BA5A810435; Mon, 20 Mar 2023 04:54:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1679313272; x=1710849272; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=tSGuRyYCkEG5apEu/urBdXyfINko5BoAavDLnCG0vqA=; b=S9O9o4hmdt1CkPO/rM1kpZ7MFVwLUalPk+GFzsdeGSudrtCeoxGtMFoE uC6CFzmuFhkRzutilHkBYv7tLBx8GrqjcFwFWqtL/X11U1vOfTBQ8GD/z vMtO8EzVKsia1yBh2KVg1/6TiJWMSCPRCl+i6tx0LxIWP5JkILbjbGY2z Rby5wGiUBmlU6t2rTcQyxAT7URKVuf/SP8jbzLwg07+XH/RB0xAbfWfFF u8paG+Ekof/pFs30ZpmS2MeoKi8/erM4H+mb+Vbb+p6OjxtV2a6X3lNAQ hPVdQ/mR0B19zblLflJLI8lNfMHi4sDzA03fOAWbl/XmV5cj4QeVbHr1h w==; X-IronPort-AV: E=McAfee;i="6600,9927,10654"; a="319040997" X-IronPort-AV: E=Sophos;i="5.98,274,1673942400"; d="scan'208";a="319040997" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Mar 2023 04:54:32 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10654"; a="804880875" X-IronPort-AV: E=Sophos;i="5.98,274,1673942400"; d="scan'208";a="804880875" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga004.jf.intel.com with ESMTP; 20 Mar 2023 04:54:28 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1peE5q-006Fq3-2q; Mon, 20 Mar 2023 13:54:26 +0200 Date: Mon, 20 Mar 2023 13:54:26 +0200 From: Andy Shevchenko To: Linus Walleij Cc: Bartosz Golaszewski , Dmitry Torokhov , linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org, Bartosz Golaszewski , Lee Jones , Daniel Thompson , Jingoo Han , Helge Deller Subject: Re: [PATCH v1 1/1] backlight: hx8357: Convert to agnostic GPIO API Message-ID: References: <20230317185230.46189-1-andriy.shevchenko@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 17, 2023 at 09:53:40PM +0100, Linus Walleij wrote: > On Fri, Mar 17, 2023 at 7:51 PM Andy Shevchenko > wrote: > > > The of_gpio.h is going to be removed. In preparation of that convert > > the driver to the agnostic API. > > > > Signed-off-by: Andy Shevchenko > > Thanks for fixing this Andy! > > > -#if !IS_ENABLED(CONFIG_LCD_HX8357) > > +#if IS_ENABLED(CONFIG_LCD_HX8357) > > /* > > * Himax LCD controllers used incorrectly named > > * "gpios-reset" property and also specified wrong > > @@ -452,7 +452,7 @@ static struct gpio_desc *of_find_gpio_rename(struct device_node *np, > > */ > > const char *compatible; > > } gpios[] = { > > -#if !IS_ENABLED(CONFIG_LCD_HX8357) > > +#if IS_ENABLED(CONFIG_LCD_HX8357) > > /* Himax LCD controllers used "gpios-reset" */ > > { "reset", "gpios-reset", "himax,hx8357" }, > > { "reset", "gpios-reset", "himax,hx8369" }, > > Eh what happened here .. it's even intuitively wrong. I believe it had to be something like #if 0 && IS_ENABLED() to show that this change is for the future. Currently it does something unneeded for the kernels with that option off. > I would add > Fixes: fbbbcd177a27 ("gpiolib: of: add quirk for locating reset lines > with legacy bindings") I'm not sure. But it's fine, I can add it. Just want to double confirm you really want this Fixes tag. > It wasn't used until now it seems so not a regression and no > need for a separate patch. Exactly why I'm not sure about the tag :-) > Other than that it looks correct. > Reviewed-by: Linus Walleij Thank you! -- With Best Regards, Andy Shevchenko