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=-23.6 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_CR_TRAILER,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_IN_DEF_DKIM_WL 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 7709EC433E0 for ; Thu, 7 Jan 2021 01:26:50 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 41FE92312A for ; Thu, 7 Jan 2021 01:26:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726498AbhAGB0t (ORCPT ); Wed, 6 Jan 2021 20:26:49 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47024 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726231AbhAGB0t (ORCPT ); Wed, 6 Jan 2021 20:26:49 -0500 Received: from mail-yb1-xb2c.google.com (mail-yb1-xb2c.google.com [IPv6:2607:f8b0:4864:20::b2c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0F644C0612EF for ; Wed, 6 Jan 2021 17:26:09 -0800 (PST) Received: by mail-yb1-xb2c.google.com with SMTP id y128so4618473ybf.10 for ; Wed, 06 Jan 2021 17:26:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+Q3ISD9lk+iyEMVjautQ2BP91e+OXNI/7EQGZw2zmBA=; b=kXTXHfEKQ73/mo9oyzafshtxpx+SFtovx9OgM9m53qzvmnTKW/UJrdSt9lXl5xeu+j K4U34rsRwU00ghxDMIXdtWuSqjInH6Fs6EpnlwptjPnPq8A9c8rCMZSefm10Zk0lPOGI DMtD9HUx/OIqFZHDkzAH1ymWYfT9ZhiXMwZZawRUCNy8CWe92DrPLSdyzuQrAb7fBgDL 2iQ8xstc0d/rfcbemElL5xwCWIqj7Ie9FPGythfjKpmOqweHcRHHO6ZJRabeTmDth/u4 b/eXeLKY4SblaTp5ljio5OxisckstSoJuf1BQkrecKpKnKjb8Y3mgqcRwIVdu+7nWkzo CqIw== 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=+Q3ISD9lk+iyEMVjautQ2BP91e+OXNI/7EQGZw2zmBA=; b=IfVdyUFbbRxA8LUrq9Ux6IXhcjn72rDGr/NdBMSek7FlVvE9ejBLnSH4gA8IvHVvuB y4WmWHHAyd2q0nyWxzCFHwYPsW+hxjNHZPBWlS8VLY04GkDunHxiJFb3t70bJRK6hR7D BGKNgZGopXcc48txscy3PxZfRHYzMWuk3J01Ez/aiuZrW/WbyF86DAjLBT3kycFTG5sK xLl+zr2MEg1wXZHMxm1ZCK38m/DOcY6TaYcMB3UmIWw7bWzXG0Fn0aNQeO0P+28/M0Jd PejNht/6ggJwUd0kHZSa16PATb8tcraNR0V25H4RNdZ0nQMAGzFmkAyJqumbFfZD2kSY qJeg== X-Gm-Message-State: AOAM5330UfU1pEJ6jLAXWIAi+2XD0IRtejl1Q/JOpRm3rvBr1LBQH7Qx x/zojLa7/a4qr8syLVuTU1NQbKW7Kd5u/AOvprTiOA== X-Google-Smtp-Source: ABdhPJxGvAuJ8UWOzecyVj/LYSXmdqjwby6wjLe+OCX4j8PTQ6cv0HsvKl+Mhj4jggRIlJvDTA8OQlk2j2zZAaylpiE= X-Received: by 2002:a25:6604:: with SMTP id a4mr10119739ybc.412.1609982768103; Wed, 06 Jan 2021 17:26:08 -0800 (PST) MIME-Version: 1.0 References: <20201218210750.3455872-1-saravanak@google.com> <2a6dbcc83d5aca7a3340e0cf4d751cdc@kernel.org> <20201231211240.GA2333246@robh.at.kernel.org> <877dovlgdl.wl-maz@kernel.org> In-Reply-To: From: Saravana Kannan Date: Wed, 6 Jan 2021 17:25:31 -0800 Message-ID: Subject: Re: [PATCH] of: property: Add device link support for interrupts To: Marc Zyngier Cc: Rob Herring , Greg Kroah-Hartman , Frank Rowand , Kevin Hilman , Android Kernel Team , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , LKML Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Wed, Jan 6, 2021 at 10:52 AM Saravana Kannan wrote: > > On Sat, Jan 2, 2021 at 3:37 AM Marc Zyngier wrote: > > > > On Thu, 31 Dec 2020 21:12:40 +0000, > > Rob Herring wrote: > > > > > > On Mon, Dec 21, 2020 at 09:30:45AM +0000, Marc Zyngier wrote: > > > > On 2020-12-18 21:07, Saravana Kannan wrote: > > > > > Add support for creating device links out of interrupts property. > > > > > > > > > > Cc: Marc Zyngier > > > > > Cc: Kevin Hilman > > > > > Signed-off-by: Saravana Kannan > > > > > --- > > > > > Rob/Greg, > > > > > > > > > > This might need to go into driver-core to avoid conflict > > > > > due to fw_devlink refactor series that merged there. > > > > > > > > > > Thanks, > > > > > Saravana > > > > > > > > > > > > > > > drivers/of/property.c | 17 +++++++++++++++++ > > > > > 1 file changed, 17 insertions(+) > > > > > > > > > > diff --git a/drivers/of/property.c b/drivers/of/property.c > > > > > index 5f9eed79a8aa..e56a5eae0a0b 100644 > > > > > --- a/drivers/of/property.c > > > > > +++ b/drivers/of/property.c > > > > > @@ -1271,6 +1271,22 @@ static struct device_node > > > > > *parse_iommu_maps(struct device_node *np, > > > > > return of_parse_phandle(np, prop_name, (index * 4) + 1); > > > > > } > > > > > > > > > > +static struct device_node *parse_interrupts(struct device_node *np, > > > > > + const char *prop_name, int index) > > > > > +{ > > > > > + struct device_node *sup; > > > > > + > > > > > + if (strcmp(prop_name, "interrupts") || index) > > > > > + return NULL; > > > > > + > > > > > + of_node_get(np); > > > > > + while (np && !(sup = of_parse_phandle(np, "interrupt-parent", 0))) > > > > > + np = of_get_next_parent(np); > > > > > + of_node_put(np); > > > > > + > > > > > + return sup; > > > > > +} > > > > > + > > > > > static const struct supplier_bindings of_supplier_bindings[] = { > > > > > { .parse_prop = parse_clocks, }, > > > > > { .parse_prop = parse_interconnects, }, > > > > > @@ -1296,6 +1312,7 @@ static const struct supplier_bindings > > > > > of_supplier_bindings[] = { > > > > > { .parse_prop = parse_pinctrl6, }, > > > > > { .parse_prop = parse_pinctrl7, }, > > > > > { .parse_prop = parse_pinctrl8, }, > > > > > + { .parse_prop = parse_interrupts, }, > > > > > { .parse_prop = parse_regulators, }, > > > > > { .parse_prop = parse_gpio, }, > > > > > { .parse_prop = parse_gpios, }, > > > > > > > > You don't really describe what this is for so I'm only guessing > > > > from the context. If you want to follow the interrupt hierarchy, > > > > "interrupt-parent" isn't enough. You also need to track > > > > things like interrupt-map, or anything that carries a phandle > > > > to an interrupt controller. > > > > > > We don't need to follow the hierarchy, we just need the immediate > > > dependencies. > > > > Indeed. I also wonder why this isn't just a irq_find_parent() call, TBH. > > Thanks Rob for explaining it. > > Marc, I wasn't sure if Rob would be okay with including of_irq.h here. > Also, I'm trying to keep of/property.c independent of the framework > code for now. The long term goal is to see if I can move out most of > this into the frameworks. But I want to do that after I sort of some > of the larger problems (like getting fw_devlink=on to work on all > devices first). Let me know if you have a strong preference for right > now, if not, I'd rather keep property.c independent for now. > > I wasn't aware of interrupt-map until a few weeks ago and didn't know > it carried phandles. I can add support for that too. There's no reason > for all of them to go in one patch though. Hmm... I looked at Documentation/devicetree/bindings/interrupt-controller/interrupts.txt and it has no documentation for interrupt-map. There's a bunch of references to it in device specific DT binding documentation but I don't want to rely on those for correctness. Marc, can you explain the interrupt-map format here or add documentation for it please? -Saravana