On Tue, May 14, 2019 at 7:50 AM Sagar Kadam wrote:
>
> Hello Rob,
>
> Thank you for the review.
>
> On Tue, May 14, 2019 at 2:26 AM Rob Herring wrote:
> >
> > On Tue, May 07, 2019 at 08:45:06PM +0530, Sagar Shrikant Kadam wrote:
> > > Add FU540-C000 specific device tree bindings to already
> > >
> > > + */
> > > + i2c@1003 {
> > > + compatible = "sifive,i2c0","sifive,fu540-c000-i2c";
> > > + reg = <0x0 0x1003 0x0 0x1000>;
> > > + reg-names = "i2c-control";
> >
> > Not doucmented.
> In v1, I had added a new binding
Hello Rob,
Thank you for the review.
On Tue, May 14, 2019 at 2:26 AM Rob Herring wrote:
>
> On Tue, May 07, 2019 at 08:45:06PM +0530, Sagar Shrikant Kadam wrote:
> > Add FU540-C000 specific device tree bindings to already
> > available i2-ocores file. This device is available on
> > HiFive Unlea
On Tue, May 07, 2019 at 08:45:06PM +0530, Sagar Shrikant Kadam wrote:
> Add FU540-C000 specific device tree bindings to already
> available i2-ocores file. This device is available on
> HiFive Unleashed Rev A00 board.
>
> Signed-off-by: Sagar Shrikant Kadam
> ---
> Documentation/devicetree/bindi
> +or
> + /*
> + An Opencore based I2C node in FU540-C000 chip from SiFive
> + This chip has a hardware erratum for broken IRQ
> + so it's recommended not to define interrupt in the device node
> + */
> + i2c@1003 {
> + compatible = "sifive,i2c0
Add FU540-C000 specific device tree bindings to already
available i2-ocores file. This device is available on
HiFive Unleashed Rev A00 board.
Signed-off-by: Sagar Shrikant Kadam
---
Documentation/devicetree/bindings/i2c/i2c-ocores.txt | 20
1 file changed, 20 insertions(+)
6 matches
Mail list logo
