From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] ARM: mediatek: Add driver for Mediatek I2C controller
Date: Tue, 13 Jan 2015 10:57:26 +0100 [thread overview]
Message-ID: <20150113095725.GC1059@katana> (raw)
In-Reply-To: <20150106133753.GA3754@katana>
On Tue, Jan 06, 2015 at 02:37:53PM +0100, Wolfram Sang wrote:
>
> > We've started upstream work for MT8173[1].
> >
> > We've fixed these issues for new SoC, and we believe it is fully I2C
> > compatible now. We'll add mt8173 support to this driver, so this driver
> > will support both fully I2C compatible SoC and the current one.
>
> From what you tell, I'd rather add the MT8173 support incrementally.
> Let's get first the limited support properly implemented, then add
> another controller.
>
> I'll send out my draft for describing the quirks later today.
What do you think about my two proposals?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150113/a96017f0/attachment.sig>
next prev parent reply other threads:[~2015-01-13 9:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 9:38 [PATCH v3 0/2] ARM: mediatek: Add driver for Mediatek I2C controller Xudong Chen
2014-11-24 9:38 ` [PATCH v3 1/2] dt-bindings: Add I2C bindings for mt65xx/mt81xx Xudong Chen
2014-11-24 9:38 ` [PATCH v3 2/2] I2C: mediatek: Add driver for MediaTek I2C controller Xudong Chen
2014-11-24 12:15 ` [PATCH v3 0/2] ARM: mediatek: Add driver for Mediatek " Wolfram Sang
2014-11-27 14:00 ` Yingjoe Chen
2014-11-27 16:45 ` Wolfram Sang
2014-12-12 2:40 ` Yingjoe Chen
2015-01-06 13:37 ` Wolfram Sang
2015-01-13 9:57 ` Wolfram Sang [this message]
2015-01-13 15:15 ` Yingjoe Chen
2015-01-13 15:23 ` Wolfram Sang
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=20150113095725.GC1059@katana \
--to=wsa@the-dreams.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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).