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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 9B166CCA479 for ; Thu, 7 Jul 2022 16:51:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=O5YtETeNp+sAFFrCL8WzW+wWCEAy0Mkg3uOskDtH3pQ=; b=x4ZtEPiRLfYYM6 WC/iNAAsOKkGFE7dRPKeV2u1qFXCr1A3oWTw4RsOVq0ZLWFpJTwW79wNvAJLrN/5xrH3h4WJhGxOV m8+Tt2D4kAXyeWohnr5txteqrpS78pUpr7dclSmJlm131+IzxIpBdYYeo1aST26EFk3X5pCRZmbqT yorxYhUdoXIVYdwqY57rarV0vSh5qcFiEkV6244eTTNR6FAWYRD2uJCQ5ScLobI/Oc0bJisZpNuhv CHgql5W7FPAHbuHZA0fB8iWGeGRAZxLKNK1iMh1y2Y8+HK1n1PyMgkFZ5u9ADINbW3UTVh/bIPbAa 3mqnrQG8wOvoBROC4xuw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1o9Uhh-00H4Wq-H3; Thu, 07 Jul 2022 16:50:13 +0000 Received: from vps0.lunn.ch ([185.16.172.187]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1o9Uhe-00H4Vn-TR for linux-arm-kernel@lists.infradead.org; Thu, 07 Jul 2022 16:50:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Transfer-Encoding:Content-Disposition: Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:From: Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Content-Disposition: In-Reply-To:References; bh=ICKmcbHRvrSyUczplI8Beeso0lINOUsmLC2dkDv7txo=; b=1W XLVkE4BimNam9FMNOjWyPAdSc/dGRpLNZ4NxYgKyHqxkskxphYQ9ZTIuTBlFn8t4LPg3Ot4MlkB65 +qIeMQ5wsdCaoLzzFFJWOMAI1wI5M3iUFe6ZWV8q1OZ+whh2xtALwjZak/wYIbz8cr7oafhgTfDCK yx0yc4ncLG1hx6U=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1o9UhU-009bFU-2G; Thu, 07 Jul 2022 18:50:00 +0200 Date: Thu, 7 Jul 2022 18:50:00 +0200 From: Andrew Lunn To: Marek =?iso-8859-1?Q?Beh=FAn?= Cc: Pali =?iso-8859-1?Q?Roh=E1r?= , Gregory Clement , Sebastian Hesselbarth , Rob Herring , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 00/11] ARM: dts: mvebu: Add definitions for PCIe legacy INTx interrupts Message-ID: References: <20220706183114.30783-1-pali@kernel.org> <20220707163818.620ccb95@dellmb> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20220707163818.620ccb95@dellmb> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220707_095010_989401_B8ADB5A7 X-CRM114-Status: GOOD ( 17.09 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Jul 07, 2022 at 04:38:18PM +0200, Marek Beh=FAn wrote: > On Wed, 6 Jul 2022 22:53:46 +0200 > Andrew Lunn wrote: > = > > On Wed, Jul 06, 2022 at 08:31:03PM +0200, Pali Roh=E1r wrote: > > > This patch series add definitions for PCIe legacy INTx interrupts into > > > every DTS file used by the pci-mvebu.c controller driver. = > > = > > What you fail to explain in the commit message is Why? > > = > > Andrew > = > Hi Andrew, > = > this is required for example in a scenario where a driver requests only > one of the legacy interrupts (INTA). Without this change, the driver > would be notified on events on all 4 (INTA, INTB, INTC, INTD), even if > it requested only one of them. O.K, so please add that to the commit message. Is this purely theoretical, or are there known broken platforms out there? Should a subset of these patches be added to stable? Andrew _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel 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 0CC50CCA47F for ; Thu, 7 Jul 2022 16:50:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236180AbiGGQuQ (ORCPT ); Thu, 7 Jul 2022 12:50:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58656 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236110AbiGGQuP (ORCPT ); Thu, 7 Jul 2022 12:50:15 -0400 Received: from vps0.lunn.ch (vps0.lunn.ch [185.16.172.187]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 49D202A422; Thu, 7 Jul 2022 09:50:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Transfer-Encoding:Content-Disposition: Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:From: Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Content-Disposition: In-Reply-To:References; bh=ICKmcbHRvrSyUczplI8Beeso0lINOUsmLC2dkDv7txo=; b=1W XLVkE4BimNam9FMNOjWyPAdSc/dGRpLNZ4NxYgKyHqxkskxphYQ9ZTIuTBlFn8t4LPg3Ot4MlkB65 +qIeMQ5wsdCaoLzzFFJWOMAI1wI5M3iUFe6ZWV8q1OZ+whh2xtALwjZak/wYIbz8cr7oafhgTfDCK yx0yc4ncLG1hx6U=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1o9UhU-009bFU-2G; Thu, 07 Jul 2022 18:50:00 +0200 Date: Thu, 7 Jul 2022 18:50:00 +0200 From: Andrew Lunn To: Marek =?iso-8859-1?Q?Beh=FAn?= Cc: Pali =?iso-8859-1?Q?Roh=E1r?= , Gregory Clement , Sebastian Hesselbarth , Rob Herring , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 00/11] ARM: dts: mvebu: Add definitions for PCIe legacy INTx interrupts Message-ID: References: <20220706183114.30783-1-pali@kernel.org> <20220707163818.620ccb95@dellmb> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220707163818.620ccb95@dellmb> Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Thu, Jul 07, 2022 at 04:38:18PM +0200, Marek Behún wrote: > On Wed, 6 Jul 2022 22:53:46 +0200 > Andrew Lunn wrote: > > > On Wed, Jul 06, 2022 at 08:31:03PM +0200, Pali Rohár wrote: > > > This patch series add definitions for PCIe legacy INTx interrupts into > > > every DTS file used by the pci-mvebu.c controller driver. > > > > What you fail to explain in the commit message is Why? > > > > Andrew > > Hi Andrew, > > this is required for example in a scenario where a driver requests only > one of the legacy interrupts (INTA). Without this change, the driver > would be notified on events on all 4 (INTA, INTB, INTC, INTD), even if > it requested only one of them. O.K, so please add that to the commit message. Is this purely theoretical, or are there known broken platforms out there? Should a subset of these patches be added to stable? Andrew