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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 355DDC19F2D for ; Sat, 13 Aug 2022 11:57:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239284AbiHML5c (ORCPT ); Sat, 13 Aug 2022 07:57:32 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51348 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229719AbiHML5b (ORCPT ); Sat, 13 Aug 2022 07:57:31 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EE7892BB0C; Sat, 13 Aug 2022 04:57:30 -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 ams.source.kernel.org (Postfix) with ESMTPS id 5EEF1B80025; Sat, 13 Aug 2022 11:57:29 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0BE80C433C1; Sat, 13 Aug 2022 11:57:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1660391848; bh=kXrxgYD20mXl/zNB8s8zhxuWo31IQt1azVzBjNTDzWE=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=Cr/Sh05hkal2JjfmFNjVOoNWn5yXFAG2PzZ2rH+N9SmV97xYBgrxD2nGlcLtXH0vc yFuY3hY1hBA+zx3HoBHTEY5NEXwgQ3L+azhExkHz8x5kcNw5NKftSqh99235HVoiz4 J+6LqpxtgQqizRTfFbMnEbM9PyWiip4yYGCc6HQ6BqLmqLAGZaWPkF+XMkdq3j5FN8 CPDjLRtzxov8MNh50ettdZh9OREG2ieReIb+58gPR7Sc6ewU5LcUnAco7ur0vwb7Zv lU2EZMVEDoe/VQL5Vx07ew7q0pvGJKEMbX4fZ4McpNE2bHiuz7505AwRDMjGrF+ETV m3bxXmgobxI6Q== Received: from sofa.misterjones.org ([185.219.108.64] helo=wait-a-minute.misterjones.org) by disco-boy.misterjones.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1oMpld-002i67-Vn; Sat, 13 Aug 2022 12:57:26 +0100 Date: Sat, 13 Aug 2022 12:57:25 +0100 Message-ID: <874jygs6e2.wl-maz@kernel.org> From: Marc Zyngier To: Frank Li Cc: tglx@linutronix.de, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org, s.hauer@pengutronix.de, kw@linux.com, bhelgaas@google.com, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org, peng.fan@nxp.com, aisheng.dong@nxp.com, jdmason@kudzu.us, kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com, kishon@ti.com, lorenzo.pieralisi@arm.com, ntb@lists.linux.dev, lznuaa@gmail.com Subject: Re: [PATCH v4 2/4] irqchip: imx mu worked as msi controller In-Reply-To: <20220812215242.2255824-3-Frank.Li@nxp.com> References: <20220812215242.2255824-1-Frank.Li@nxp.com> <20220812215242.2255824-3-Frank.Li@nxp.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/27.1 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-SA-Exim-Connect-IP: 185.219.108.64 X-SA-Exim-Rcpt-To: Frank.Li@nxp.com, tglx@linutronix.de, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org, s.hauer@pengutronix.de, kw@linux.com, bhelgaas@google.com, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org, peng.fan@nxp.com, aisheng.dong@nxp.com, jdmason@kudzu.us, kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com, kishon@ti.com, lorenzo.pieralisi@arm.com, ntb@lists.linux.dev, lznuaa@gmail.com X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Fri, 12 Aug 2022 22:52:40 +0100, Frank Li wrote: > > MU support generate irq by write data to a register. > This patch make mu worked as msi controller. > So MU can do doorbell by using standard msi api. > > Signed-off-by: Frank Li May I add that it wouldn't hurt if you checked what addresses you send your patches to? For example, 'kernel@vger.kernel.org' doesn't exist (maybe you meant linux-kernel@...). I will not take patches that haven't been posted to LKML (and I shouldn't have reviewed it the first place). Thanks, M. -- Without deviation from the norm, progress is not possible.