Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp324831rwb; Wed, 16 Nov 2022 00:50:49 -0800 (PST) X-Google-Smtp-Source: AA0mqf6t5t9BqWaRFmpppy9WfJ3vg/45QvRNUy7EyeCCx/owxRlWTmstCQQTQtVx06nIeMhOmidA X-Received: by 2002:a17:90a:ba13:b0:218:5854:4dbd with SMTP id s19-20020a17090aba1300b0021858544dbdmr2654198pjr.59.1668588649286; Wed, 16 Nov 2022 00:50:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1668588649; cv=none; d=google.com; s=arc-20160816; b=cB3k+sxLrsZ+oHCA70NZUOaupflkshfXsxrATJeUackD/PMr7aLWNb+TSzyoJMs6o2 9jdN4M2Mg+p4MHjM3HvkMeMo5DgoBQGAPunZpQp9nbnOUwX8MQawlUWvcyvRcQtCZynQ aY20+XCNJi7YAg6WwWoPujJ8v0RPiamNsYl+7+rKxTyLgPibc5pLh2mEVbpyT8BamsJ5 73f4NxlvJCBB1xSEnQFJRdjozANqDzNPodN2cBK1B8r0E8dsC0B/+NGCAW/+M6c91VS2 RVjP+vPMCgv4w1nd59XSiwhO6WbdiDNEhBzNjLBBS5yG9zsK1j3YFS9NSTPi1qrgr592 I4yA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=7E52UgeDgBikPUyfmAXqV0RNh0nggToZg8ivIyzthVA=; b=uMLM4nYjHd/65nFMirRznP1URl5v1p2zycrD6auTO7OR9acLuHo32P4a+OQIFUtcZL 3pps7woGBgvePkVgigg7IzOZMF4aEYKGcBmYB09vJTz5szS5MEEncrYK7Lusbnk5kJbA IBrgZ3u/ObSjiCjsPlo+acW8WRn/98aULwekpB/tSSCCsvZ4t5dZPhGwWuS66MgzVyXu yHcAhP4un+7l5jHSeZf/d6FJCNPhtYHY06b65gt2s7Frt+vDJvGp4+2lGhdBUYaUMbLv OWopaJiP0ZJNvnVx+r8a61RxptI8gbP6pMBDEBSfgpIRBWPiAQFs3iwQ4oY0o3eBUCnB cgdA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@bgdev-pl.20210112.gappssmtp.com header.s=20210112 header.b=fIxw4CQj; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id t186-20020a6381c3000000b0043a20d3388esi14891614pgd.321.2022.11.16.00.50.37; Wed, 16 Nov 2022 00:50:49 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@bgdev-pl.20210112.gappssmtp.com header.s=20210112 header.b=fIxw4CQj; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238894AbiKPIcQ (ORCPT + 91 others); Wed, 16 Nov 2022 03:32:16 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34166 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238888AbiKPIbl (ORCPT ); Wed, 16 Nov 2022 03:31:41 -0500 Received: from mail-vs1-xe2d.google.com (mail-vs1-xe2d.google.com [IPv6:2607:f8b0:4864:20::e2d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B0B77CE02 for ; Wed, 16 Nov 2022 00:29:00 -0800 (PST) Received: by mail-vs1-xe2d.google.com with SMTP id m4so10390702vsc.6 for ; Wed, 16 Nov 2022 00:29:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bgdev-pl.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=7E52UgeDgBikPUyfmAXqV0RNh0nggToZg8ivIyzthVA=; b=fIxw4CQjuXbD9t0Ku8I0WcARmlyxbRoGVQTjHYdJAupUtc9IeJf8bGZPN1AKuFJRn/ BH9YL5N6DK8wf+NAeGXXuNTJGWoccz0AYVi/WJdBnSMVsEREx8aj2mdKnVLqeSxlwYwB yPbjLXIoV5pgkJ/Q0phcyXY8QUtmoyPE3vWUIcuePsg+exQUzGkV2+QfYf7ZBmv5oB5Z 9/s7mU1pX+XF9fpp1pAOgwApPEmDn1W+cIthagPP8olWiFtKnQ25D5T9C68ilWgz/s6a UtNqbuKBHPRZnKtTWJzRoU7qvmQHoy9y2XZ3EuSbXLlUn+wudSbWc4donrCj77YE5Ns2 9ZpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=7E52UgeDgBikPUyfmAXqV0RNh0nggToZg8ivIyzthVA=; b=kBzaTjtZqNLl+GP4c6ZqBDzN2NFZ0UPdF+o9AA0XTUdf3teqi3pZNRqD0hu/unK3og 7IJyjrTYJT9syL9M8ZnovLshxcPHUKy1ZDjg2pekZO7h3383YBtC0nxtWFXHG9iQlysG fCp0yJPl0nPbpGWQwfjyCNDpgWbLUBY3EkNLEC6v8pXPV+87ZAOlmPgwXT8rKAqS5EiM w6Sa/SIdi9axAQy0mn0rMC8Pdu9uDusiFLVwtwKanUxaILD9Bv0td4COxAQftgwQdsM/ 4QEaWBt6j6qwgJDQ1iARAsh6aC8b2l0sr/M+uVUVYbVrW0uQvx8Nl6KnBmWT4wWLkeza 3t7g== X-Gm-Message-State: ANoB5pkrcljjYrKzGQIt+wd6CsA/Ywm+HFMMOOVzorelnRznB53K3IeC 83hbd20Djv9p1DyLNvczx8QIsJXCU98XoCxFaXylSg== X-Received: by 2002:a67:ce13:0:b0:3a7:769c:6dee with SMTP id s19-20020a67ce13000000b003a7769c6deemr11443047vsl.13.1668587339861; Wed, 16 Nov 2022 00:28:59 -0800 (PST) MIME-Version: 1.0 References: <20221116065335.8823-1-zhuyinbo@loongson.cn> <88f8d4b3-b144-4d04-a2bc-61ee30dd6ff6@app.fastmail.com> In-Reply-To: <88f8d4b3-b144-4d04-a2bc-61ee30dd6ff6@app.fastmail.com> From: Bartosz Golaszewski Date: Wed, 16 Nov 2022 09:28:49 +0100 Message-ID: Subject: Re: [PATCH v3 1/2] gpio: loongson: add dts/acpi gpio support To: Arnd Bergmann Cc: Yinbo Zhu , Linus Walleij , Rob Herring , Krzysztof Kozlowski , WANG Xuerui , Jiaxun Yang , Thomas Bogendoerfer , Juxin Gao , Bibo Mao , Yanteng Si , "open list:GPIO SUBSYSTEM" , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, loongarch@lists.linux.dev, linux-mips@vger.kernel.org, Arnaud Patard , Huacai Chen , Jianmin Lv , zhanghongchen , Liu Peibao Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 16, 2022 at 8:31 AM Arnd Bergmann wrote: > > On Wed, Nov 16, 2022, at 07:53, Yinbo Zhu wrote: > > The latest Loongson series platform use dts or acpi framework to > > register gpio device resources, such as the Loongson-2 series > > SoC of LOONGARCH architecture. In order to support dts, acpi and > > compatibility with previous platform device resources in driver, > > this patch was added. > > I think the support for legacy platform_data should be left out > of this patch. I am working on a series that removes unused > platform_data headers for machines that have DT support and no > longer use static platform_device declarations anywhere in > the kernel, so if you add another instance, that would just > get removed again in the near future. > > Just don't add it here. If there are users that use traditional > boardfiles instead of DT, they already need kernel patches to > add the board files, and adding in the driver support can be > part of the same patches. > To add to that: there's nothing in this platform data that can't be represented as static device properties in board files which actually makes it easier to use the upstreamed driver as is with out-of-tree platforms. Bartosz