From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>, Loc Ho <lho@apm.com>
Cc: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>,
wsa@the-dreams.de, Ken Xue <Ken.Xue@amd.com>,
Jeff.Wu@amd.com, rjw@rjwysocki.net, Len Brown <lenb@kernel.org>,
linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Jon Masters <jcm@redhat.com>, "patches@apm.com" <patches@apm.com>,
"Hurwitz, Sherry" <sherry.hurwitz@amd.com>,
"Duran, Leo" <leo.duran@amd.com>,
Hanjun Guo <hanjun.guo@linaro.org>,
Al Stone <al.stone@linaro.org>
Subject: Re: [PATCH v2 0/2] i2c:dw: Add APM X-Gene ACPI I2C device support
Date: Wed, 16 Dec 2015 14:53:02 +0200 [thread overview]
Message-ID: <56715EAE.4080006@linux.intel.com> (raw)
In-Reply-To: <20151216090454.GL1762@lahna.fi.intel.com>
On 12/16/2015 11:04 AM, Mika Westerberg wrote:
> On Tue, Dec 15, 2015 at 11:20:03AM -0800, Loc Ho wrote:
>> Can we not just add an AML method that will return the operation clock
>> frequency that the I2C driver can use? If the method doesn't existed,
>> we will just bail and do nothing or assume what ever default behavior?
>
> Why would you add yet another method? There already are existing ACPI
> *CNT methods that you can use, and are used in systems out there.
One thing to remember that *CNT methods allow more precise machine and
per bus specific tunings against different HW characteristics like
pull-up resistance, line load, propagation delay, etc.
--
Jarkko
next prev parent reply other threads:[~2015-12-16 12:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 21:19 [PATCH v2 0/2] i2c:dw: Add APM X-Gene ACPI I2C device support Loc Ho
2015-12-10 21:19 ` [PATCH v2 1/2] acpi:apd: " Loc Ho
2015-12-11 1:13 ` Ken Xue
2015-12-10 21:19 ` [PATCH v2 2/2] i2c:dw: " Loc Ho
2015-12-15 0:53 ` [PATCH v2 0/2] " Suravee Suthikulanit
2015-12-15 13:27 ` Mika Westerberg
2015-12-15 14:52 ` Suravee Suthikulpanit
2015-12-15 14:59 ` Mika Westerberg
2015-12-15 19:20 ` Loc Ho
2015-12-16 9:04 ` Mika Westerberg
2015-12-16 12:53 ` Jarkko Nikula [this message]
2015-12-23 9:34 ` Ken Xue
2015-12-23 9:52 ` Mika Westerberg
2015-12-23 9:59 ` Ken Xue
2015-12-23 10:17 ` Mika Westerberg
2015-12-23 10:02 ` Zheng, Ivan
2015-12-23 10:09 ` Mika Westerberg
2015-12-23 11:24 ` Zheng, Ivan
2015-12-23 11:40 ` Mika Westerberg
2016-01-04 9:09 ` Ben Dooks
2016-01-03 0:54 ` Rafael J. Wysocki
2016-01-04 6:23 ` Loc Ho
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=56715EAE.4080006@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=Jeff.Wu@amd.com \
--cc=Ken.Xue@amd.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=al.stone@linaro.org \
--cc=hanjun.guo@linaro.org \
--cc=jcm@redhat.com \
--cc=lenb@kernel.org \
--cc=leo.duran@amd.com \
--cc=lho@apm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=patches@apm.com \
--cc=rjw@rjwysocki.net \
--cc=sherry.hurwitz@amd.com \
--cc=wsa@the-dreams.de \
/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).