From: Gustavo Padovan <gustavo@padovan.org>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 08/17] Bluetooth: Add support for Three-wire Link Control packets
Date: Tue, 10 Jul 2012 15:51:07 -0300 [thread overview]
Message-ID: <20120710185107.GF13847@joana> (raw)
In-Reply-To: <1340796367-10321-9-git-send-email-johan.hedberg@gmail.com>
Hi Johan,
* Johan Hedberg <johan.hedberg@gmail.com> [2012-06-27 14:25:58 +0300]:
> From: Johan Hedberg <johan.hedberg@intel.com>
>
> This patch adds basic support for parsing and sending Three-wire UART
> Link Controll packets.
typo here, it is Control.
>
> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
> ---
> drivers/bluetooth/hci_h5.c | 93 ++++++++++++++++++++++++++++++++++++--------
> 1 file changed, 77 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/bluetooth/hci_h5.c b/drivers/bluetooth/hci_h5.c
> index e27dce7..d602cc4 100644
> --- a/drivers/bluetooth/hci_h5.c
> +++ b/drivers/bluetooth/hci_h5.c
> @@ -63,7 +63,6 @@ struct h5 {
> size_t rx_pending; /* Expecting more bytes */
> bool rx_esc; /* SLIP escape mode */
> u8 rx_ack; /* Last ack number received */
> - u8 rx_seq; /* Last seq number received */
>
> int (*rx_func) (struct hci_uart *hu, u8 c);
>
> @@ -71,6 +70,7 @@ struct h5 {
>
> bool tx_ack_req; /* Pending ack to send */
> u8 tx_seq; /* Next seq number to send */
> + u8 tx_ack; /* Next ack number to send */
> };
>
> static void h5_reset_rx(struct h5 *h5);
> @@ -96,9 +96,26 @@ static void h5_timed_event(unsigned long arg)
> hci_uart_tx_wakeup(hu);
> }
>
> +static void h5_link_control(struct hci_uart *hu, const void *data, size_t len)
> +{
> + struct h5 *h5 = hu->priv;
> + struct sk_buff *nskb;
> +
> + nskb = alloc_skb(3, GFP_ATOMIC);
> + if (!nskb)
> + return;
> +
> + bt_cb(nskb)->pkt_type = HCI_3WIRE_LINK_PKT;
> +
> + memcpy(skb_put(nskb, len), data, len);
> +
> + skb_queue_tail(&h5->unrel, nskb);
> +}
> +
> static int h5_open(struct hci_uart *hu)
> {
> struct h5 *h5;
> + const unsigned char sync[] = { 0x01, 0x7e };
>
> BT_DBG("hu %p", hu);
>
> @@ -118,6 +135,10 @@ static int h5_open(struct hci_uart *hu)
> h5->timer.function = h5_timed_event;
> h5->timer.data = (unsigned long) hu;
>
> + /* Send initial sync request */
> + h5_link_control(hu, sync, sizeof(sync));
> + mod_timer(&h5->timer, jiffies + HZ / 10);
remove this HZ usage please.
> +
> return 0;
> }
>
> @@ -146,6 +167,8 @@ static void h5_pkt_cull(struct h5 *h5)
> spin_lock_irqsave(&h5->unack.lock, flags);
>
> to_remove = skb_queue_len(&h5->unack);
> + if (to_remove == 0)
> + goto unlock;
>
> seq = h5->tx_seq;
>
> @@ -172,12 +195,44 @@ static void h5_pkt_cull(struct h5 *h5)
> if (skb_queue_empty(&h5->unack))
> del_timer(&h5->timer);
>
> +unlock:
> spin_unlock_irqrestore(&h5->unack.lock, flags);
> }
>
> static void h5_handle_internal_rx(struct hci_uart *hu)
> {
> + struct h5 *h5 = hu->priv;
> + const unsigned char sync_req[] = { 0x01, 0x7e };
> + const unsigned char sync_rsp[] = { 0x02, 0x7d };
> + const unsigned char conf_req[] = { 0x03, 0xfc, 0x01 };
> + const unsigned char conf_rsp[] = { 0x04, 0x7b, 0x01 };
> + const unsigned char *hdr = h5->rx_skb->data;
> + const unsigned char *data = &h5->rx_skb->data[4];
> +
> BT_DBG("%s", hu->hdev->name);
> +
> + if (H5_HDR_PKT_TYPE(hdr) != HCI_3WIRE_LINK_PKT)
> + return;
> +
> + if (H5_HDR_LEN(hdr) < 2)
> + return;
> +
> + if (memcmp(data, sync_req, 2) == 0)
> + h5_link_control(hu, sync_rsp, 2);
> + else if (memcmp(data, sync_rsp, 2) == 0)
> + h5_link_control(hu, conf_req, 3);
> + else if (memcmp(data, conf_req, 2) == 0) {
> + h5_link_control(hu, conf_rsp, 2);
> + h5_link_control(hu, conf_req, 3);
> + } else if (memcmp(data, conf_rsp, 2) == 0) {
> + BT_DBG("Three-wire init sequence complete");
> + return;
> + } else {
> + BT_DBG("Link Control: 0x%02hhx 0x%02hhx", data[0], data[1]);
> + return;
> + }
There are missing braces here, some of them have but some of them not.
Gustavo
next prev parent reply other threads:[~2012-07-10 18:51 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
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 [this message]
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=20120710185107.GF13847@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).