From: Florian Fainelli <f.fainelli@gmail.com>
To: Ray Jui <ray.jui@broadcom.com>, Wolfram Sang <wsa@the-dreams.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>
Subject: Re: [PATCH v5 0/8] iProc I2C slave mode and NIC mode
Date: Fri, 22 Mar 2019 09:40:36 -0700 [thread overview]
Message-ID: <c06896b8-d3dc-2d3e-1d12-b2f2c2a09410@gmail.com> (raw)
In-Reply-To: <5c5ed177-0e9e-6271-518c-6956a7a6c554@broadcom.com>
On 2/22/19 12:04 PM, Ray Jui wrote:
> Hi Wolfram,
>
> Rob has reviewed all DT binding related changes from this patch series.
> Could you please help to review the I2C driver related changes when you
> have time?
Wolfram, did you queue those patches yet? The dt-binding patch has been
reviewed by Rob, therefore I am going to queue up patch 8 for the ARM
SoC pull request for 5.2. Let me know if that does not align with when
you plan on sending the i2c changes, thanks!
>
> Thanks,
>
> Ray
>
> On 2/14/2019 9:57 AM, Ray Jui wrote:
>> This patch series adds the following support to the iProc I2C driver:
>> - Increase maximum read transfer size to 255 bytes
>> - I2C slave mode
>> - Polling mode
>> - NIC I2C mode
>>
>> This patch series is based on kernel v5.0-rc3 and available at:
>> https://github.com/Broadcom/arm64-linux.git
>> branch: i2c-slave-v5
>>
>> Changes from v4:
>> - Add more detailed explanations in the device tree binding document
>> changes, to address Rob's review comments
>>
>> Changes from v3:
>> - Various minor fixes on commit messages and commits
>> - Rebased to v5.0-rc3
>>
>> Changes from v2:
>> - Address Ray's review comments.
>>
>> Changes from v1:
>> - Rebased to Linux v5.0.0-rc2
>>
>> Ray Jui (1):
>> dt-bindings: i2c: iproc: make 'interrupts' optional
>>
>> Rayagonda Kokatanur (5):
>> i2c: iproc: add polling support
>> i2c: iproc: use wrapper for read/write access
>> dt-bindings: i2c: iproc: add "brcm,iproc-nic-i2c" compatible string
>> i2c: iproc: add NIC I2C support
>> arm64: dts: Stingray: Add NIC i2c device node
>>
>> Shreesha Rajashekar (2):
>> i2c: iproc: Extend I2C read up to 255 bytes
>> i2c: iproc: Add slave mode support
>>
>> .../bindings/i2c/brcm,iproc-i2c.txt | 17 +-
>> .../boot/dts/broadcom/stingray/stingray.dtsi | 18 +
>> drivers/i2c/busses/Kconfig | 1 +
>> drivers/i2c/busses/i2c-bcm-iproc.c | 758 +++++++++++++++---
>> 4 files changed, 663 insertions(+), 131 deletions(-)
>>
--
Florian
next prev parent reply other threads:[~2019-03-22 16:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 17:57 [PATCH v5 0/8] iProc I2C slave mode and NIC mode Ray Jui
2019-02-14 17:57 ` [PATCH v5 1/8] i2c: iproc: Extend I2C read up to 255 bytes Ray Jui
2019-03-27 22:17 ` Wolfram Sang
2019-04-01 21:35 ` Ray Jui
2019-02-14 17:57 ` [PATCH v5 2/8] i2c: iproc: Add slave mode support Ray Jui
2019-03-27 22:14 ` Wolfram Sang
2019-03-27 22:41 ` Wolfram Sang
2019-04-01 21:33 ` Ray Jui
2019-04-02 8:24 ` Rayagonda Kokatanur
2019-04-02 9:01 ` Wolfram Sang
2019-02-14 17:57 ` [PATCH v5 3/8] dt-bindings: i2c: iproc: make 'interrupts' optional Ray Jui
2019-02-14 22:25 ` Rob Herring
2019-02-14 17:57 ` [PATCH v5 4/8] i2c: iproc: add polling support Ray Jui
2019-02-14 17:57 ` [PATCH v5 5/8] i2c: iproc: use wrapper for read/write access Ray Jui
2019-02-14 17:57 ` [PATCH v5 6/8] dt-bindings: i2c: iproc: add "brcm,iproc-nic-i2c" compatible string Ray Jui
2019-02-14 22:26 ` Rob Herring
2019-03-27 22:24 ` Wolfram Sang
2019-04-01 21:43 ` Ray Jui
2019-04-02 10:17 ` Wolfram Sang
2019-02-14 17:57 ` [PATCH v5 7/8] i2c: iproc: add NIC I2C support Ray Jui
2019-04-02 10:27 ` Wolfram Sang
2019-04-02 17:57 ` Ray Jui
2019-04-03 1:10 ` Ray Jui
2019-02-14 17:57 ` [PATCH v5 8/8] arm64: dts: Stingray: Add NIC i2c device node Ray Jui
2019-02-22 20:04 ` [PATCH v5 0/8] iProc I2C slave mode and NIC mode Ray Jui
2019-03-22 16:40 ` Florian Fainelli [this message]
2019-03-27 22:27 ` Wolfram Sang
2019-04-01 21:44 ` Ray Jui
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=c06896b8-d3dc-2d3e-1d12-b2f2c2a09410@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--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=ray.jui@broadcom.com \
--cc=rayagonda.kokatanur@broadcom.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 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).