From: Oliver Hartkopp <socketcan@hartkopp.net>
To: linux-can@vger.kernel.org
Subject: Re: [PATCH v4 7/7] can: add bittiming check at interface open for CAN FD
Date: Sat, 22 Feb 2014 19:25:21 +0100 [thread overview]
Message-ID: <5308EB91.1010409@hartkopp.net> (raw)
In-Reply-To: <1393009025-4903-8-git-send-email-socketcan@hartkopp.net>
On 21.02.2014 19:57, Oliver Hartkopp wrote:
> Additionally to have the second (data) bitrate available the data bitrate
> has to be greater or equal to the arbitration bitrate in CAN FD.
>
> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
> ---
> drivers/net/can/dev.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/net/can/dev.c b/drivers/net/can/dev.c
> index d9f7281..9c3fb51 100644
> --- a/drivers/net/can/dev.c
> +++ b/drivers/net/can/dev.c
> @@ -652,6 +652,14 @@ int open_candev(struct net_device *dev)
> return -EINVAL;
> }
>
> + /* For CAN FD the data bitrate has to be >= the arbitration bitrate */
> + if ((priv->ctrlmode_supported & CAN_CTRLMODE_FD) &&
Oops.
This has to be the 'living'
priv->ctrlmode
instead of the 'constant'
priv->ctrlmode_supported
Will send an update when there's some more feedback or ACKs ...
Regards,
Oliver
> + (!priv->data_bittiming.tq || !priv->data_bittiming.bitrate ||
> + (priv->data_bittiming.bitrate < priv->bittiming.bitrate))) {
> + netdev_err(dev, "incorrect/missing data bit-timing\n");
> + return -EINVAL;
> + }
> +
> /* Switch carrier on if device was stopped while in bus-off state */
> if (!netif_carrier_ok(dev))
> netif_carrier_on(dev);
>
next prev parent reply other threads:[~2014-02-22 18:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 18:56 [PATCH v4 0/7] Add CAN FD infrastructure for CAN driver Oliver Hartkopp
2014-02-21 18:56 ` [PATCH v4 1/7] can: preserve skbuff protocol in can_put_echo_skb Oliver Hartkopp
2014-02-21 18:57 ` [PATCH v4 2/7] can: netlink send bittiming data only when a bitrate is available Oliver Hartkopp
2014-02-21 18:57 ` [PATCH v4 3/7] can: provide a separate bittiming_const parameter to bittiming functions Oliver Hartkopp
2014-02-21 18:57 ` [PATCH v4 4/7] can: introduce the data bitrate configuration for CAN FD Oliver Hartkopp
2014-02-21 18:57 ` [PATCH v4 5/7] can: allow to change the device mtu for CAN FD capable devices Oliver Hartkopp
2014-02-21 18:57 ` [PATCH v4 6/7] can: fix bitrate check semantics at interface open time Oliver Hartkopp
2014-02-21 18:57 ` [PATCH v4 7/7] can: add bittiming check at interface open for CAN FD Oliver Hartkopp
2014-02-22 18:25 ` Oliver Hartkopp [this message]
2014-02-26 19:52 ` Kurt Van Dijck
2014-02-26 20:35 ` Oliver Hartkopp
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=5308EB91.1010409@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@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).