From: <Conor.Dooley@microchip.com>
To: <wsa@kernel.org>, <linux-i2c@vger.kernel.org>,
<ben.dooks@codethink.co.uk>, <linux-kernel@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <Daire.McNamara@microchip.com>
Subject: Re: [PATCH v7 1/2] i2c: add support for microchip fpga i2c controllers
Date: Wed, 6 Jul 2022 20:27:50 +0000 [thread overview]
Message-ID: <0e28e644-a25a-173b-caeb-826cc4fb4537@microchip.com> (raw)
In-Reply-To: <YsXhyB9GrfUQjy4n@shikoro>
On 06/07/2022 20:26, Wolfram Sang wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Wed, Jul 06, 2022 at 03:13:13PM +0100, Conor Dooley wrote:
>> Add Microchip CoreI2C i2c controller support. This driver supports the
>> "hard" i2c controller on the Microchip PolarFire SoC & the basic feature
>> set for "soft" i2c controller implemtations in the FPGA fabric.
>>
>> Co-developed-by: Daire McNamara <daire.mcnamara@microchip.com>
>> Signed-off-by: Daire McNamara <daire.mcnamara@microchip.com>
>> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
>
> Driver looks good, but what about the bindings? I shall not merge the
> driver without these.
>
Already upstream :)
Documentation/devicetree/bindings/i2c/microchip,corei2c.yaml
next prev parent reply other threads:[~2022-07-06 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 14:13 [PATCH v7 1/2] i2c: add support for microchip fpga i2c controllers Conor Dooley
2022-07-06 14:13 ` [PATCH v7 2/2] MAINTAINERS: add the polarfire soc's i2c driver Conor Dooley
2022-07-06 19:26 ` [PATCH v7 1/2] i2c: add support for microchip fpga i2c controllers Wolfram Sang
2022-07-06 20:27 ` Conor.Dooley [this message]
2022-07-07 20:54 ` Wolfram Sang
2022-07-07 21:40 ` Conor.Dooley
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=0e28e644-a25a-173b-caeb-826cc4fb4537@microchip.com \
--to=conor.dooley@microchip.com \
--cc=Daire.McNamara@microchip.com \
--cc=ben.dooks@codethink.co.uk \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=wsa@kernel.org \
/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).