From: Florian Fainelli <f.fainelli@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
linux-arm-kernel@lists.infradead.org
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
maxime@cerno.tech, dave.stevenson@raspberrypi.com,
maz@kernel.org, open list <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org, eric@anholt.net,
Rob Herring <robh+dt@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org, tzimmermann@suse.de,
hverkuil-cisco@xs4all.nl, mchehab@kernel.org,
nsaenzjulienne@suse.de, linux-media@vger.kernel.org
Subject: Re: [PATCH] Revert "ARM: dts: bcm2711: Add the BSC interrupt controller"
Date: Tue, 16 Feb 2021 17:12:39 -0800 [thread overview]
Message-ID: <6ce9e820-992f-7f97-ccaa-f8cb99698a68@gmail.com> (raw)
In-Reply-To: <20210212191104.2365912-1-f.fainelli@gmail.com>
On 2/12/2021 11:11 AM, Florian Fainelli wrote:
> As Dave reported:
>
> This seems to have unintended side effects. GIC interrupt 117 is shared
> between the standard I2C controllers (i2c-bcm2835) and the l2-intc block
> handling the HDMI I2C interrupts.
>
> There is not a great way to share an interrupt between an interrupt
> controller using the chained IRQ handler which is an interrupt flow and
> another driver like i2c-bcm2835 which uses an interrupt handler
> (although it specifies IRQF_SHARED).
>
> Simply revert this change for now which will mean that HDMI I2C will be
> polled, like it was before.
>
> Reported-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Applied to devicetree/next, thanks!
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-02-17 1:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 19:11 [PATCH] Revert "ARM: dts: bcm2711: Add the BSC interrupt controller" Florian Fainelli
2021-02-16 7:55 ` Maxime Ripard
2021-02-16 17:13 ` Nicolas Saenz Julienne
2021-02-17 1:12 ` Florian Fainelli [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6ce9e820-992f-7f97-ccaa-f8cb99698a68@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=maxime@cerno.tech \
--cc=maz@kernel.org \
--cc=mchehab@kernel.org \
--cc=nsaenzjulienne@suse.de \
--cc=robh+dt@kernel.org \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).