All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Wolfram Sang <wsa@the-dreams.de>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	linux-i2c <linux-i2c@vger.kernel.org>,
	Devicetree List <devicetree@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Jassi Brar <jassisinghbrar@gmail.com>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH v5 0/2] add support for Socionext SynQuacer I2C controller
Date: Wed, 21 Mar 2018 09:48:02 +0800	[thread overview]
Message-ID: <CAKv+Gu-SEYwM1CF3-9YPVK4xNMy8hUt=JNTCA4GbP5j1Ts3_2w@mail.gmail.com> (raw)
In-Reply-To: <CAKv+Gu-7MP9OqsQpR+AKzn=yHTH5qv5pa4THy0X5JGr-O+XLDg@mail.gmail.com>

On 17 March 2018 at 00:19, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> On 10 March 2018 at 15:01, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>> On 2 March 2018 at 08:31, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>>> Add a binding and a driver for the I2C IP found in the Socionext SynQuacer
>>> SoC, which is essentially a rebranded version of the Fujitsu F_I2C controller.
>>>
>>> I think this is good to go now. Wolfram?
>>>
>>
>> Ping?
>>
>
> Ping?
>

Hello Wolfram,

Do you intend to queue this for v4.17? Or are there any issues that
need to be addressed first?

Thanks,
Ard.


>>> v5:
>>> - add Rob's ack to #1
>>> - drop unnecessary 'platform_set_drvdata(pdev, NULL)' in remove path (#2)
>>>
>>> v4:
>>> - clarify binding that only a single interrupt specifier is expected (#1)
>>> - check return value of clk_prepare_enable() on probe path (#2)
>>> - add Andy's R-b to patch #2
>>>
>>> v3:
>>> - incorporate more of Andy's review comments (#2), especially regarding the
>>>   bus speed and clock source handling for ACPI
>>> - patch #1 unchanged.
>>>
>>> v2:
>>> - incorporate Andy's review comments (#2)
>>> - patch #1 unchanged.
>>>
>>> Ard Biesheuvel (2):
>>>   dt-bindings: i2c: add binding for Socionext SynQuacer I2C
>>>   i2c: add support for Socionext SynQuacer I2C controller
>>>
>>>  Documentation/devicetree/bindings/i2c/i2c-synquacer.txt |  29 +
>>>  drivers/i2c/busses/Kconfig                              |  10 +
>>>  drivers/i2c/busses/Makefile                             |   1 +
>>>  drivers/i2c/busses/i2c-synquacer.c                      | 791 ++++++++++++++++++++
>>>  4 files changed, 831 insertions(+)
>>>  create mode 100644 Documentation/devicetree/bindings/i2c/i2c-synquacer.txt
>>>  create mode 100644 drivers/i2c/busses/i2c-synquacer.c
>>>
>>> --
>>> 2.11.0
>>>

WARNING: multiple messages have this Message-ID (diff)
From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/2] add support for Socionext SynQuacer I2C controller
Date: Wed, 21 Mar 2018 09:48:02 +0800	[thread overview]
Message-ID: <CAKv+Gu-SEYwM1CF3-9YPVK4xNMy8hUt=JNTCA4GbP5j1Ts3_2w@mail.gmail.com> (raw)
In-Reply-To: <CAKv+Gu-7MP9OqsQpR+AKzn=yHTH5qv5pa4THy0X5JGr-O+XLDg@mail.gmail.com>

On 17 March 2018 at 00:19, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> On 10 March 2018 at 15:01, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>> On 2 March 2018 at 08:31, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>>> Add a binding and a driver for the I2C IP found in the Socionext SynQuacer
>>> SoC, which is essentially a rebranded version of the Fujitsu F_I2C controller.
>>>
>>> I think this is good to go now. Wolfram?
>>>
>>
>> Ping?
>>
>
> Ping?
>

Hello Wolfram,

Do you intend to queue this for v4.17? Or are there any issues that
need to be addressed first?

Thanks,
Ard.


>>> v5:
>>> - add Rob's ack to #1
>>> - drop unnecessary 'platform_set_drvdata(pdev, NULL)' in remove path (#2)
>>>
>>> v4:
>>> - clarify binding that only a single interrupt specifier is expected (#1)
>>> - check return value of clk_prepare_enable() on probe path (#2)
>>> - add Andy's R-b to patch #2
>>>
>>> v3:
>>> - incorporate more of Andy's review comments (#2), especially regarding the
>>>   bus speed and clock source handling for ACPI
>>> - patch #1 unchanged.
>>>
>>> v2:
>>> - incorporate Andy's review comments (#2)
>>> - patch #1 unchanged.
>>>
>>> Ard Biesheuvel (2):
>>>   dt-bindings: i2c: add binding for Socionext SynQuacer I2C
>>>   i2c: add support for Socionext SynQuacer I2C controller
>>>
>>>  Documentation/devicetree/bindings/i2c/i2c-synquacer.txt |  29 +
>>>  drivers/i2c/busses/Kconfig                              |  10 +
>>>  drivers/i2c/busses/Makefile                             |   1 +
>>>  drivers/i2c/busses/i2c-synquacer.c                      | 791 ++++++++++++++++++++
>>>  4 files changed, 831 insertions(+)
>>>  create mode 100644 Documentation/devicetree/bindings/i2c/i2c-synquacer.txt
>>>  create mode 100644 drivers/i2c/busses/i2c-synquacer.c
>>>
>>> --
>>> 2.11.0
>>>

  reply	other threads:[~2018-03-21  1:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-02  8:31 [PATCH v5 0/2] add support for Socionext SynQuacer I2C controller Ard Biesheuvel
2018-03-02  8:31 ` Ard Biesheuvel
2018-03-02  8:31 ` Ard Biesheuvel
2018-03-02  8:31 ` [PATCH v5 1/2] dt-bindings: i2c: add binding for Socionext SynQuacer I2C Ard Biesheuvel
2018-03-02  8:31   ` Ard Biesheuvel
2018-03-02  8:31 ` [PATCH v5 2/2] i2c: add support for Socionext SynQuacer I2C controller Ard Biesheuvel
2018-03-02  8:31   ` Ard Biesheuvel
2018-03-24 23:19   ` Wolfram Sang
2018-03-24 23:19     ` Wolfram Sang
2018-03-24 23:25     ` Wolfram Sang
2018-03-24 23:25       ` Wolfram Sang
2018-03-25 10:30     ` Ard Biesheuvel
2018-03-25 10:30       ` Ard Biesheuvel
2018-03-10 15:01 ` [PATCH v5 0/2] " Ard Biesheuvel
2018-03-10 15:01   ` Ard Biesheuvel
2018-03-16 16:19   ` Ard Biesheuvel
2018-03-16 16:19     ` Ard Biesheuvel
2018-03-21  1:48     ` Ard Biesheuvel [this message]
2018-03-21  1:48       ` Ard Biesheuvel

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='CAKv+Gu-SEYwM1CF3-9YPVK4xNMy8hUt=JNTCA4GbP5j1Ts3_2w@mail.gmail.com' \
    --to=ard.biesheuvel@linaro.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --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.