public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Gerhard Engleder <gerhard@engleder-embedded.com>
Cc: linux-i2c@vger.kernel.org, andi.shyti@kernel.org, arnd@arndb.de
Subject: Re: [PATCH v2 0/2] I2C controller support for KEBA PLCs
Date: Thu, 4 Jul 2024 12:30:16 +0200	[thread overview]
Message-ID: <2024070441-class-backless-4ea7@gregkh> (raw)
In-Reply-To: <20240630194740.7137-1-gerhard@engleder-embedded.com>

On Sun, Jun 30, 2024 at 09:47:38PM +0200, Gerhard Engleder wrote:
> KEBA PLCs use a PCIe FPGA to implement several functions in a common
> way. This is a first step to include basic support for this FPGA.
> 
> Under drivers/misc the cp500 PCI driver is added. This drivers creates
> auxiliary devices for every function inside the FPGA. As a first step it
> only creates auxiliary devices for the I2C controllers.
> 
> The I2C controller driver is added under drivers/i2c/busses like all the
> other I2C controller drivers.
> 
> This patches enable access to the EEPROMs and to the hardware monitoring
> chip of KEBA PLCs.

I've applied patch 1/2 to my char-misc tree, nice work!

I'll wait for an ack from the i2c maintainers before applying that one,
or it can come in through the i2c tree after 6.11-rc1 is out.

thanks,

greg k-h

      parent reply	other threads:[~2024-07-04 10:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-30 19:47 [PATCH v2 0/2] I2C controller support for KEBA PLCs Gerhard Engleder
2024-06-30 19:47 ` [PATCH v2 1/2] misc: keba: Add basic KEBA CP500 system FPGA support Gerhard Engleder
2024-06-30 19:47 ` [PATCH v2 2/2] i2c: keba: Add KEBA I2C controller support Gerhard Engleder
2024-07-03 22:09   ` Andi Shyti
2024-07-05 17:03     ` Gerhard Engleder
2024-07-04 10:30 ` Greg KH [this message]

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=2024070441-class-backless-4ea7@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=andi.shyti@kernel.org \
    --cc=arnd@arndb.de \
    --cc=gerhard@engleder-embedded.com \
    --cc=linux-i2c@vger.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