From: Gustavo Padovan <gustavo@padovan.org>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 04/17] Bluetooth: Add basic packet parsing to Three-wire UART driver
Date: Mon, 9 Jul 2012 11:44:10 -0300 [thread overview]
Message-ID: <20120709144410.GD536@joana> (raw)
In-Reply-To: <1340796367-10321-5-git-send-email-johan.hedberg@gmail.com>
Hi Johan,
* Johan Hedberg <johan.hedberg@gmail.com> [2012-06-27 14:25:54 +0300]:
> From: Johan Hedberg <johan.hedberg@intel.com>
>
> This patch adds basic packet parsing to the Three-wire UART HCI driver
> for packets received from the controller.
>
> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
> ---
> drivers/bluetooth/hci_h5.c | 230 ++++++++++++++++++++++++++++++++++++++++++--
> 1 file changed, 222 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/bluetooth/hci_h5.c b/drivers/bluetooth/hci_h5.c
> index 0f97b05..3b33f90 100644
> --- a/drivers/bluetooth/hci_h5.c
> +++ b/drivers/bluetooth/hci_h5.c
> @@ -32,20 +32,37 @@
>
> #define H5_TXWINSIZE 4
>
> +/*
> + * Maximum Three-wire packet:
> + * 4 byte header + max value for 12-bit length + 2 bytes for CRC
> + */
> +#define H5_MAX_LEN (4 + 0xfff + 2)
> +
> +#define SLIP_DELIMITER 0xc0
> +#define SLIP_ESC 0xdb
> +#define SLIP_ESC_DELIM 0xdc
> +#define SLIP_ESC_ESC 0xdd
> +
> struct h5 {
> - struct sk_buff_head unack; /* Unack'ed packets queue */
> - struct sk_buff_head rel; /* Reliable packets queue */
> - struct sk_buff_head unrel; /* Unreliable packets queue */
> + struct sk_buff_head unack; /* Unack'ed packets queue */
> + struct sk_buff_head rel; /* Reliable packets queue */
> + struct sk_buff_head unrel; /* Unreliable packets queue */
>
> - struct sk_buff *rx_skb;
> + struct sk_buff *rx_skb; /* Receive buffer */
> + size_t rx_pending; /* Expecting more bytes */
> + bool rx_esc; /* SLIP escape mode */
>
> - struct timer_list timer; /* Retransmission timer */
> + int (*rx_func) (struct hci_uart *hu, u8 c);
>
> - bool txack_req;
> + struct timer_list timer; /* Retransmission timer */
>
> - u8 msgq_txseq;
> + bool txack_req;
Can we merge those bool items in a flags field?
> +
> + u8 msgq_txseq;
> };
>
> +static void h5_reset_rx(struct h5 *h5);
> +
> static void h5_timed_event(unsigned long arg)
> {
> struct hci_uart *hu = (struct hci_uart *) arg;
> @@ -83,6 +100,8 @@ static int h5_open(struct hci_uart *hu)
> skb_queue_head_init(&h5->rel);
> skb_queue_head_init(&h5->unrel);
>
> + h5_reset_rx(h5);
> +
> init_timer(&h5->timer);
> h5->timer.function = h5_timed_event;
> h5->timer.data = (unsigned long) hu;
> @@ -105,9 +124,204 @@ static int h5_close(struct hci_uart *hu)
> return 0;
> }
>
> +static void h5_handle_internal_rx(struct hci_uart *hu)
> +{
> + BT_DBG("%s", hu->hdev->name);
> +}
> +
> +static void h5_complete_rx_pkt(struct hci_uart *hu)
> +{
> + struct h5 *h5 = hu->priv;
> + u8 pkt_type;
> +
> + BT_DBG("%s", hu->hdev->name);
> +
> + pkt_type = h5->rx_skb->data[1] & 0x0f;
> +
> + switch (pkt_type) {
> + case HCI_EVENT_PKT:
> + case HCI_ACLDATA_PKT:
> + case HCI_SCODATA_PKT:
> + bt_cb(h5->rx_skb)->pkt_type = pkt_type;
> +
> + /* Remove Three-wire header */
> + skb_pull(h5->rx_skb, 4);
> +
> + hci_recv_frame(h5->rx_skb);
> + h5->rx_skb = NULL;
> +
> + break;
> +
> + default:
> + h5_handle_internal_rx(hu);
> + break;
> + }
> +
> + h5_reset_rx(h5);
> +}
> +
> +static int h5_rx_crc(struct hci_uart *hu, unsigned char c)
> +{
> + struct h5 *h5 = hu->priv;
> +
> + BT_DBG("%s 0x%02hhx", hu->hdev->name, c);
> +
> + h5_complete_rx_pkt(hu);
> + h5_reset_rx(h5);
> +
> + return 0;
There is no point in returning int here.
> +}
> +
> +static int h5_rx_payload(struct hci_uart *hu, unsigned char c)
> +{
> + struct h5 *h5 = hu->priv;
> + const unsigned char *hdr = h5->rx_skb->data;
> +
> + BT_DBG("%s 0x%02hhx", hu->hdev->name, c);
> +
> + if ((hdr[0] >> 4) & 0x01) {
> + h5->rx_func = h5_rx_crc;
> + h5->rx_pending = 2;
> + } else {
> + h5_complete_rx_pkt(hu);
> + h5_reset_rx(h5);
> + }
> +
> + return 0;
> +}
> +
> +static int h5_rx_3wire_hdr(struct hci_uart *hu, unsigned char c)
> +{
> + struct h5 *h5 = hu->priv;
> + const unsigned char *hdr = h5->rx_skb->data;
> +
> + BT_DBG("%s 0x%02hhx", hu->hdev->name, c);
> +
> + if (((hdr[0] + hdr[1] + hdr[2] + hdr[3]) & 0xff) != 0xff) {
> + BT_ERR("Invalid header checksum");
> + h5_reset_rx(h5);
> + return 0;
> + }
> +
> + h5->rx_func = h5_rx_payload;
> + h5->rx_pending = ((hdr[1] >> 4) & 0xff) + (hdr[2] << 4);
> +
> + return 0;
> +}
> +
> +static int h5_rx_pkt_start(struct hci_uart *hu, unsigned char c)
> +{
> + struct h5 *h5 = hu->priv;
> +
> + BT_DBG("%s 0x%02hhx", hu->hdev->name, c);
> +
> + if (c == SLIP_DELIMITER)
> + return 1;
> +
> + h5->rx_func = h5_rx_3wire_hdr;
> + h5->rx_pending = 4;
> +
> + h5->rx_skb = bt_skb_alloc(H5_MAX_LEN, GFP_ATOMIC);
> + if (!h5->rx_skb) {
> + BT_ERR("Can't allocate mem for new packet");
> + h5_reset_rx(h5);
> + return -ENOMEM;
> + }
> +
> + h5->rx_skb->dev = (void *) hu->hdev;
> +
> + return 0;
> +}
> +
> +static int h5_rx_delimiter(struct hci_uart *hu, unsigned char c)
> +{
> + struct h5 *h5 = hu->priv;
> +
> + BT_DBG("%s 0x%02hhx", hu->hdev->name, c);
> +
> + if (c == SLIP_DELIMITER)
> + h5->rx_func = h5_rx_pkt_start;
> +
> + return 1;
Same here.
Gustavo
next prev parent reply other threads:[~2012-07-09 14:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 11:25 [PATCH 00/17] Bluetooth: Implement Three-wire UART HCI driver Johan Hedberg
2012-06-27 11:25 ` [PATCH 01/17] Bluetooth: Initial skeleton for Three-wire UART (H5) support Johan Hedberg
2012-06-27 11:25 ` [PATCH 02/17] Bluetooth: Add basic state tracking to Three-wire UART driver Johan Hedberg
2012-06-27 11:25 ` [PATCH 03/17] Bluetooth: Add initial reliable packet support for Three-wire UART Johan Hedberg
2012-07-09 14:34 ` Gustavo Padovan
2012-06-27 11:25 ` [PATCH 04/17] Bluetooth: Add basic packet parsing to Three-wire UART driver Johan Hedberg
2012-07-09 14:44 ` Gustavo Padovan [this message]
2012-06-27 11:25 ` [PATCH 05/17] Bluetooth: Add initial packet sending support to Three-wire UART Johan Hedberg
2012-06-27 11:25 ` [PATCH 06/17] Bluetooth: Add Three-wire header value convenience macros Johan Hedberg
2012-06-27 11:25 ` [PATCH 07/17] Bluetooth: Fix/implement Three-wire reliable packet sending Johan Hedberg
2012-06-27 11:25 ` [PATCH 08/17] Bluetooth: Add support for Three-wire Link Control packets Johan Hedberg
2012-07-10 18:51 ` Gustavo Padovan
2012-06-27 11:25 ` [PATCH 09/17] Bluetooth: Simplify hci_uart_tty_close logic Johan Hedberg
2012-06-27 11:26 ` [PATCH 10/17] Bluetooth: Add delayed init sequence support for UART controllers Johan Hedberg
2012-07-10 18:53 ` Gustavo Padovan
2012-06-27 11:26 ` [PATCH 11/17] Bluetooth: Use delayed init for Three-wire UART Johan Hedberg
2012-06-27 11:26 ` [PATCH 12/17] Bluetooth: Improve rx debug logs " Johan Hedberg
2012-06-27 11:26 ` [PATCH 13/17] Bluetooth: Add initial sleep support to " Johan Hedberg
2012-07-10 18:57 ` Gustavo Padovan
2012-06-27 11:26 ` [PATCH 14/17] Bluetooth: Add initialization tracking to HCI Three-wire driver Johan Hedberg
2012-07-10 18:58 ` Gustavo Padovan
2012-06-27 11:26 ` [PATCH 15/17] Bluetooth: Implement proper low-power support for Three-wire UART Johan Hedberg
2012-06-27 11:26 ` [PATCH 16/17] Bluetooth: Remove unnecessary h5_build_pkt function Johan Hedberg
2012-06-27 11:26 ` [PATCH 17/17] Bluetooth: Improve Three-wire UART configuration handling Johan Hedberg
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=20120709144410.GD536@joana \
--to=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@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;
as well as URLs for NNTP newsgroup(s).