Linux wireless drivers development
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Amitkumar Karwar <amitkarwar@gmail.com>
Cc: marcel@holtmann.org, linux-wireless@vger.kernel.org,
	Amitkumar Karwar <amit.karwar@redpinesignals.com>,
	Prameela Rani Garnepudi <prameela.j04cs@gmail.com>,
	linux-bluetooth@vger.kernel.org,
	Siva Rebbagondla <siva.rebbagondla@redpinesignals.com>
Subject: Re: [v5 4/8] rsi: add coex support
Date: Thu, 01 Feb 2018 08:56:14 +0200	[thread overview]
Message-ID: <87r2q5mc4x.fsf@purkki.adurom.net> (raw)
In-Reply-To: <1513168977-2121-5-git-send-email-amitkarwar@gmail.com> (Amitkumar Karwar's message of "Wed, 13 Dec 2017 18:12:53 +0530")

Amitkumar Karwar <amitkarwar@gmail.com> writes:

> From: Prameela Rani Garnepudi <prameela.j04cs@gmail.com>
>
> With BT support, driver has to handle two streams of data
> (i.e. wlan and BT). Actual coex implementation is in firmware.
> Coex module just schedule the packets to firmware by taking them
> from the corresponding paths.
>
> Structures for module and protocol operations are introduced for
> this purpose. Protocol operations structure is global structure
> which can be shared among different modules. Initialization of
> coex and operating mode values is moved to rsi_91x_init().
>
> Signed-off-by: Prameela Rani Garnepudi <prameela.j04cs@gmail.com>
> Signed-off-by: Siva Rebbagondla <siva.rebbagondla@redpinesignals.com>
> Signed-off-by: Amitkumar Karwar <amit.karwar@redpinesignals.com>

[...]

> @@ -270,6 +271,7 @@ struct rsi_common {
>  	u8 obm_ant_sel_val;
>  	int tx_power;
>  	u8 ant_in_use;
> +	struct semaphore tx_bus_lock;

Do you really need to use semaphore? I think nowadays the preference is
to use something other than semaphores.

Also calling it tx_bus_lock is IMHO misleading, tx_bus_sema would be
nicer.

-- 
Kalle Valo

  reply	other threads:[~2018-02-01  6:56 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 12:42 [v5 0/8] rsi: add bluetooth and coex support Amitkumar Karwar
2017-12-13 12:42 ` [v5 1/8] rsi: add rx control block to handle rx packets in USB Amitkumar Karwar
2018-02-01  6:30   ` Kalle Valo
2018-02-13 10:20     ` Amitkumar Karwar
2017-12-13 12:42 ` [v5 2/8] rsi: add bluetooth rx endpoint Amitkumar Karwar
2017-12-13 12:42 ` [v5 3/8] rsi: add header file rsi_header Amitkumar Karwar
2018-02-01  6:39   ` Kalle Valo
2018-02-13 10:22     ` Amitkumar Karwar
2017-12-13 12:42 ` [v5 4/8] rsi: add coex support Amitkumar Karwar
2018-02-01  6:56   ` Kalle Valo [this message]
2018-02-13 10:39     ` Amitkumar Karwar
2018-02-13 15:37       ` Kalle Valo
2018-02-16 14:46         ` Amitkumar Karwar
2018-02-01  7:08   ` Kalle Valo
2018-02-13 10:40     ` Amitkumar Karwar
2017-12-13 12:42 ` [v5 5/8] Bluetooth: btrsi: add new rsi bluetooth driver Amitkumar Karwar
2017-12-13 13:46   ` Marcel Holtmann
2017-12-14 14:22     ` Amitkumar Karwar
2018-01-19  6:53       ` Amitkumar Karwar
2018-02-01  6:58     ` Kalle Valo
2018-02-01  8:16       ` Marcel Holtmann
2018-02-01  8:34         ` Kalle Valo
2017-12-13 12:42 ` [v5 6/8] rsi: handle BT traffic in driver Amitkumar Karwar
2018-02-01  7:10   ` Kalle Valo
2017-12-13 12:42 ` [v5 7/8] rsi: add module parameter operating mode Amitkumar Karwar
2018-02-01  7:11   ` Kalle Valo
2018-02-01  8:20     ` Marcel Holtmann
2018-02-01  8:36       ` Kalle Valo
2017-12-13 12:42 ` [v5 8/8] rsi: sdio changes to support BT Amitkumar Karwar

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=87r2q5mc4x.fsf@purkki.adurom.net \
    --to=kvalo@codeaurora.org \
    --cc=amit.karwar@redpinesignals.com \
    --cc=amitkarwar@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=prameela.j04cs@gmail.com \
    --cc=siva.rebbagondla@redpinesignals.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