From: Stefan Roese <sr@denx.de>
To: Paul Burton <paul.burton@mips.com>
Cc: "linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
Harvey Hunt <harveyhuntnexus@gmail.com>,
John Crispin <john@phrozen.org>, Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH 5/8 v2] MIPS: ralink: mt7628a.dtsi: Add I2C controller DT node
Date: Wed, 29 May 2019 07:19:31 +0200 [thread overview]
Message-ID: <96f6564a-e45b-a082-4682-c81dde8d22d5@denx.de> (raw)
In-Reply-To: <20190528204119.g7kvutxcprhwo56d@pburton-laptop>
Hi Paul,
On 28.05.19 22:41, Paul Burton wrote:
> Hi Stefan,
>
> On Mon, May 27, 2019 at 11:13:20AM +0200, Stefan Roese wrote:
>> diff --git a/arch/mips/boot/dts/ralink/mt7628a.dtsi b/arch/mips/boot/dts/ralink/mt7628a.dtsi
>> index 0c2983c9c47c..64a425c7d639 100644
>> --- a/arch/mips/boot/dts/ralink/mt7628a.dtsi
>> +++ b/arch/mips/boot/dts/ralink/mt7628a.dtsi
>> @@ -170,6 +170,22 @@
>> interrupts = <6>;
>> };
>>
>> + i2c: i2c@900 {
>> + compatible = "mediatek,mt7621-i2c";
>> + reg = <0x900 0x100>;
>
> I don't see this compatible string listed under
> Documentation/devicetree/bindings, nor in
> drivers/i2c/busses/i2c-mt65xx.c which I presume is the driver that would
> handle it.
No, these is a different driver queued for this (old) SoC. I've submitted
it on the I2C list and am pretty hopeful, that it will hit next shortly:
https://patchwork.ozlabs.org/patch/1095794/
The bindings are included in this patch.
> I guess this needs driver changes to be applied before it'll actually do
> anything?
Correct.
> I'd prefer that at least the DT binding documentation goes in before we
> add the nodes to the DT.
I understand. I've added Wolfram to Cc to perhaps comment on this.
> If those changes are already queued up somewhere else could you point me
> at them?
Please see above.
Thanks,
Stefan
next prev parent reply other threads:[~2019-05-29 5:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 9:13 [PATCH 1/8 v2] MIPS: ralink: mt7628a.dtsi: Add SPDX GPL-2.0 license identifier Stefan Roese
2019-05-27 9:13 ` [PATCH 2/8 v2] MIPS: ralink: mt7628a.dtsi: Add pinmux DT node Stefan Roese
2019-06-24 21:16 ` Paul Burton
2019-05-27 9:13 ` [PATCH 3/8 v2] MIPS: ralink: mt7628a.dtsi: Add pinctrl DT properties to the UART nodes Stefan Roese
2019-06-24 21:16 ` Paul Burton
2019-05-27 9:13 ` [PATCH 4/8 v2] MIPS: ralink: mt7628a.dtsi: Add GPIO controller DT node Stefan Roese
2019-06-24 21:16 ` Paul Burton
2019-05-27 9:13 ` [PATCH 5/8 v2] MIPS: ralink: mt7628a.dtsi: Add I2C " Stefan Roese
2019-05-28 20:41 ` Paul Burton
2019-05-29 5:19 ` Stefan Roese [this message]
2019-06-24 21:24 ` Paul Burton
2019-06-24 22:07 ` Wolfram Sang
2019-06-29 9:07 ` Stefan Roese
2019-05-27 9:13 ` [PATCH 6/8 v2] MIPS: ralink: mt7628a.dtsi: Add SPI " Stefan Roese
2019-05-28 20:43 ` Paul Burton
2019-05-29 5:22 ` Stefan Roese
2019-06-24 21:16 ` Paul Burton
2019-05-27 9:13 ` [PATCH 7/8 v2] MIPS: ralink: mt7628a.dtsi: Add watchdog " Stefan Roese
2019-06-24 21:16 ` Paul Burton
2019-05-27 9:13 ` [PATCH 8/8 v2] MIPS: ralink: Add GARDENA smart Gateway MT7688 board Stefan Roese
2019-06-24 21:30 ` Paul Burton
2019-06-25 5:31 ` Stefan Roese
2019-06-24 21:16 ` [PATCH 1/8 v2] MIPS: ralink: mt7628a.dtsi: Add SPDX GPL-2.0 license identifier Paul Burton
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=96f6564a-e45b-a082-4682-c81dde8d22d5@denx.de \
--to=sr@denx.de \
--cc=harveyhuntnexus@gmail.com \
--cc=john@phrozen.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=wsa@the-dreams.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).