From: Kamlakant Patel <kamlakant.patel@cavium.com>
To: linux-acpi@vger.kernel.org, linux-i2c@vger.kernel.org
Cc: Kamlakant Patel <kamlakant.patel@cavium.com>,
Wolfram Sang <wsa@the-dreams.de>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: [PATCH v2 0/3] i2c-xlp9xx: update i2c driver to handle I2C_M_RECV_LEN flag
Date: Tue, 10 Oct 2017 11:57:53 +0530 [thread overview]
Message-ID: <1507616876-17189-1-git-send-email-kamlakant.patel@cavium.com> (raw)
This patch set has following changes:
* Use Linux clk APIs to get input clock frequency for the I2C controller.
* I2C driver update to handle I2C_M_RECV_LEN and I2C_CLIENT_PEC flags.
Changes since v1:
* Rebased to mainline(4.14-rc4).
* Removed unnecessary parens in i2c-xlp9xx.c.
Jayachandran C (2):
ACPI / APD: Add clock frequency for ThunderX2 I2C controller
i2c: xlp9xx: Get clock frequency with clk API
Kamlakant Patel (1):
i2c: xlp9xx: Handle I2C_M_RECV_LEN in msg->flags
drivers/acpi/acpi_apd.c | 5 +++++
drivers/i2c/busses/i2c-xlp9xx.c | 44 +++++++++++++++++++++++++++++++++++++----
2 files changed, 45 insertions(+), 4 deletions(-)
--
2.7.4
next reply other threads:[~2017-10-10 6:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 6:27 Kamlakant Patel [this message]
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
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=1507616876-17189-1-git-send-email-kamlakant.patel@cavium.com \
--to=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 \
--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).