From: Yingjoe Chen <yingjoe.chen@mediatek.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Liguo Zhang <Liguo.Zhang@mediatek.com>,
Xudong Chen <xudong.chen@mediatek.com>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@arm.linux.org.uk>,
Pawel Moll <pawel.moll@arm.com>, <srv_heupstream@mediatek.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Linus Walleij <linus.walleij@linaro.org>,
YH Chen <yh.chen@mediatek.com>, <linux-kernel@vger.kernel.org>,
Grant Likely <grant.likely@linaro.org>,
<devicetree@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
<linux-arm-kernel@lists.infradead.org>,
Sascha Hauer <kernel@pengutronix.de>,
Kumar Gala <galak@codeaurora.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Nathan Chung <nathan.chung@mediatek.com>,
Eddie Huang <eddie.huang@mediatek.com>,
Jean Delvare <jdelvare@suse.de>, <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] ARM: mediatek: Add driver for Mediatek I2C controller
Date: Fri, 12 Dec 2014 10:40:22 +0800 [thread overview]
Message-ID: <1418352022.4994.44.camel@mtksdaap41> (raw)
In-Reply-To: <20141127164536.GC5667@katana>
On Thu, 2014-11-27 at 17:45 +0100, Wolfram Sang wrote:
> > > I think there are now 3 drivers in my queue which are not fully I2C
> > > compatible but more supporting the very minimum to, say, read an eeprom.
> > > I am not feeling well to allow them to use I2C_FUNC_I2C. So, I want to
> > > think about ways how to communicate deficiencies like "only 255 byte" or
> > > "only WRRD messages" to users of that I2C controller. This is most
> > > likely not happening before 3.19. But assistance is very welcome.
Hi Wolfram,
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.
Joe.C
[1]
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-December/309847.html
WARNING: multiple messages have this Message-ID (diff)
From: Yingjoe Chen <yingjoe.chen@mediatek.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-i2c@vger.kernel.org, Jean Delvare <jdelvare@suse.de>,
Xudong Chen <xudong.chen@mediatek.com>,
Russell King <linux@arm.linux.org.uk>,
Arnd Bergmann <arnd@arndb.de>, YH Chen <yh.chen@mediatek.com>,
Liguo Zhang <Liguo.Zhang@mediatek.com>,
Nathan Chung <nathan.chung@mediatek.com>,
Grant Likely <grant.likely@linaro.org>,
devicetree@vger.kernel.org, Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Eddie Huang <eddie.huang@mediatek.com>,
linux-arm-kernel@lists.infradead.org,
srv_heupstream@mediatek.com, linux-kernel@vger.kernel.org,
Sascha Hauer <kernel@pengutronix.de>,
Kumar Gala <galak@codeaurora.org>
Subject: Re: [PATCH v3 0/2] ARM: mediatek: Add driver for Mediatek I2C controller
Date: Fri, 12 Dec 2014 10:40:22 +0800 [thread overview]
Message-ID: <1418352022.4994.44.camel@mtksdaap41> (raw)
In-Reply-To: <20141127164536.GC5667@katana>
On Thu, 2014-11-27 at 17:45 +0100, Wolfram Sang wrote:
> > > I think there are now 3 drivers in my queue which are not fully I2C
> > > compatible but more supporting the very minimum to, say, read an eeprom.
> > > I am not feeling well to allow them to use I2C_FUNC_I2C. So, I want to
> > > think about ways how to communicate deficiencies like "only 255 byte" or
> > > "only WRRD messages" to users of that I2C controller. This is most
> > > likely not happening before 3.19. But assistance is very welcome.
Hi Wolfram,
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.
Joe.C
[1]
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-December/309847.html
WARNING: multiple messages have this Message-ID (diff)
From: yingjoe.chen@mediatek.com (Yingjoe Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] ARM: mediatek: Add driver for Mediatek I2C controller
Date: Fri, 12 Dec 2014 10:40:22 +0800 [thread overview]
Message-ID: <1418352022.4994.44.camel@mtksdaap41> (raw)
In-Reply-To: <20141127164536.GC5667@katana>
On Thu, 2014-11-27 at 17:45 +0100, Wolfram Sang wrote:
> > > I think there are now 3 drivers in my queue which are not fully I2C
> > > compatible but more supporting the very minimum to, say, read an eeprom.
> > > I am not feeling well to allow them to use I2C_FUNC_I2C. So, I want to
> > > think about ways how to communicate deficiencies like "only 255 byte" or
> > > "only WRRD messages" to users of that I2C controller. This is most
> > > likely not happening before 3.19. But assistance is very welcome.
Hi Wolfram,
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.
Joe.C
[1]
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-December/309847.html
next prev parent reply other threads:[~2014-12-12 2:40 UTC|newest]
Thread overview: 32+ 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 ` Xudong Chen
2014-11-24 9:38 ` 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 ` Xudong Chen
2014-11-24 9:38 ` Xudong Chen
2014-11-24 9:38 ` [PATCH v3 2/2] I2C: mediatek: Add driver for MediaTek I2C controller Xudong Chen
2014-11-24 9:38 ` Xudong Chen
2014-11-24 9:38 ` Xudong Chen
2014-11-24 12:15 ` [PATCH v3 0/2] ARM: mediatek: Add driver for Mediatek " Wolfram Sang
2014-11-24 12:15 ` Wolfram Sang
2014-11-24 12:15 ` Wolfram Sang
2014-11-27 14:00 ` Yingjoe Chen
2014-11-27 14:00 ` Yingjoe Chen
2014-11-27 14:00 ` Yingjoe Chen
2014-11-27 16:45 ` Wolfram Sang
2014-11-27 16:45 ` Wolfram Sang
2014-11-27 16:45 ` Wolfram Sang
2014-12-12 2:40 ` Yingjoe Chen [this message]
2014-12-12 2:40 ` Yingjoe Chen
2014-12-12 2:40 ` Yingjoe Chen
2015-01-06 13:37 ` Wolfram Sang
2015-01-06 13:37 ` Wolfram Sang
2015-01-06 13:37 ` Wolfram Sang
2015-01-13 9:57 ` Wolfram Sang
2015-01-13 9:57 ` Wolfram Sang
2015-01-13 9:57 ` Wolfram Sang
2015-01-13 15:15 ` Yingjoe Chen
2015-01-13 15:15 ` Yingjoe Chen
2015-01-13 15:15 ` Yingjoe Chen
2015-01-13 15:23 ` Wolfram Sang
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=1418352022.4994.44.camel@mtksdaap41 \
--to=yingjoe.chen@mediatek.com \
--cc=Liguo.Zhang@mediatek.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=eddie.huang@mediatek.com \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jdelvare@suse.de \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=nathan.chung@mediatek.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=wsa@the-dreams.de \
--cc=xudong.chen@mediatek.com \
--cc=yh.chen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.