From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C483BC64EB8 for ; Wed, 3 Oct 2018 16:58:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 899852098A for ; Wed, 3 Oct 2018 16:58:59 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 899852098A Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=bootlin.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727368AbeJCXsL (ORCPT ); Wed, 3 Oct 2018 19:48:11 -0400 Received: from mail.bootlin.com ([62.4.15.54]:45142 "EHLO mail.bootlin.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726842AbeJCXsK (ORCPT ); Wed, 3 Oct 2018 19:48:10 -0400 Received: by mail.bootlin.com (Postfix, from userid 110) id 33DDE206A7; Wed, 3 Oct 2018 18:58:54 +0200 (CEST) Received: from bbrezillon (91-160-177-164.subs.proxad.net [91.160.177.164]) by mail.bootlin.com (Postfix) with ESMTPSA id 7693920DD8; Wed, 3 Oct 2018 18:58:15 +0200 (CEST) Date: Wed, 3 Oct 2018 18:58:15 +0200 From: Boris Brezillon To: Ricardo Ribalda Delgado Cc: Zhouyang Jia , LKML , Marek Vasut , linux-mtd@lists.infradead.org, Richard Weinberger , Brian Norris , David Woodhouse Subject: Re: [PATCH v4 6/8] mtd: maps: gpio-addr-flash: Convert to gpiod Message-ID: <20181003185815.23b40832@bbrezillon> In-Reply-To: References: <20181001124351.31615-1-ricardo.ribalda@gmail.com> <20181001124351.31615-6-ricardo.ribalda@gmail.com> <20181003171114.51ab47b8@bbrezillon> <20181003171727.145e7e41@bbrezillon> X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Ricardo, On Wed, 3 Oct 2018 17:56:03 +0200 Ricardo Ribalda Delgado wrote: > Hi Boris > On Wed, Oct 3, 2018 at 5:17 PM Boris Brezillon > wrote: > > > > On Wed, 3 Oct 2018 17:11:14 +0200 > > Boris Brezillon wrote: > > > > > Hi Ricardo, > > > > > > On Mon, 1 Oct 2018 14:43:49 +0200 > > > Ricardo Ribalda Delgado wrote: > > > > > > > @@ -248,14 +252,19 @@ static int gpio_flash_probe(struct platform_device *pdev) > > > > > > > > i = 0; > > > > do { > > > > - if (devm_gpio_request(&pdev->dev, state->gpio_addrs[i], > > > > - DRIVER_NAME)) { > > > > + unsigned int *gpio_id = (unsigned int *)gpios->start; > > > > + > > > > + if (devm_gpio_request_one(&pdev->dev, gpio_id[i], GPIOD_OUT_LOW, > > > > + DRIVER_NAME)) { > > > > dev_err(&pdev->dev, "failed to request gpio %d\n", > > > > - state->gpio_addrs[i]); > > > > + gpio_id[i]); > > > > return -EBUSY; > > > > } > > > > - gpio_direction_output(state->gpio_addrs[i], 0); > > > > - } while (++i < state->gpio_count); > > > > + > > > > + state->gpios->desc[i] = gpio_to_desc(gpio_id[i]); > > > > + if (!state->gpios->desc[i]) > > > > + return -EINVAL; > > > > + } while (++i < state->gpios->ndescs); > > > > > > Actually, I was thinking about using devm_gpiod_get_array() here and > > > defining a gpio lookup table in the board file registering the device. > > > This way, adding support for DT based parsing is transparent. > > > > It's actually easier than I thought since no one is registering such a > > device, so all you have to do is call devm_gpiod_get_array() and have a > > struct gpio_descs pointer in struct async_state. > > That is what I do in patch 8/8 for DT based parsing. Well, yes, except you do it differently for the !DT case, while I'm suggesting to use the same patch for both DT and !DT. > > I am am doing the gpio_to_desc and other to maintain compatibility > with old platform board files (in and out tree). I do care about keeping in-tree users functional (which is why I suggested to declare gpio lookup tables in the first place), but keeping out-of-tree code functional is on a best-effort basis. If it breaks because we have to rework an internal API then that's not our fault. Actually, that's one of the reason we push people to upstream their code => their maintenance burden is greatly reduced once the code has reached mainline. > > I think is important to maintain that compatibility, but you decide ;) And my decision is, keep the code as simple as possible even if it breaks out of tree users. Regards, Boris