mbox series

[v2,0/3] i2c-xlp9xx: update i2c driver to handle I2C_M_RECV_LEN flag

Message ID 1507616876-17189-1-git-send-email-kamlakant.patel@cavium.com
Headers show
Series i2c-xlp9xx: update i2c driver to handle I2C_M_RECV_LEN flag | expand

Message

Kamlakant Patel Oct. 10, 2017, 6:27 a.m. UTC 
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(-)

Comments

Rafael J. Wysocki Oct. 10, 2017, 11:35 p.m. UTC | #1 
On Tue, Oct 10, 2017 at 8:27 AM, Kamlakant Patel
<kamlakant.patel@cavium.com> wrote:
> 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(-)

Hi Wolfram,

I'm assuming that this will go in via the i2c tree, so please let me
know if anything is needed from my side.

Thanks,
Rafael
Wolfram Sang Oct. 11, 2017, 7:06 a.m. UTC | #2 
On Wed, Oct 11, 2017 at 01:35:10AM +0200, Rafael J. Wysocki wrote:
> On Tue, Oct 10, 2017 at 8:27 AM, Kamlakant Patel
> <kamlakant.patel@cavium.com> wrote:
> > 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(-)
> 
> Hi Wolfram,
> 
> I'm assuming that this will go in via the i2c tree, so please let me
> know if anything is needed from my side.

An ack for patch 1 would be nice.
Rafael J. Wysocki Oct. 11, 2017, 1:09 p.m. UTC | #3 
On Wed, Oct 11, 2017 at 9:06 AM, Wolfram Sang <wsa@the-dreams.de> wrote:
> On Wed, Oct 11, 2017 at 01:35:10AM +0200, Rafael J. Wysocki wrote:
>> On Tue, Oct 10, 2017 at 8:27 AM, Kamlakant Patel
>> <kamlakant.patel@cavium.com> wrote:
>> > 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(-)
>>
>> Hi Wolfram,
>>
>> I'm assuming that this will go in via the i2c tree, so please let me
>> know if anything is needed from my side.
>
> An ack for patch 1 would be nice.

OK