linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rishi Gupta <gupt21@gmail.com>
To: jikos@kernel.org, benjamin.tissoires@redhat.com,
	wsa+renesas@sang-engineering.com
Cc: gregkh@linuxfoundation.org, linux-i2c@vger.kernel.org,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	Rishi Gupta <gupt21@gmail.com>
Subject: [PATCH v1 0/1] HID: mcp2221: add usb to i2c-smbus host bridge driver
Date: Mon, 20 Jan 2020 10:57:37 +0530	[thread overview]
Message-ID: <cover.1579497275.git.gupt21@gmail.com> (raw)

MCP2221 is a USB HID to I2C/SMbus host bridge device. This
commit implements i2c and smbus host adapter support. 7-bit
address and i2c multi-message transaction is also supported.

Different transactions have been tested with various common
hardwares, linux driver and user space tools.

Host PC communicates with mcp2221a over usb using raw hid protocol.
Reports are exchanged using interrupt end points. Command and responses
are mcp2221a specific and documented in datasheet:
http://ww1.microchip.com/downloads/en/DeviceDoc/20005565B.pdf

There is only 1 patch in this driver submission.

Rishi Gupta (1):
  HID: mcp2221: add usb to i2c-smbus host bridge driver

 drivers/hid/Kconfig       |  10 +
 drivers/hid/Makefile      |   1 +
 drivers/hid/hid-ids.h     |   1 +
 drivers/hid/hid-mcp2221.c | 773 ++++++++++++++++++++++++++++++++++++++++++++++
 drivers/hid/hid-quirks.c  |   3 +
 5 files changed, 788 insertions(+)
 create mode 100644 drivers/hid/hid-mcp2221.c

-- 
2.7.4


             reply	other threads:[~2020-01-20  5:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20  5:27 Rishi Gupta [this message]
2020-01-20  5:27 ` [PATCH v1 1/1] HID: mcp2221: add usb to i2c-smbus host bridge driver Rishi Gupta
2020-01-20 18:05   ` kbuild test robot
2020-01-20 18:05   ` [RFC PATCH] HID: mcp2221: mcp_smbus_xfer() can be static kbuild test robot

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=cover.1579497275.git.gupt21@gmail.com \
    --to=gupt21@gmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jikos@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.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 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).