From: Kalle Valo <kvalo@codeaurora.org>
To: David Miller <davem@davemloft.net>,
Johannes Berg <johannes@sipsolutions.net>
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>,
Amitkumar Karwar <amitkarwar@gmail.com>
Subject: Re: [v7 3/8] rsi: add header file rsi_91x
Date: Tue, 20 Feb 2018 15:14:14 +0200 [thread overview]
Message-ID: <87o9kjiz15.fsf@codeaurora.org> (raw)
In-Reply-To: <1519046379-10068-4-git-send-email-amitkarwar@gmail.com> (Amitkumar Karwar's message of "Mon, 19 Feb 2018 18:49:34 +0530")
Hi Dave and Johannes,
a question to both of you below:
Amitkumar Karwar <amitkarwar@gmail.com> writes:
> From: Prameela Rani Garnepudi <prameela.j04cs@gmail.com>
>
> The common parameters used by wlan and bt modules are add
> to a new header file "rsi_91x.h" defined in 'include/net'
>
> 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>
> ---
> v7: Same as v6
> v6: Renamed rsi_header.h to rsi_91x.h and moved to include/net
> from include/linux(Kalle)
> v5: Same as earlier versions
[...]
> --- /dev/null
> +++ b/include/net/rsi_91x.h
> @@ -0,0 +1,34 @@
> +/**
> + * Copyright (c) 2017 Redpine Signals Inc.
> + *
> + * Permission to use, copy, modify, and/or distribute this software for any
> + * purpose with or without fee is hereby granted, provided that the above
> + * copyright notice and this permission notice appear in all copies.
> + *
> + * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
> + * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
> + * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
> + * ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
> + * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
> + * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
> + * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
> + */
> +
> +#ifndef __RSI_HEADER_H__
> +#define __RSI_HEADER_H__
> +
> +/* HAL queue information */
> +#define RSI_COEX_Q 0x0
> +#define RSI_BT_Q 0x2
> +#define RSI_WLAN_Q 0x3
> +#define RSI_WIFI_MGMT_Q 0x4
> +#define RSI_WIFI_DATA_Q 0x5
> +#define RSI_BT_MGMT_Q 0x6
> +#define RSI_BT_DATA_Q 0x7
> +
> +enum rsi_host_intf {
> + RSI_HOST_INTF_SDIO = 0,
> + RSI_HOST_INTF_USB
> +};
> +
> +#endif
Are you guys ok to have this header file shared by rsi wireless and
bluetooth driver in include/net?
--
Kalle Valo
next prev parent reply other threads:[~2018-02-20 13:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 13:19 [v7 0/8] rsi: add bluetooth and coex support Amitkumar Karwar
2018-02-19 13:19 ` [v7 1/8] rsi: add rx control block to handle rx packets in USB Amitkumar Karwar
2018-02-19 13:19 ` [v7 2/8] rsi: add bluetooth rx endpoint Amitkumar Karwar
2018-02-19 13:19 ` [v7 3/8] rsi: add header file rsi_91x Amitkumar Karwar
2018-02-20 13:14 ` Kalle Valo [this message]
2018-03-05 13:56 ` Amitkumar Karwar
2018-02-19 13:19 ` [v7 4/8] rsi: add coex support Amitkumar Karwar
2018-02-20 3:49 ` kbuild test robot
2018-02-19 13:19 ` [v7 5/8] Bluetooth: btrsi: add new rsi bluetooth driver Amitkumar Karwar
2018-02-19 23:57 ` kbuild test robot
2018-02-19 13:19 ` [v7 6/8] rsi: handle BT traffic in driver Amitkumar Karwar
2018-02-19 13:19 ` [v7 7/8] rsi: add module parameter operating mode Amitkumar Karwar
2018-02-19 13:19 ` [v7 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=87o9kjiz15.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=amit.karwar@redpinesignals.com \
--cc=amitkarwar@gmail.com \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.