From: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: mika.westerberg@linux.intel.com, jarkko.nikula@linux.intel.com,
andriy.shevchenko@linux.intel.com, lho@apm.com, Ken.Xue@amd.com,
linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, "Hurwitz,
Sherry" <sherry.hurwitz@amd.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [PATCH v4] i2c: designware: Do not require clock when SSCN and FFCN are provided
Date: Wed, 13 Jan 2016 16:46:41 -0600 [thread overview]
Message-ID: <5696D3D1.2010509@amd.com> (raw)
In-Reply-To: <20160110083812.GE1526@katana>
On 1/10/2016 2:38 AM, Wolfram Sang wrote:
> On Mon, Jan 04, 2016 at 09:17:35AM -0600, Suravee Suthikulpanit wrote:
>> The current driver uses input clock source frequency to calculate
>> values for [SS|FS]_[HC|LC] registers. However, when booting ACPI, we do not
>> currently have a good way to provide the frequency information.
>> Instead, we can leverage the SSCN and FFCN ACPI methods, which can be used
>> to directly provide these values. So, the clock information should
>> no longer be required during probing.
>>
>> However, since clk can be invalid, additional checks must be done where
>> we are making use of it.
>>
>> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
>> Signed-off-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
>> Tested-by: Loc Ho <lho@apm.com>
>
> Applied to for-next, thanks! Also thanks to all reviewers and testers.
>
Thank you,
Suravee
WARNING: multiple messages have this Message-ID (diff)
From: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: <mika.westerberg@linux.intel.com>,
<jarkko.nikula@linux.intel.com>,
<andriy.shevchenko@linux.intel.com>, <lho@apm.com>,
<Ken.Xue@amd.com>, <linux-i2c@vger.kernel.org>,
<linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Hurwitz, Sherry" <sherry.hurwitz@amd.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [PATCH v4] i2c: designware: Do not require clock when SSCN and FFCN are provided
Date: Wed, 13 Jan 2016 16:46:41 -0600 [thread overview]
Message-ID: <5696D3D1.2010509@amd.com> (raw)
In-Reply-To: <20160110083812.GE1526@katana>
On 1/10/2016 2:38 AM, Wolfram Sang wrote:
> On Mon, Jan 04, 2016 at 09:17:35AM -0600, Suravee Suthikulpanit wrote:
>> The current driver uses input clock source frequency to calculate
>> values for [SS|FS]_[HC|LC] registers. However, when booting ACPI, we do not
>> currently have a good way to provide the frequency information.
>> Instead, we can leverage the SSCN and FFCN ACPI methods, which can be used
>> to directly provide these values. So, the clock information should
>> no longer be required during probing.
>>
>> However, since clk can be invalid, additional checks must be done where
>> we are making use of it.
>>
>> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
>> Signed-off-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
>> Tested-by: Loc Ho <lho@apm.com>
>
> Applied to for-next, thanks! Also thanks to all reviewers and testers.
>
Thank you,
Suravee
next prev parent reply other threads:[~2016-01-13 22:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 15:17 [PATCH v4] i2c: designware: Do not require clock when SSCN and FFCN are provided Suravee Suthikulpanit
2016-01-04 15:17 ` Suravee Suthikulpanit
2016-01-04 16:15 ` Wolfram Sang
2016-01-05 19:58 ` Loc Ho
2016-01-07 0:31 ` Loc Ho
2016-01-07 5:05 ` Suravee Suthikulpanit
2016-01-07 5:05 ` Suravee Suthikulpanit
2016-01-10 8:38 ` Wolfram Sang
2016-01-13 22:46 ` Suravee Suthikulanit [this message]
2016-01-13 22:46 ` Suravee Suthikulanit
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=5696D3D1.2010509@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=Ken.Xue@amd.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=lho@apm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=sherry.hurwitz@amd.com \
--cc=thomas.lendacky@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 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.