From: Wolfram Sang <wsa@the-dreams.de>
To: qii.wang@mediatek.com
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
srv_heupstream@mediatek.com, leilk.liu@mediatek.com,
ryder.lee@mediatek.com
Subject: Re: [PATCH 4/5] dt-bindings: i2c: Add Mediatek MT8183 i2c binding
Date: Tue, 11 Dec 2018 21:29:31 +0100 [thread overview]
Message-ID: <20181211202931.xav4gzi7rzh2scgx@ninjato> (raw)
In-Reply-To: <1543843974-4054-5-git-send-email-qii.wang@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 261 bytes --]
> + - ch-offset: base reg offset for multi-user.
What is "multi-user"? Why can't you add this offset to the reg-property
directly?
> + - mediatek,share-i3c: i3c controller can share i2c function.
Please explain in more detail? Is this an I3C controller?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-12-11 20:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 13:32 [PATCH 0/5] add i2c support for mt7629 and mt8183 qii.wang
2018-12-03 13:32 ` [PATCH 1/5] dt-bindings: i2c: Add Mediatek MT7629 i2c binding qii.wang
2018-12-04 20:19 ` Sean Wang
2018-12-11 6:28 ` mtk15107
2018-12-03 13:32 ` [PATCH 2/5] i2c: mediatek: remove useless code and replace definitions qii.wang
2018-12-04 20:37 ` Sean Wang
2018-12-11 20:20 ` Wolfram Sang
2018-12-13 9:13 ` Qii Wang
2018-12-03 13:32 ` [PATCH 3/5] i2c: mediatek: Add offsets array for new i2c registers qii.wang
2018-12-04 20:45 ` Sean Wang
2018-12-03 13:32 ` [PATCH 4/5] dt-bindings: i2c: Add Mediatek MT8183 i2c binding qii.wang
2018-12-04 20:59 ` Sean Wang
2018-12-11 20:29 ` Wolfram Sang [this message]
2018-12-13 9:32 ` Qii Wang
2018-12-17 23:06 ` Wolfram Sang
2018-12-18 2:35 ` Qii Wang
2018-12-03 13:32 ` [PATCH 5/5] i2c: mediatek: Add i2c compatible for MediaTek MT8183 qii.wang
2018-12-04 5:49 ` Sean Wang
2018-12-12 7:18 ` Qii 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=20181211202931.xav4gzi7rzh2scgx@ninjato \
--to=wsa@the-dreams.de \
--cc=devicetree@vger.kernel.org \
--cc=leilk.liu@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=qii.wang@mediatek.com \
--cc=ryder.lee@mediatek.com \
--cc=srv_heupstream@mediatek.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).