From: Matt Johnston <matt@codeconstruct.com.au>
To: unlisted-recipients:; (no To-header on input)
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jeremy Kerr <jk@codeconstruct.com.au>,
linux-i2c@vger.kernel.org, netdev@vger.kernel.org,
Zev Weiss <zev@bewilderbeest.net>
Subject: [PATCH net-next v6 0/2] MCTP I2C driver
Date: Fri, 18 Feb 2022 13:51:04 +0800 [thread overview]
Message-ID: <20220218055106.1944485-1-matt@codeconstruct.com.au> (raw)
This patch series adds a netdev driver providing MCTP transport over
I2C.
I think I've addressed all the points raised in v5. It now has
mctp_i2c_unregister() to run things in the correct order, waiting for
the worker thread and I2C rx to complete.
Cheers,
Matt
--
v6:
- Changed netdev register/unregister/free to avoid races. Ensure that
netif functions are not used by irq handler/threads after unregister.
- Fix incoming I2C hwaddr that was previously incorrect (left
shifted 1 bit)
- Add a check that byte_count wire header matches the length received
- Renamed I2C driver to mctp-i2c-interface
- Removed __func__ from print messages, added missing newlines
- Removed sysfs mctp_current_mux file which was used for debug
- Renamed curr_lock to sel_lock
- Tidied comment formatting
- Fix newline in Kconfig
v5:
- Fix incorrect format string
v4:
- Switch to __i2c_transfer() rather than __i2c_smbus_xfer(), drop 255 byte
smbus patches
- Use wait_event_idle() for the sleeping TX thread
- Use dev_addr_set()
v3:
- Added Reviewed-bys for npcm7xx
- Resend with net-next open
v2:
- Simpler Kconfig condition for i2c-mux dependency, from Randy Dunlap
Matt Johnston (2):
dt-bindings: net: New binding mctp-i2c-controller
mctp i2c: MCTP I2C binding driver
Documentation/devicetree/bindings/i2c/i2c.txt | 4 +
.../bindings/net/mctp-i2c-controller.yaml | 92 ++
drivers/net/mctp/Kconfig | 12 +
drivers/net/mctp/Makefile | 1 +
drivers/net/mctp/mctp-i2c.c | 1081 +++++++++++++++++
5 files changed, 1190 insertions(+)
create mode 100644 Documentation/devicetree/bindings/net/mctp-i2c-controller.yaml
create mode 100644 drivers/net/mctp/mctp-i2c.c
--
2.32.0
next reply other threads:[~2022-02-18 5:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 5:51 Matt Johnston [this message]
2022-02-18 5:51 ` [PATCH net-next v6 1/2] dt-bindings: net: New binding mctp-i2c-controller Matt Johnston
2022-02-18 5:51 ` [PATCH net-next v6 2/2] mctp i2c: MCTP I2C binding driver Matt Johnston
2022-02-18 9:41 ` Wolfram Sang
2022-02-19 16:40 ` [PATCH net-next v6 0/2] MCTP I2C driver patchwork-bot+netdevbpf
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=20220218055106.1944485-1-matt@codeconstruct.com.au \
--to=matt@codeconstruct.com.au \
--cc=davem@davemloft.net \
--cc=jk@codeconstruct.com.au \
--cc=kuba@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=zev@bewilderbeest.net \
/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).