From: Wolfram Sang <wsa@the-dreams.de>
To: "Huang, Tao" <huangtao@rock-chips.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
"jianqun.xu" <jay.xu@rock-chips.com>,
wdc@rock-chips.com, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: rk3x: init module as subsys call
Date: Tue, 5 Jan 2016 11:01:10 +0100 [thread overview]
Message-ID: <20160105100110.GB1525@katana> (raw)
In-Reply-To: <568B837B.50607@rock-chips.com>
[-- Attachment #1: Type: text/plain, Size: 605 bytes --]
> > Tomeu from Collabora is working on some better scheme to optimize device
> > probing order but it looks like this may be a bit off still.
...
> I don't just talk about touch screen driver, most i2c device driver such
> as input sensor/camera/rtc/battery will suffer. So people will see their
> drivers do not work or slow down on rk3368 platform :(
I totally agree that the current situation is not ideal. This is why it
has to be *properly fixed* and not workarounded (which caused other side
effects in the past). If you care about it, then please help Tomeu with
his patchset.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-05 10:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 3:02 [PATCH] i2c: rk3x: init module as subsys call jianqun.xu
2016-01-05 7:02 ` Heiko Stuebner
2016-01-05 7:42 ` Huang, Tao
2016-01-05 8:00 ` Heiko Stuebner
2016-01-05 8:48 ` Huang, Tao
2016-01-05 10:01 ` Wolfram Sang [this message]
2016-01-05 7:42 ` Jianqun Xu
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=20160105100110.GB1525@katana \
--to=wsa@the-dreams.de \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=jay.xu@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=wdc@rock-chips.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).