From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-arm-kernel@lists.infradead.org,
Al Stone <al.stone@linaro.org>,
Jeff.Wu@amd.com, jcm@redhat.com, wsa@the-dreams.de,
rjw@rjwysocki.net, linux-i2c@vger.kernel.org,
linux-acpi@vger.kernel.org, patches@apm.com, "Duran,
Leo" <leo.duran@amd.com>, Loc Ho <lho@apm.com>,
"Hurwitz, Sherry" <sherry.hurwitz@amd.com>,
Hanjun Guo <hanjun.guo@linaro.org>,
Ken.Xue@amd.com, lenb@kernel.org
Subject: Re: [PATCH v2 0/2] i2c:dw: Add APM X-Gene ACPI I2C device support
Date: Tue, 15 Dec 2015 08:52:19 -0600 [thread overview]
Message-ID: <56702923.9010305@amd.com> (raw)
In-Reply-To: <20151215132721.GJ1762@lahna.fi.intel.com>
On 12/15/2015 07:27 AM, Mika Westerberg wrote:
> On Mon, Dec 14, 2015 at 06:53:25PM -0600, Suravee Suthikulanit wrote:
>> >I'm not sure if this has been discussed earlier. But after looking at the
>> >the acpi_apd driver, all we need is just the platform-specific input clock
>> >frequency value used by the drivers/i2c/busses/i2c-designware-core.c:
>> >i2c_dw_init() to calculate the values to program into the DW_IC_SS_SCL_HCNT
>> >and DW_IC_SS_SCL_LCNT registers.
> There is a way to pass *CNT values already from ACPI to the driver -- It
> looks for method called FMCN (or SSCN) and retrieves the values from
> there if found.
Right, I also noticed this afterward. By the way, are FMCN and SSCN
documented anywhere in the ACPI spec? I am trying to figure out how to
update the ACPI table to add this information for the AMD Seattle
(ARM64) platform, and I will also submit a patch to add the new HID for
this driver.
> The driver could be modified not to require clock if it already knows
> *CNT values.
>
Sounds good.
Thanks,
Suravee
next prev parent reply other threads:[~2015-12-15 14:52 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 [this message]
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
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=56702923.9010305@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=Jeff.Wu@amd.com \
--cc=Ken.Xue@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).