From: Wolfram Sang <wsa@the-dreams.de>
To: Kamlakant Patel <kamlakant.patel@cavium.com>
Cc: linux-acpi@vger.kernel.org, linux-i2c@vger.kernel.org,
Jayachandran C <jnair@caviumnetworks.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH v2 1/3] ACPI / APD: Add clock frequency for ThunderX2 I2C controller
Date: Tue, 17 Oct 2017 23:54:44 +0200 [thread overview]
Message-ID: <20171017215444.ofbudbjyk7ne4sch@ninjato> (raw)
In-Reply-To: <1507616876-17189-2-git-send-email-kamlakant.patel@cavium.com>
[-- Attachment #1: Type: text/plain, Size: 456 bytes --]
On Tue, Oct 10, 2017 at 11:57:54AM +0530, Kamlakant Patel wrote:
> From: Jayachandran C <jnair@caviumnetworks.com>
>
> Add the input frequency of 125MHz for the ThunderX2 I2C controller block.
> The ACPI ID used is "CAV9007".
>
> Signed-off-by: Jayachandran C <jnair@caviumnetworks.com>
> Signed-off-by: Kamlakant Patel <kamlakant.patel@cavium.com>
> Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-17 21:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 6:27 [PATCH v2 0/3] i2c-xlp9xx: update i2c driver to handle I2C_M_RECV_LEN flag Kamlakant Patel
2017-10-10 6:27 ` [PATCH v2 1/3] ACPI / APD: Add clock frequency for ThunderX2 I2C controller Kamlakant Patel
2017-10-11 13:10 ` Rafael J. Wysocki
2017-10-17 21:54 ` Wolfram Sang [this message]
2017-10-10 6:27 ` [PATCH v2 2/3] i2c: xlp9xx: Get clock frequency with clk API Kamlakant Patel
2017-10-17 21:54 ` Wolfram Sang
2017-10-10 6:27 ` [PATCH v2 3/3] i2c: xlp9xx: Handle I2C_M_RECV_LEN in msg->flags Kamlakant Patel
2017-10-17 21:54 ` Wolfram Sang
2017-10-10 23:35 ` [PATCH v2 0/3] i2c-xlp9xx: update i2c driver to handle I2C_M_RECV_LEN flag Rafael J. Wysocki
2017-10-11 7:06 ` Wolfram Sang
2017-10-11 13:09 ` Rafael J. Wysocki
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=20171017215444.ofbudbjyk7ne4sch@ninjato \
--to=wsa@the-dreams.de \
--cc=jnair@caviumnetworks.com \
--cc=kamlakant.patel@cavium.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
/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