Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp8008iob; Mon, 2 May 2022 10:36:48 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzsieAM2g2Sl5FnUncRfG6miLrKOR89S4hW7ExEiHl+Z1hjewpvRmhCXPMbV62nm/TV7HfO X-Received: by 2002:a17:90b:1894:b0:1dc:1028:aecb with SMTP id mn20-20020a17090b189400b001dc1028aecbmr281913pjb.106.1651513007968; Mon, 02 May 2022 10:36:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1651513007; cv=none; d=google.com; s=arc-20160816; b=sQbwo+/bWQuz4K8LwRtms/3PLZdXCuzCK+nM3j/qKBA/0UQxxn8Ng5p0OXH63LSlph wkYTKAExZBO3NCe8GinjwAsQmbdYt4mt5jJYJxprTAQPG4WMTzdx+V9QQKeMd5fpRFNs 04vhaJcmFWOAAPYnQGAHkv0oQOBXmcKsdSY7bVdcXd2l4C2f1yZpcrrSLfzt9Mi1dZEo Hb1nsdVFBMRBPimO1wIh6MDcBc+uSQYS8q+EIrRyQLjOWjEI361MZOS85ajI9bzu8ICv llD6b7H6ARtuEU+Wxg5wLF8vx4UzhY55XNRWl/MgX538doo3na+G791cDjMdEwTyCEag Dbeg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:subject:cc:to:from:date:dkim-signature; bh=GB9a1W/6wIyZUk3ADi1jik1MJiLz1GoQmITB575jZOk=; b=JSOm8JguoXtjfEss8zK3Gm4cgfg/XHhS0gpgIcc89UWkwXRLEZZNW0yGG4xrTZfyNM I2TfB86nYeWBhgmuXRpzAzn549St+8FnOzSIDFFMKiT9oCztJQEwWAIboh5SMNUTflT0 Yncg1W2JALA/ZQlj/4kM8uwnbDHpKfw2vjXtZqJ891ysREn3f7nduu3UJrh4Sy9pfizW xACvp9Gc7j36dNOe5NtVA+DaAxEGZ333gV1v7tB5uDoD2PFzrAD1cARkAALKGs0nptan S4UR/J1xX4tQwpj7poCT9mUcqvgUd6+z1ApNkvn4jlWyS/6vR+BePrg3EKobLa1UXJOK teBA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=A1qsWe1Z; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id oa1-20020a17090b1bc100b001ca9946de5dsi14892659pjb.56.2022.05.02.10.36.07; Mon, 02 May 2022 10:36:47 -0700 (PDT) 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=@kernel.org header.s=k20201202 header.b=A1qsWe1Z; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1359335AbiEBIZS (ORCPT + 99 others); Mon, 2 May 2022 04:25:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39734 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1359278AbiEBIZQ (ORCPT ); Mon, 2 May 2022 04:25:16 -0400 Received: from sin.source.kernel.org (sin.source.kernel.org [IPv6:2604:1380:40e1:4800::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0F33440A2C for ; Mon, 2 May 2022 01:21:45 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sin.source.kernel.org (Postfix) with ESMTPS id 5DF8ECE17C8 for ; Mon, 2 May 2022 08:21:44 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3817AC385A4; Mon, 2 May 2022 08:21:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1651479702; bh=DO14eca36/8x8DjDJdsA4uwFGc1SVhaWvo9PYVUd8XY=; h=Date:From:To:Cc:Subject:From; b=A1qsWe1ZePTa1hFfNqFpyfe+uDovYVrObUOPp0E9EnPjbNt7toS/j1Mm1Zc5D/K1X iisfsULu30schurBChEpNXnfYwvjJcyBndBTKH8PUpcHESVguc+L0EbAqRTIYsRFq4 49xdPbJtdD4vKasyUlWCaWxYh7FucXtR7l2aqt2Z9Cu5iDL4zzae1UUcBDUqDj7QmR 1SGtRinvzDUWhXs4N4JVdl9wGOrS8v49MyeEuss6PqaVo2RNviJMVuTzbqnjHIjj/x hmoISSgtEE8mJH1+nFjcwnO3XbjOY6WMempkByZH6j89q7TsGfobBJTMkTeKxvrAqZ gD3wlcoyrENOw== Date: Mon, 2 May 2022 10:21:37 +0200 From: Marek =?UTF-8?B?QmVow7pu?= To: Marc Zyngier Cc: linux-kernel@vger.kernel.org, Thomas Gleixner , pali@kernel.org Subject: irqdomain API: how to set affinity of parent irq of chained irqs? Message-ID: <20220502102137.764606ee@thinkpad> X-Mailer: Claws Mail 3.18.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-7.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham 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 Dear Marc, Thomas, we have encountered the following problem that can hopefully be put some light onto: What is the intended way to set affinity (and possibly other irq attributes) of parent IRQ of chained IRQs, when using the irqdomain API? We are working on a driver that - registers an irqchip and adds an irqdomain - calls irq_set_chained_handler_and_data(parent_irq, handler) where handler triggers handling of child IRQs - but since parent_irq isn't requested for with request_thread_irq(), it does not show up in proc/sysfs, only in debugfs - the HW does not support setting affinity for the chained IRQs, only the parent (which comes from a GIC chip) The problem is that he parent IRQ, as mentioned in the third point, does not show up in proc/sysfs. Is there some precedent for this? Thank you. Marek