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=-1.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 295BEC2D0CD for ; Wed, 18 Dec 2019 11:49:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id F282C21582 for ; Wed, 18 Dec 2019 11:49:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576669760; bh=D0KfWFKQnsh0M2Jg4/pnIgGfmjwpAKhCm83TzxKKh54=; h=To:Subject:Date:From:Cc:In-Reply-To:References:List-ID:From; b=d6O2SdoqaF8fKBv2BZ9sdVyJ+CnH3Ey1XwRQ36xJbCcoylWDiNMQzNS+r88hdc4H1 uVDzFCNr6FNIdPY+syquezq16G9a87O4BI3Doe44esFommgi2JXDIYhIHNNittNB2y isFoWlLxKhKDGbrSJWo7Cke2kSVnnSlGnAYpZLFQ= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726921AbfLRLtT (ORCPT ); Wed, 18 Dec 2019 06:49:19 -0500 Received: from inca-roads.misterjones.org ([213.251.177.50]:41229 "EHLO inca-roads.misterjones.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726141AbfLRLtT (ORCPT ); Wed, 18 Dec 2019 06:49:19 -0500 Received: from www-data by cheepnis.misterjones.org with local (Exim 4.80) (envelope-from ) id 1ihXpI-0007MK-JJ; Wed, 18 Dec 2019 12:49:12 +0100 To: Joakim Zhang Subject: RE: [PATCH 1/3] dt-bindings/irq: add binding for NXP INTMUX interrupt multiplexer X-PHP-Originating-Script: 0:main.inc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Wed, 18 Dec 2019 11:49:12 +0000 From: Marc Zyngier Cc: , , , , , , "S.j. Wang" , , , dl-linux-imx , , , , Andy Duan , Aisheng Dong In-Reply-To: References: <1576653615-27954-1-git-send-email-qiangqing.zhang@nxp.com> <1576653615-27954-2-git-send-email-qiangqing.zhang@nxp.com> <254925e345493019c3e1e558b37e46f2@www.loen.fr> Message-ID: <796eb027cbecbdc9dbc01b417d196a44@www.loen.fr> X-Sender: maz@kernel.org User-Agent: Roundcube Webmail/0.7.2 X-SA-Exim-Connect-IP: X-SA-Exim-Rcpt-To: qiangqing.zhang@nxp.com, tglx@linutronix.de, jason@lakedaemon.net, robh+dt@kernel.org, mark.rutland@arm.com, shawnguo@kernel.org, s.hauer@pengutronix.de, shengjiu.wang@nxp.com, kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, fugang.duan@nxp.com, aisheng.dong@nxp.com X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on cheepnis.misterjones.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019-12-18 11:34, Joakim Zhang wrote: >> -----Original Message----- >> From: Joakim Zhang >> Sent: 2019年12月18日 18:22 >> To: Marc Zyngier >> Cc: tglx@linutronix.de; jason@lakedaemon.net; robh+dt@kernel.org; >> mark.rutland@arm.com; shawnguo@kernel.org; s.hauer@pengutronix.de; >> S.j. >> Wang ; kernel@pengutronix.de; >> festevam@gmail.com; dl-linux-imx ; >> linux-kernel@vger.kernel.org; devicetree@vger.kernel.org; >> linux-arm-kernel@lists.infradead.org; Andy Duan >> ; >> Aisheng Dong >> Subject: RE: [PATCH 1/3] dt-bindings/irq: add binding for NXP INTMUX >> interrupt >> multiplexer [...] >> > What I don't understand is how the interrupt descriptor can >> indicate >> > which channel it is multiplexed on. The driver doesn't makes this >> > clear either, and I strongly suspect that it was never tested with >> more than a >> single channel... >> >> Yes, to be frank, I tested with a signle channel, I will take this >> into >> consideration. Thanks. > Hi Marc, > > I tested channels from 1 to 8, and no issue found. > > We register irq handler with irq_set_chained_handler_and_data(), so > the interrupt descriptor could find the controller's private data, > and > channel index is one part of private data. > I think this can explain the interrupt descriptor how to indicate > which channel it is multiplexed. But that doesn't explain how the driver can find which channel a given interrupts is wired to. Nothing in your binding shows how you can extract the channel number from the interrupt descriptor. Nothing in the driver even *computes* a channel number. As far as I can see, you register a bunch of domains, all with the same OF node, so all your interrupts end-up with the same domain. Is it really what you expect? This driver looks terribly wrong. M. -- Jazz is not dead. It just smells funny...