From: Stefan Schmidt <stefan@osg.samsung.com>
To: Alexander Aring <alex.aring@gmail.com>, linux-wpan@vger.kernel.org
Cc: kernel@pengutronix.de, alan@signal11.us, jonatan@myeden.se
Subject: Re: [RFC bluetooth-next 16/21] mrf24j40: add csma params support
Date: Thu, 27 Aug 2015 15:46:59 +0200 [thread overview]
Message-ID: <55DF14D3.2030700@osg.samsung.com> (raw)
In-Reply-To: <1439468568-22288-17-git-send-email-alex.aring@gmail.com>
Hello.
On 13/08/15 14:22, Alexander Aring wrote:
> This patch adds supports to change the CSMA parameters. The datasheet
> doesn't say anything about max_be value. Seems not configurable and we
> assume the 802.15.4 default. But this value must exists because there is
> a min_be value.
>
> Signed-off-by: Alexander Aring <alex.aring@gmail.com>
> ---
> drivers/net/ieee802154/mrf24j40.c | 30 +++++++++++++++++++++++++++++-
> 1 file changed, 29 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ieee802154/mrf24j40.c b/drivers/net/ieee802154/mrf24j40.c
> index e992bff..fdb0b84 100644
> --- a/drivers/net/ieee802154/mrf24j40.c
> +++ b/drivers/net/ieee802154/mrf24j40.c
> @@ -769,6 +769,26 @@ static int mrf24j40_handle_rx(struct mrf24j40 *devrec)
> return spi_async(devrec->spi, &devrec->rx_msg);
> }
>
> +static int
> +mrf24j40_csma_params(struct ieee802154_hw *hw, u8 min_be, u8 max_be,
> + u8 retries)
> +{
> + struct mrf24j40 *devrec = hw->priv;
> + u8 val;
> +
> + /* datasheet doesn't say anything about max_be, but we have min_be
> + * So we assume the max_be default.
> + */
> + WARN_ON(max_be != 5);
Hmm, the WARN_ON here should never trigger as long as no change is made
to the driver, right? You advertise min_maxbe and max_maxbe both to 5
below and this is the only value that could come from userspace. Maybe
remove the WARN_ON here and move the comment below?
> +
> + /* min_be */
> + val = min_be << 3;
> + /* csma backoffs */
> + val |= retries;
> +
> + return regmap_update_bits(devrec->regmap_short, REG_TXMCR, 0x1f, val);
> +}
> +
> static const struct ieee802154_ops mrf24j40_ops = {
> .owner = THIS_MODULE,
> .xmit_async = mrf24j40_tx,
> @@ -777,6 +797,7 @@ static const struct ieee802154_ops mrf24j40_ops = {
> .stop = mrf24j40_stop,
> .set_channel = mrf24j40_set_channel,
> .set_hw_addr_filt = mrf24j40_filter,
> + .set_csma_params = mrf24j40_csma_params,
> };
>
> static void mrf24j40_intstat_complete(void *context)
> @@ -972,6 +993,12 @@ static void mrf24j40_phy_setup(struct mrf24j40 *devrec)
> {
> ieee802154_random_extended_addr(&devrec->hw->phy->perm_extended_addr);
> devrec->hw->phy->current_channel = 11;
> +
> + /* mrf24j40 supports max_minbe 0 - 3 */
> + devrec->hw->phy->supported.max_minbe = 3;
> + /* We assume max_be is 802.15.4 default */
> + devrec->hw->phy->supported.min_maxbe = 5;
> + devrec->hw->phy->supported.max_maxbe = 5;
> }
>
> static int mrf24j40_probe(struct spi_device *spi)
> @@ -994,7 +1021,8 @@ static int mrf24j40_probe(struct spi_device *spi)
> devrec->hw = hw;
> devrec->hw->parent = &spi->dev;
> devrec->hw->phy->supported.channels[0] = CHANNEL_MASK;
> - devrec->hw->flags = IEEE802154_HW_TX_OMIT_CKSUM | IEEE802154_HW_AFILT;
> + devrec->hw->flags = IEEE802154_HW_TX_OMIT_CKSUM | IEEE802154_HW_AFILT |
> + IEEE802154_HW_CSMA_PARAMS;
>
> mrf24j40_setup_tx_spi_messages(devrec);
> mrf24j40_setup_rx_spi_messages(devrec);
regards
Stefan Schmidt
next prev parent reply other threads:[~2015-08-27 13:47 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 12:22 [RFC bluetooth-next 00/21] mrf24j40: async rx/tx handling and new features Alexander Aring
2015-08-13 12:22 ` [RFC bluetooth-next 01/21] mrf24j40: cleanup define identation Alexander Aring
2015-08-27 12:59 ` Stefan Schmidt
2015-08-13 12:22 ` [RFC bluetooth-next 02/21] mrf24j40: use ieee802154_alloc_hw for private data Alexander Aring
2015-08-27 13:03 ` Stefan Schmidt
2015-08-13 12:22 ` [RFC bluetooth-next 03/21] mrf24j40: calling ieee802154_register_hw at last Alexander Aring
2015-08-27 13:06 ` Stefan Schmidt
2015-08-13 12:22 ` [RFC bluetooth-next 04/21] mrf24j40: remove spi settings overwrite Alexander Aring
2015-08-27 13:14 ` Stefan Schmidt
2015-08-28 7:50 ` Alexander Aring
2015-08-28 7:58 ` Stefan Schmidt
2015-08-13 12:22 ` [RFC bluetooth-next 05/21] mrf24j40: add device-tree support Alexander Aring
2015-08-27 13:16 ` Stefan Schmidt
2015-08-13 12:22 ` [RFC bluetooth-next 06/21] mrf24j40: add default channel setting Alexander Aring
2015-08-27 13:24 ` Stefan Schmidt
2015-08-13 12:22 ` [RFC bluetooth-next 07/21] mrf24j40: add random extended addr generation Alexander Aring
2015-08-27 13:25 ` Stefan Schmidt
2015-08-13 12:22 ` [RFC bluetooth-next 08/21] mrf24j40: add more register defines Alexander Aring
2015-08-27 13:28 ` Stefan Schmidt
2015-08-13 12:22 ` [RFC bluetooth-next 09/21] mrf24j40: add regmap support Alexander Aring
2015-08-27 17:45 ` Alexander Aring
2015-08-28 8:37 ` Stefan Schmidt
2015-08-13 12:22 ` [RFC bluetooth-next 10/21] mrf24j40: use regmap for register access Alexander Aring
2015-08-28 8:43 ` Stefan Schmidt
2015-08-13 12:22 ` [RFC bluetooth-next 11/21] mrf24j40: change to frame delivery with crc Alexander Aring
2015-08-27 13:30 ` Stefan Schmidt
2015-08-13 12:22 ` [RFC bluetooth-next 12/21] ieee802154: add helpers for frame control checks Alexander Aring
2015-08-13 12:22 ` [RFC bluetooth-next 13/21] mrf24j40: rework tx handling to async tx handling Alexander Aring
2015-08-28 8:50 ` Stefan Schmidt
2015-08-13 12:22 ` [RFC bluetooth-next 14/21] mrf24j40: rework rx handling to async rx handling Alexander Aring
2015-08-28 8:55 ` Stefan Schmidt
2015-08-13 12:22 ` [RFC bluetooth-next 15/21] mrf24j40: async interrupt handling Alexander Aring
2015-08-28 8:57 ` Stefan Schmidt
2015-08-13 12:22 ` [RFC bluetooth-next 16/21] mrf24j40: add csma params support Alexander Aring
2015-08-27 13:46 ` Stefan Schmidt [this message]
2015-08-28 7:53 ` Alexander Aring
2015-08-13 12:22 ` [RFC bluetooth-next 17/21] mrf24j40: add cca mode support Alexander Aring
2015-08-27 13:50 ` Stefan Schmidt
2015-08-27 17:49 ` Alexander Aring
2015-08-13 12:22 ` [RFC bluetooth-next 18/21] mrf24j40: add cca ed level support Alexander Aring
2015-08-27 13:52 ` Stefan Schmidt
2015-08-27 17:44 ` Alexander Aring
2015-08-13 12:22 ` [RFC bluetooth-next 19/21] mrf24j40: add tx power support Alexander Aring
2015-08-27 13:59 ` Stefan Schmidt
2015-08-13 12:22 ` [RFC bluetooth-next 20/21] mrf24j40: add promiscuous mode support Alexander Aring
2015-08-27 14:00 ` Stefan Schmidt
2015-08-13 12:22 ` [RFC bluetooth-next 21/21] mrf24j40: change irq trigger type behaviour Alexander Aring
2015-08-28 8:28 ` Stefan Schmidt
2015-08-18 13:54 ` [RFC bluetooth-next 00/21] mrf24j40: async rx/tx handling and new features Alan Ott
2015-08-27 12:29 ` Stefan Schmidt
2015-08-27 12:33 ` Alan Ott
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=55DF14D3.2030700@osg.samsung.com \
--to=stefan@osg.samsung.com \
--cc=alan@signal11.us \
--cc=alex.aring@gmail.com \
--cc=jonatan@myeden.se \
--cc=kernel@pengutronix.de \
--cc=linux-wpan@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).