From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: "Shah, Nehal-bakulchandra" <Nehal-bakulchandra.Shah@amd.com>
Cc: "linux-i2c-owner@vger.kernel.org"
<linux-i2c-owner@vger.kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
Ken Xue <Ken.Xue@amd.com>, Xiangliang Yu <Xiangliang.Yu@amd.com>,
Wang Hongcheng <annie.wang@amd.com>
Subject: Re: Question related i2c fixed clk rate
Date: Fri, 26 Aug 2016 14:29:14 +0300 [thread overview]
Message-ID: <64363513-96c8-9ace-131f-27fc176d146b@linux.intel.com> (raw)
In-Reply-To: <MWHPR12MB121624883C79696F1A248570A0ED0@MWHPR12MB1216.namprd12.prod.outlook.com>
Hi
+ Cc AMD contacts from acpi_apd.c changelog
On 08/25/2016 08:00 PM, Shah, Nehal-bakulchandra wrote:
> Hi,
> I am new to this. Appreciate your help for my query.
> I am working on updating i2c-designware clock rate for AMD upcoming platform. Here new 150000000 clk rate will be supported. I want to validate this but currently in our platform I do not have any i2c lines out. Is there any tool or way to check if this is getting setup properly.
> Basically I want to change
> .fixed_clk_rate = 133000000 to
> .fixed_clk_rate = 150000000 in acpi_apd.c file.
>
I guess what you want is to have a new static struct apd_device_desc
descriptor in drivers/acpi/acpi_apd.c and a new entry to
acpi_apd_device_ids[] for your new platform.
Something like what commits b790eb20b8e4 ("ACPI / APD: Add APM X-Gene
ACPI I2C device support") does.
--
Jarkko
prev parent reply other threads:[~2016-08-26 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 17:00 Question related i2c fixed clk rate Shah, Nehal-bakulchandra
2016-08-26 11:29 ` Jarkko Nikula [this message]
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=64363513-96c8-9ace-131f-27fc176d146b@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=Ken.Xue@amd.com \
--cc=Nehal-bakulchandra.Shah@amd.com \
--cc=Xiangliang.Yu@amd.com \
--cc=annie.wang@amd.com \
--cc=linux-i2c-owner@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
/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).