From: Wolfram Sang <wsa@the-dreams.de>
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,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH REPOST v8 2/3] i2c-ocores: sifive: add support for i2c device on FU540-c000 SoC.
Date: Fri, 14 Jun 2019 22:58:46 +0200 [thread overview]
Message-ID: <20190614205846.GD17899@ninjato> (raw)
In-Reply-To: <1559369475-15374-3-git-send-email-sagar.kadam@sifive.com>
[-- Attachment #1: Type: text/plain, Size: 459 bytes --]
On Sat, Jun 01, 2019 at 11:41:14AM +0530, Sagar Shrikant Kadam wrote:
> Update device id table for Opencore's I2C master based re-implementation
> used in FU540-c000 chipset on HiFive Unleashed platform.
>
> Device ID's include Sifive, soc-specific device for chip specific tweaks
> and sifive IP block specific device for generic programming model.
>
> Signed-off-by: Sagar Shrikant Kadam <sagar.kadam@sifive.com>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
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,
linux-i2c@vger.kernel.org, paul.walmsley@sifive.com,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH REPOST v8 2/3] i2c-ocores: sifive: add support for i2c device on FU540-c000 SoC.
Date: Fri, 14 Jun 2019 22:58:46 +0200 [thread overview]
Message-ID: <20190614205846.GD17899@ninjato> (raw)
In-Reply-To: <1559369475-15374-3-git-send-email-sagar.kadam@sifive.com>
[-- Attachment #1.1: Type: text/plain, Size: 459 bytes --]
On Sat, Jun 01, 2019 at 11:41:14AM +0530, Sagar Shrikant Kadam wrote:
> Update device id table for Opencore's I2C master based re-implementation
> used in FU540-c000 chipset on HiFive Unleashed platform.
>
> Device ID's include Sifive, soc-specific device for chip specific tweaks
> and sifive IP block specific device for generic programming model.
>
> Signed-off-by: Sagar Shrikant Kadam <sagar.kadam@sifive.com>
Applied to for-next, thanks!
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-06-14 20:58 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
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 [this message]
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 2/3] i2c-ocores: sifive: add support for i2c device on FU540-c000 SoC 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=20190614205846.GD17899@ninjato \
--to=wsa@the-dreams.de \
--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.