From: Oleksij Rempel <o.rempel@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Oleksij Rempel <o.rempel@pengutronix.de>
Subject: [PATCH v4 07/13] spi: port spi_sync_transfer() function from kernel v5.17
Date: Fri, 8 Apr 2022 10:29:44 +0200 [thread overview]
Message-ID: <20220408082950.824927-8-o.rempel@pengutronix.de> (raw)
In-Reply-To: <20220408082950.824927-1-o.rempel@pengutronix.de>
This function is needed for SJA11xx switch driver
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
---
include/spi/spi.h | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/include/spi/spi.h b/include/spi/spi.h
index d133e0e212..b6d08592a3 100644
--- a/include/spi/spi.h
+++ b/include/spi/spi.h
@@ -442,6 +442,30 @@ spi_transfer_del(struct spi_transfer *t)
int spi_sync(struct spi_device *spi, struct spi_message *message);
+/**
+ * spi_sync_transfer - synchronous SPI data transfer
+ * @spi: device with which data will be exchanged
+ * @xfers: An array of spi_transfers
+ * @num_xfers: Number of items in the xfer array
+ * Context: can sleep
+ *
+ * Does a synchronous SPI data transfer of the given spi_transfer array.
+ *
+ * For more specific semantics see spi_sync().
+ *
+ * Return: zero on success, else a negative error code.
+ */
+static inline int
+spi_sync_transfer(struct spi_device *spi, struct spi_transfer *xfers,
+ unsigned int num_xfers)
+{
+ struct spi_message msg;
+
+ spi_message_init_with_transfers(&msg, xfers, num_xfers);
+
+ return spi_sync(spi, &msg);
+}
+
struct spi_device *spi_new_device(struct spi_controller *ctrl,
struct spi_board_info *chip);
int spi_register_controller(struct spi_controller *ctrl);
--
2.30.2
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2022-04-08 8:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 8:29 [PATCH v4 00/13] provide DSA support Oleksij Rempel
2022-04-08 8:29 ` [PATCH v4 01/13] net: add RX preprocessor support Oleksij Rempel
2022-04-12 7:58 ` Sascha Hauer
2022-04-12 8:14 ` Oleksij Rempel
2022-04-08 8:29 ` [PATCH v4 02/13] net: add of_find_eth_device_by_node() function Oleksij Rempel
2022-04-08 8:29 ` [PATCH v4 03/13] net: phy: export of_phy_register_fixed_link() function Oleksij Rempel
2022-04-08 8:29 ` [PATCH v4 04/13] net: add DSA framework to support basic switch functionality Oleksij Rempel
2022-04-12 8:02 ` Sascha Hauer
2022-04-08 8:29 ` [PATCH v4 05/13] driver: add dev_get_priv() helper Oleksij Rempel
2022-04-08 8:29 ` [PATCH v4 06/13] net: port part of if_vlan header from kernel v5.17 Oleksij Rempel
2022-04-08 8:29 ` Oleksij Rempel [this message]
2022-04-08 8:29 ` [PATCH v4 08/13] net: mdio: add MDIO_DEVAD_NONE define Oleksij Rempel
2022-04-08 8:29 ` [PATCH v4 09/13] net: phy: make sure MDIO bus is probed if we search for the PHY Oleksij Rempel
2022-04-08 8:29 ` [PATCH v4 10/13] of_net: add rev-rmii support Oleksij Rempel
2022-04-08 8:29 ` [PATCH v4 11/13] net: dsa: add support for SJA11xx switches Oleksij Rempel
2022-04-12 8:25 ` Sascha Hauer
2022-04-08 8:29 ` [PATCH v4 12/13] net: dsa: add KSZ9477 switch SPI driver Oleksij Rempel
2022-04-12 8:37 ` Sascha Hauer
2022-04-08 8:29 ` [PATCH v4 13/13] add ethlog command Oleksij Rempel
2022-04-12 8:54 ` Sascha Hauer
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=20220408082950.824927-8-o.rempel@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=barebox@lists.infradead.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