From: Rob Herring <robh@kernel.org>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, peter@korsgaard.com,
andrew@lunn.ch, palmer@sifive.com, paul.walmsley@sifive.com,
sagar.kadam@sifive.com, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH REPOST v8 1/3] dt-bindings: i2c: extend existing opencore bindings.
Date: Tue, 11 Jun 2019 16:49:52 -0600 [thread overview]
Message-ID: <20190611224952.GA17031@bogus> (raw)
In-Reply-To: <1559369475-15374-2-git-send-email-sagar.kadam@sifive.com>
On Sat, 1 Jun 2019 11:41:13 +0530, Sagar Shrikant Kadam wrote:
> Reformatted compatibility strings to one valid combination on
> each line.
> Add FU540-C000 specific device tree bindings to already available
> i2-ocores file. This device is available on
> HiFive Unleashed Rev A00 board. Move interrupt under optional
> property list as this can be optional.
>
> The FU540-C000 SoC from sifive, has an Opencore's I2C block
> reimplementation.
>
> The DT compatibility string for this IP is present in HDL and available at.
> https://github.com/sifive/sifive-blocks/blob/master/src/main/scala/devices/i2c/I2C.scala#L73
>
> Signed-off-by: Sagar Shrikant Kadam <sagar.kadam@sifive.com>
> ---
> Documentation/devicetree/bindings/i2c/i2c-ocores.txt | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Sagar Shrikant Kadam <sagar.kadam@sifive.com>
Cc: mark.rutland@arm.com, andrew@lunn.ch, peter@korsgaard.com,
devicetree@vger.kernel.org, palmer@sifive.com,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
sagar.kadam@sifive.com, paul.walmsley@sifive.com,
linux-riscv@lists.infradead.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH REPOST v8 1/3] dt-bindings: i2c: extend existing opencore bindings.
Date: Tue, 11 Jun 2019 16:49:52 -0600 [thread overview]
Message-ID: <20190611224952.GA17031@bogus> (raw)
In-Reply-To: <1559369475-15374-2-git-send-email-sagar.kadam@sifive.com>
On Sat, 1 Jun 2019 11:41:13 +0530, Sagar Shrikant Kadam wrote:
> Reformatted compatibility strings to one valid combination on
> each line.
> Add FU540-C000 specific device tree bindings to already available
> i2-ocores file. This device is available on
> HiFive Unleashed Rev A00 board. Move interrupt under optional
> property list as this can be optional.
>
> The FU540-C000 SoC from sifive, has an Opencore's I2C block
> reimplementation.
>
> The DT compatibility string for this IP is present in HDL and available at.
> https://github.com/sifive/sifive-blocks/blob/master/src/main/scala/devices/i2c/I2C.scala#L73
>
> Signed-off-by: Sagar Shrikant Kadam <sagar.kadam@sifive.com>
> ---
> Documentation/devicetree/bindings/i2c/i2c-ocores.txt | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Sagar Shrikant Kadam <sagar.kadam@sifive.com>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, peter@korsgaard.com,
andrew@lunn.ch, palmer@sifive.com, paul.walmsley@sifive.com,
sagar.kadam@sifive.com, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH REPOST v8 1/3] dt-bindings: i2c: extend existing opencore bindings.
Date: Tue, 11 Jun 2019 16:49:52 -0600 [thread overview]
Message-ID: <20190611224952.GA17031@bogus> (raw)
In-Reply-To: <1559369475-15374-2-git-send-email-sagar.kadam@sifive.com>
On Sat, 1 Jun 2019 11:41:13 +0530, Sagar Shrikant Kadam wrote:
> Reformatted compatibility strings to one valid combination on
> each line.
> Add FU540-C000 specific device tree bindings to already available
> i2-ocores file. This device is available on
> HiFive Unleashed Rev A00 board. Move interrupt under optional
> property list as this can be optional.
>
> The FU540-C000 SoC from sifive, has an Opencore's I2C block
> reimplementation.
>
> The DT compatibility string for this IP is present in HDL and available at.
> https://github.com/sifive/sifive-blocks/blob/master/src/main/scala/devices/i2c/I2C.scala#L73
>
> Signed-off-by: Sagar Shrikant Kadam <sagar.kadam@sifive.com>
> ---
> Documentation/devicetree/bindings/i2c/i2c-ocores.txt | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-06-11 22:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-01 6:11 [PATCH REPOST v8 0/3] Extend dt bindings to support I2C on sifive devices and a fix broken IRQ in polling mode Sagar Shrikant Kadam
2019-06-01 6:11 ` Sagar Shrikant Kadam
2019-06-01 6:11 ` [PATCH REPOST v8 1/3] dt-bindings: i2c: extend existing opencore bindings Sagar Shrikant Kadam
2019-06-01 6:11 ` Sagar Shrikant Kadam
2019-06-11 22:49 ` Rob Herring [this message]
2019-06-11 22:49 ` Rob Herring
2019-06-11 22:49 ` Rob Herring
2019-06-14 20:58 ` Wolfram Sang
2019-06-14 20:58 ` Wolfram Sang
2019-06-01 6:11 ` [PATCH REPOST v8 2/3] i2c-ocores: sifive: add support for i2c device on FU540-c000 SoC Sagar Shrikant Kadam
2019-06-01 6:11 ` Sagar Shrikant Kadam
2019-06-14 20:58 ` Wolfram Sang
2019-06-14 20:58 ` Wolfram Sang
2019-06-01 6:11 ` [PATCH REPOST v8 3/3] i2c-ocores: sifive: add polling mode workaround for FU540-C000 SoC Sagar Shrikant Kadam
2019-06-01 6:11 ` Sagar Shrikant Kadam
2019-06-14 20:58 ` Wolfram Sang
2019-06-14 20:58 ` Wolfram Sang
-- strict thread matches above, loose matches on Subject: below --
2019-05-31 18:30 [PATCH REPOST v8 0/3] Extend dt bindings to support I2C on sifive devices and a fix broken IRQ in polling mode Sagar Shrikant Kadam
2019-05-31 18:30 ` [PATCH REPOST v8 1/3] dt-bindings: i2c: extend existing opencore bindings Sagar Shrikant Kadam
2019-05-31 18:30 ` Sagar Shrikant Kadam
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=20190611224952.GA17031@bogus \
--to=robh@kernel.org \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=peter@korsgaard.com \
--cc=robh+dt@kernel.org \
--cc=sagar.kadam@sifive.com \
/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.