public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <mail@conchuod.ie>
To: Conor.Dooley@microchip.com, wsa@kernel.org, linux-i2c@vger.kernel.org
Cc: ben.dooks@codethink.co.uk, linux-kernel@vger.kernel.org,
	linux-riscv@lists.infradead.org, Daire.McNamara@microchip.com,
	geert@linux-m68k.org
Subject: Re: [PATCH v2] i2c: add support for microchip fpga i2c controllers
Date: Wed, 4 May 2022 17:17:43 +0100	[thread overview]
Message-ID: <1e6de466-eefc-c5f7-5db7-6a87ff1608ed@conchuod.ie> (raw)
In-Reply-To: <cad04bc5-ce7b-d7db-f967-8b2bb67897ae@microchip.com>

On 04/05/2022 09:40, Conor.Dooley@microchip.com wrote:
> On 21/03/2022 12:58, Conor Dooley wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> 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>
>> ---
>> Changes from v1:
>> - Use byte write and read functions
> 
> So it turns out that how I made this change, which worked in my
> test app, has issues.
> I will rework and send a v3.
> 

Welp, as it turns out we can chalk the issues up to user error,
aka me entirely forgetting what the correct i2cdetect options
were - d'oh.

Apologies for the noise & unless something else changes, don't
expect a V3.

Sorry,
Conor.

  reply	other threads:[~2022-05-04 16:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 12:58 [PATCH v2] i2c: add support for microchip fpga i2c controllers Conor Dooley
2022-05-04  8:40 ` Conor.Dooley
2022-05-04 16:17   ` Conor Dooley [this message]
     [not found] <20220504091622.5024-1-hdanton@sina.com>
2022-05-04 12:54 ` 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=1e6de466-eefc-c5f7-5db7-6a87ff1608ed@conchuod.ie \
    --to=mail@conchuod.ie \
    --cc=Conor.Dooley@microchip.com \
    --cc=Daire.McNamara@microchip.com \
    --cc=ben.dooks@codethink.co.uk \
    --cc=geert@linux-m68k.org \
    --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