From: Matthias Brugger <matthias.bgg@gmail.com>
To: Sean Wang <sean.wang@mediatek.com>
Cc: robh+dt@kernel.org, gregkh@linuxfoundation.org, jslaby@suse.com,
andriy.shevchenko@linux.intel.com, robert.jarzmik@free.fr,
arnd@arndb.de, p.zabel@pengutronix.de, joel@jms.id.au,
david@lechnology.com, jan.kiszka@siemens.com,
heikki.krogerus@linux.intel.com, hpeter@gmail.com,
vigneshr@ti.com, tthayer@opensource.altera.com,
devicetree@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 RESEND 1/2] dt-bindings: serial: 8250: Add MediaTek BTIF controller bindings
Date: Mon, 28 Aug 2017 08:21:20 +0300 [thread overview]
Message-ID: <13f6d052-0fad-e99f-2c87-6a98035787cf@gmail.com> (raw)
In-Reply-To: <1503862785.19230.76.camel@mtkswgap22>
On 08/27/2017 10:39 PM, Sean Wang wrote:
> On Sun, 2017-08-27 at 22:00 +0300, Matthias Brugger wrote:
>>
>> On 08/19/2017 09:06 PM, sean.wang@mediatek.com wrote:
>>> From: Sean Wang <sean.wang@mediatek.com>
>>>
>>> Document the devicetree bindings in 8250.txt for MediaTek BTIF
>>> controller which could be found on MT7622 and MT7623 SoC.
>>>
>>> Signed-off-by: Sean Wang <sean.wang@mediatek.com>
>>> ---
>>> Documentation/devicetree/bindings/serial/8250.txt | 3 +++
>>> 1 file changed, 3 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/serial/8250.txt b/Documentation/devicetree/bindings/serial/8250.txt
>>> index 419ff6c..7528d90 100644
>>> --- a/Documentation/devicetree/bindings/serial/8250.txt
>>> +++ b/Documentation/devicetree/bindings/serial/8250.txt
>>> @@ -14,6 +14,9 @@ Required properties:
>>> tegra132, or tegra210.
>>> - "nxp,lpc3220-uart"
>>> - "ralink,rt2880-uart"
>>> + - For MediaTek MT7623, must contain "mediatek,mt7623-btif"
>>> + - For other MediaTek SoCs , must contain "mediatek,<chip>-btif",
>>> + "mediatek,mt7623-btif" where <chip> is mt7622.
>>
>> Hm, to me that's confusing. What about:
>> "mediatek,mt7623-btif": for MediaTek MT7623
>> "mediatek,mt7622-btif", "mediatek,mt7623-btif": for MediaTek MT7622
>>
>> If in the future we have more SoCs that support the BTIF, we should add them
>> like the mt7622 case.
>>
>
> I had v3, but it should have similar logic and also got ack from Rob
>
> I knew all your logic of adding binding document for all MediaTek
> devices, even I alway added MediaTek device in dt-bindings as the way
> you mentioned here, but I felt this way is fine for this kind of
> dedicated document.
>
> The reason i don't add it as usual is the following. 8250.txt is common
> and shared among all uart like devices, so i don't want btif device
> occupies too much section and bloat the document when every new MediaTek
> SoC is introduced.
>
> So instead I refer to existing Nvidia device added in 8250.txt which I
> thought its way is simple, elegant and also using pattern I can use to
> add btif devices.
>
Working on my email backlog after vactions I didn't see that this was accepted
by Rob. Sorry for the noise.
Matthias
next prev parent reply other threads:[~2017-08-28 5:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 18:03 [PATCH v2 0/2] sean.wang
2017-08-19 18:03 ` [PATCH v2 1/2] dt-bindings: serial: 8250: Add MediaTek BTIF controller bindings sean.wang
2017-08-27 19:00 ` [PATCH v2 RESEND " Matthias Brugger
2017-08-27 19:39 ` Sean Wang
2017-08-28 5:21 ` Matthias Brugger [this message]
2017-08-19 18:03 ` [PATCH v2 2/2] serial: 8250: of: Add new port type for MediaTek BTIF controller on MT7622/23 SoC sean.wang
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=13f6d052-0fad-e99f-2c87-6a98035787cf@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=hpeter@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=joel@jms.id.au \
--cc=jslaby@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robert.jarzmik@free.fr \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=tthayer@opensource.altera.com \
--cc=vigneshr@ti.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
Powered by JetHome