From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9A5F01A5B84 for ; Sun, 22 Feb 2026 22:46:57 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771800417; cv=none; b=uulIIgzmnGMMbGFHkJXubFs5JFoI+tJJ/UnvI6udcPTZxjHejwlCXkmHKQ6ZSz7ktaEYsgFFWEJl+r4LYHeKCO6LWTiKiIjVwbKqvz9hfRQkOH10qIXTt7DalfMsDXBJ23EEpppq195AtBv+H6oXBRHPTidsTesrLUbuth+IedU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771800417; c=relaxed/simple; bh=emgHJ6xSqLSQy3OTD/07Iz1YleAxSnRmHyfr1+zjP7k=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=Vl7xRAtQ18IGB1cSfx8P9eXJKtjAE9DmVibleL7Dx0k/EZK/ikHw2ToKo0w3RNWIBgJyDguK7xyu7U2vL2n0XW3FeRQAH6DtBcKP0MyHwsRtT6ZMT7RuouU0FgYrhTVlCN2oqIQ9r4P8aiv1EGqHgw6mA+t1LoV/RDX6gd6cWzI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=kiMepc6O; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="kiMepc6O" Received: by smtp.kernel.org (Postfix) with ESMTPSA id AA5F1C116D0; Sun, 22 Feb 2026 22:46:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1771800417; bh=emgHJ6xSqLSQy3OTD/07Iz1YleAxSnRmHyfr1+zjP7k=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=kiMepc6Oa9en6RP71oTdCkyRlEoWJRGRXvTP1QkXrMjjuy3zulqJX6QUiVeP0UbRZ /iUiWGxsCVj03D7+xvI8utB3wmVyTxstMv34mrJ9qJfzqWbX2k/XUqn0Oz6x1g84cI XThhEtFt4F5KfDlPqaNhARt/7qRxgK9e9XArgP/eYDpCZUXwh4JuI1wWLkYrU3OTNM euXNdQ5x7xtU8k1pEdt8qSeKTttWpddmkNbJnNj5TJsCh3iqh62oMDr8cKbsLK6y7t 3ZiRBfjurB2WpUau+Dw/Vtu5v6IKT7H/M2Wqmrk1wQX5Kl1+CyXWEoMfJXK8qyQFGu qzkZMML7KlikQ== From: Thomas Gleixner To: Meghana Malladi , grzegorz.jaszczyk@linaro.org, maz@kernel.org, rogerq@ti.com, david@lechnology.com, afd@ti.com Cc: linux-kernel@vger.kernel.org, srk@ti.com, Vignesh Raghavendra , Roger Quadros , danishanwar@ti.com, m-malladi@ti.com, Grygorii Strashko , Suman Anna Subject: Re: [PATCH v2 2/3] irqchip/irq-pruss-intc: Fix listed IRQ type in /proc/interrupts In-Reply-To: <871picwgg4.ffs@tglx> References: <20260218093730.3123342-1-m-malladi@ti.com> <20260218093730.3123342-3-m-malladi@ti.com> <871picwgg4.ffs@tglx> Date: Sun, 22 Feb 2026 23:46:53 +0100 Message-ID: <87wm04v1k2.ffs@tglx> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Sun, Feb 22 2026 at 23:39, Thomas Gleixner wrote: > On Wed, Feb 18 2026 at 15:07, Meghana Malladi wrote: >> From: Grygorii Strashko >> >> The PRUSS INTC driver doesn't have .irq_set_type() callback implemented and >> supports only IRQ_TYPE_LEVEL_HIGH. This resulted in the IRQ properties not >> being updated properly and the PRUSS INTC IRQs were listed incorrectly in >> /proc/interrupts as Edge. > > That's again incomprehensible word salad. If the driver only supports > edge then obviously all interrupts belonging to this chip are marked > edge. How should they be listed? Oops. Sorry. I misread the IRQ_TYPE_LEVEL_HIGH as EDGE_HIGH. Need new glasses. Thomas