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=-3.9 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no 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 8D725C55179 for ; Thu, 29 Oct 2020 17:11:49 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 32CB720796 for ; Thu, 29 Oct 2020 17:11:49 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="Ntol3+ZC" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726081AbgJ2RLs (ORCPT ); Thu, 29 Oct 2020 13:11:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34300 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725777AbgJ2RLs (ORCPT ); Thu, 29 Oct 2020 13:11:48 -0400 Received: from mail-ed1-x543.google.com (mail-ed1-x543.google.com [IPv6:2a00:1450:4864:20::543]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 944B5C0613D3 for ; Thu, 29 Oct 2020 10:11:47 -0700 (PDT) Received: by mail-ed1-x543.google.com with SMTP id dg9so3769718edb.12 for ; Thu, 29 Oct 2020 10:11:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=B7msipSc39tbx1cyam8omVWWLfNOcLFksmzhLfw5XTU=; b=Ntol3+ZCQdnYkvEnnGcK6/sb2MP3E3Iv0WyuPD3TEh3RsyFIlLIbWDZPLenuJhseJd PRao5U88R1b15s775JvkBydB0C3Ppdz6is+tlkXlOebPD+eyL50aS0wNzhTUo169v2GH FG1+hXR3AtcxocCKOA4fK6FaCzKGdDkadP8IBZphfOoIU/MeFWs5d5Za6m9bVS4SccOP CPOhPlmn2ezvhyB0dsJaE9AJ//uH8fx6VRvUpqO/ElW/Oot9e2+yn+zA28ER8BstNHiI aLMTxPCcT7BHiZtxSHS2CuhsOF3BIPf45R17FPrLqGnfnktYM62YiABQ2gdQwI7JJZdU jscg== 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=B7msipSc39tbx1cyam8omVWWLfNOcLFksmzhLfw5XTU=; b=mA5OzvM0hHOL+XIBqXqQ4ma3TtEVxsPiROFyCTrjrO4O8UzbEr/GpKwg64lWMBv/fu k/afbd8UIYjvEEnLTzmwcHpzTsNju1+0WANUces2nZyi2srIhiEI4yd9Byi9aMFV3ur/ cSlfUHFtpHf6fYip0JsTBdiwS/8HzxomGM2e5G+pIm2kp9wu5Ow1E2SYouW4UmXL1shN sPiNUKz67T+IaMhF2lSf8sDcDUWeBl5LhP9MpSiK4QcrQRhP/4wbnhluEbScvsKUwUjE M+bqv3m/EEAnNM7hvTni3UsAkl2ZuQmhqMOCSr5Kgr95cvG9BISBuh49m8FL5esCDYyW mXXA== X-Gm-Message-State: AOAM530u3mpxb+0n+DK+4P+iX2JZXuIpaWYpjybMkKDyf1gw4nOBkds7 8cYXM/9nf3DlUORsEjJjoS7SA2iUZd27MQAoUij+0Q== X-Google-Smtp-Source: ABdhPJzaEhMJXsACQWDk9L0LSAaUdCxVgC3daLMdvGu6jdDQF2oJHrqIDTIma9G928K/x3q1Idovqlw76AnsZGHAmWE= X-Received: by 2002:a50:96d2:: with SMTP id z18mr3478714eda.367.1603991506282; Thu, 29 Oct 2020 10:11:46 -0700 (PDT) MIME-Version: 1.0 References: <20201004162908.3216898-1-martin.blumenstingl@googlemail.com> <20201004162908.3216898-3-martin.blumenstingl@googlemail.com> In-Reply-To: From: Linus Walleij Date: Thu, 29 Oct 2020 18:11:35 +0100 Message-ID: Subject: Re: [RFC PATCH 2/3] dt-bindings: gpio: Add binding documentation for Etron EJ168/EJ188/EJ198 To: Martin Blumenstingl Cc: Rob Herring , linux-pci , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "open list:GPIO SUBSYSTEM" , Bartosz Golaszewski , "linux-kernel@vger.kernel.org" , Bjorn Helgaas Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Fri, Oct 16, 2020 at 10:52 PM Martin Blumenstingl wrote: > On Wed, Oct 14, 2020 at 2:43 PM Rob Herring wrote: > > On Tue, Oct 13, 2020 at 8:27 AM Linus Walleij wrote: > > > I do not understand why a PCI device would need a DT binding > > > at all. They just probe from the magic number in the PCI > > > config space, they spawn struct pci_dev PCI devices, not the > > > type of platform devices coming out of the DT parser code. > > > No DT compatible needed. > > > > Same reason for all the discoverable buses need bindings. There can be > > parts that are not discoverable or connections with non-discoverable > > nodes. There's also cases where the discoverable device has to be > > powered, reset deasserted, clocks enabled, etc. first to be > > discovered. > > > > If the GPIOs here had connections elsewhere in the DT, then we have to > > describe the provider in DT. > > this is exactly what I need it for: that platform has hand-written > .dts files and I need to wire up a GPIO LED Aha I get it! OK then :) Yours, Linus Walleij