From: Florian Fainelli <f.fainelli@gmail.com>
To: bcm-kernel-feedback-list@broadcom.com,
Christian Lamparter <chunkeey@gmail.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Cc: "Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Matthew Hagan" <mnhagan88@gmail.com>
Subject: Re: [PATCH v1] ARM: BCM53016: MR32: convert to Broadcom iProc I2C Driver
Date: Mon, 15 Nov 2021 09:33:22 -0800 [thread overview]
Message-ID: <20211115173322.489465-1-f.fainelli@gmail.com> (raw)
In-Reply-To: <20211028070344.12652-1-chunkeey@gmail.com>
On Thu, 28 Oct 2021 09:03:44 +0200, Christian Lamparter <chunkeey@gmail.com> wrote:
> replaces the bit-banged i2c-gpio provided i2c functionality
> with the hardware in the SoC.
>
> During review of the MR32, Florian Fainelli pointed out that the
> SoC has a real I2C-controller. Furthermore, the connected pins
> (SDA and SCL) would line up perfectly for use. Back then I couldn't
> get it working though and I left it with i2c-gpio (which worked).
>
> Now we know the reason: the interrupt was incorrectly specified.
> (Hence, this patch depends on Florian Fainelli's
> "ARM: dts: BCM5301X: Fix I2C controller interrupt" patch).
>
> Cc: Florian Fainelli <f.fainelli@gmail.com>
> Cc: Rafał Miłecki <zajec5@gmail.com>
> Cc: Matthew Hagan <mnhagan88@gmail.com>
> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
> ---
Applied to https://github.com/Broadcom/stblinux/commits/devicetree/next, thanks!
--
Florian
prev parent reply other threads:[~2021-11-16 1:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 7:03 [PATCH v1] ARM: BCM53016: MR32: convert to Broadcom iProc I2C Driver Christian Lamparter
2021-11-15 17:33 ` 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=20211115173322.489465-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=chunkeey@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mnhagan88@gmail.com \
--cc=robh+dt@kernel.org \
--cc=zajec5@gmail.com \
/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).