linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* Re: [PATCH 0/8] Add IPROC I2C slave mode and NIC I2C support
       [not found] <1546938997-13798-1-git-send-email-rayagonda.kokatanur@broadcom.com>
@ 2019-01-08 17:25 ` Ray Jui
       [not found]   ` <CAHO=5PG3NnYqoSyZ9u9kN1m7KagtKv275tpWj6s8NXvzhj52fQ@mail.gmail.com>
  0 siblings, 1 reply; 2+ messages in thread
From: Ray Jui @ 2019-01-08 17:25 UTC (permalink / raw)
  To: Rayagonda Kokatanur, Ray Jui, Scott Branden, Shreesha Rajashekar,
	Michael Cheng, linux-i2c, linux-arm-kernel, linux-kernel,
	bcm-kernel-feedback-list

You sent out the same patch series 3 times without any explanation. Very
confusing.

Is this the latest one that should be reviewed?

Thanks,

Ray

On 1/8/2019 1:16 AM, Rayagonda Kokatanur wrote:
> Hi,
> This patchset contains support for IPROC I2C slave and NIC I2C support.
> Following are the brief changes done inorder to support both IPROC I2C
> slave mode and NIC I2C,
> 
> a. Add support to allow I2C rx transfer upto 255 bytes
> b. Add polling mode support to the iProc I2C driver. Polling mode is used
>    in certain SoCs where interrupt is not connected from the I2C block.
> c. Add warpper read/write access for register to support indirect register
>    access. This is required in certain SoCs with this iProc I2C
>    block registered.
> 
> 
> 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: I2C read up to 255 bytes support
>   i2c: iproc: Add Slave mode support
> 
>  .../devicetree/bindings/i2c/brcm,iproc-i2c.txt     |  14 +-
>  .../arm64/boot/dts/broadcom/stingray/stingray.dtsi |  18 +
>  drivers/i2c/busses/Kconfig                         |   1 +
>  drivers/i2c/busses/i2c-bcm-iproc.c                 | 767 +++++++++++++++++----
>  4 files changed, 669 insertions(+), 131 deletions(-)
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PATCH 0/8] Add IPROC I2C slave mode and NIC I2C support
       [not found]   ` <CAHO=5PG3NnYqoSyZ9u9kN1m7KagtKv275tpWj6s8NXvzhj52fQ@mail.gmail.com>
@ 2019-01-09 18:27     ` Ray Jui
  0 siblings, 0 replies; 2+ messages in thread
From: Ray Jui @ 2019-01-09 18:27 UTC (permalink / raw)
  To: Rayagonda Kokatanur
  Cc: Scott Branden, Ray Jui, linux-kernel, Shreesha Rajashekar,
	bcm-kernel-feedback-list, linux-i2c, Michael Cheng,
	linux-arm-kernel

Okay. Just noticed another thing. May I ask if you ran the
'get_maintaimner.pl' script to figure out the 'To:' and 'Cc:'?

I don't see Wolfram's name on on the To or Cc field of the emails you
send out:

Wolfram Sang <wsa@the-dreams.de>

6845 I2C SUBSYSTEM
6846 M:      Wolfram Sang <wsa@the-dreams.de>
6847 L:      linux-i2c@vger.kernel.org


Thanks,

Ray

On 1/8/2019 6:15 PM, Rayagonda Kokatanur wrote:
> Sorry for confusion. I made mistake in adding bcm-kernel-feedback-list
> while sending patch. Hence sent same patch set with updated email list. 
> 
> Best regards,
> Rayagonda
> 
> 
> 
> On Jan 8, 2019 10:55 PM, "Ray Jui" <ray.jui@broadcom.com
> <mailto:ray.jui@broadcom.com>> wrote:
> 
>     You sent out the same patch series 3 times without any explanation. Very
>     confusing.
> 
>     Is this the latest one that should be reviewed?
> 
>     Thanks,
> 
>     Ray
> 
> 
>     On 1/8/2019 1:16 AM, Rayagonda Kokatanur wrote:
>     > Hi,
>     > This patchset contains support for IPROC I2C slave and NIC I2C
>     support.
>     > Following are the brief changes done inorder to support both IPROC I2C
>     > slave mode and NIC I2C,
>     >
>     > a. Add support to allow I2C rx transfer upto 255 bytes
>     > b. Add polling mode support to the iProc I2C driver. Polling mode
>     is used
>     >    in certain SoCs where interrupt is not connected from the I2C
>     block.
>     > c. Add warpper read/write access for register to support indirect
>     register
>     >    access. This is required in certain SoCs with this iProc I2C
>     >    block registered.
>     >
>     >
>     > 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: I2C read up to 255 bytes support
>     >   i2c: iproc: Add Slave mode support
>     >
>     >  .../devicetree/bindings/i2c/brcm,iproc-i2c.txt     |  14 +-
>     >  .../arm64/boot/dts/broadcom/stingray/stingray.dtsi |  18 +
>     >  drivers/i2c/busses/Kconfig                         |   1 +
>     >  drivers/i2c/busses/i2c-bcm-iproc.c                 | 767
>     +++++++++++++++++----
>     >  4 files changed, 669 insertions(+), 131 deletions(-)
>     >
> 
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-01-09 18:28 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <1546938997-13798-1-git-send-email-rayagonda.kokatanur@broadcom.com>
2019-01-08 17:25 ` [PATCH 0/8] Add IPROC I2C slave mode and NIC I2C support Ray Jui
     [not found]   ` <CAHO=5PG3NnYqoSyZ9u9kN1m7KagtKv275tpWj6s8NXvzhj52fQ@mail.gmail.com>
2019-01-09 18:27     ` Ray Jui

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).