linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>, linux-can@vger.kernel.org
Subject: Re: [PATCH v7 4/7] can: provide a separate bittiming_const parameter to bittiming functions
Date: Fri, 28 Feb 2014 11:46:51 +0100	[thread overview]
Message-ID: <5310691B.1090507@pengutronix.de> (raw)
In-Reply-To: <1393583188-13307-5-git-send-email-socketcan@hartkopp.net>

[-- Attachment #1: Type: text/plain, Size: 5403 bytes --]

On 02/28/2014 11:26 AM, Oliver Hartkopp wrote:
> As the bittiming calculation functions are to be used with different
> bittiming_const structures for CAN and CAN FD the direct reference to
> priv->bittiming_const inside these functions has to be removed.
> 
> Also simplify the return value generation in can_get_bittiming() as only
> correct return values of can_[calc|fixup]_bittiming() lead to a return value
> of zero. And moved the check for existing bittiming const to one place.
> 
> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
> ---
>  drivers/net/can/dev.c | 59 ++++++++++++++++++++++-----------------------------
>  1 file changed, 25 insertions(+), 34 deletions(-)
> 
> diff --git a/drivers/net/can/dev.c b/drivers/net/can/dev.c
> index 89fc798..c8cd528 100644
> --- a/drivers/net/can/dev.c
> +++ b/drivers/net/can/dev.c
> @@ -99,10 +99,10 @@ static int can_update_spt(const struct can_bittiming_const *btc,
>  	return 1000 * (tseg + 1 - *tseg2) / (tseg + 1);
>  }
>  
> -static int can_calc_bittiming(struct net_device *dev, struct can_bittiming *bt)
> +static int can_calc_bittiming(struct net_device *dev, struct can_bittiming *bt,
> +			      const struct can_bittiming_const *btc)
>  {
>  	struct can_priv *priv = netdev_priv(dev);
> -	const struct can_bittiming_const *btc = priv->bittiming_const;
>  	long rate, best_rate = 0;
>  	long best_error = 1000000000, error = 0;
>  	int best_tseg = 0, best_brp = 0, brp = 0;
> @@ -110,9 +110,6 @@ static int can_calc_bittiming(struct net_device *dev, struct can_bittiming *bt)
>  	int spt_error = 1000, spt = 0, sampl_pt;
>  	u64 v64;
>  
> -	if (!priv->bittiming_const)
> -		return -ENOTSUPP;
> -
>  	/* Use CIA recommended sample points */
>  	if (bt->sample_point) {
>  		sampl_pt = bt->sample_point;
> @@ -204,7 +201,8 @@ static int can_calc_bittiming(struct net_device *dev, struct can_bittiming *bt)
>  	return 0;
>  }
>  #else /* !CONFIG_CAN_CALC_BITTIMING */
> -static int can_calc_bittiming(struct net_device *dev, struct can_bittiming *bt)
> +static int can_calc_bittiming(struct net_device *dev, struct can_bittiming *bt,
> +			      const struct can_bittiming_const *btc)
>  {
>  	netdev_err(dev, "bit-timing calculation not available\n");
>  	return -EINVAL;
> @@ -217,16 +215,13 @@ static int can_calc_bittiming(struct net_device *dev, struct can_bittiming *bt)
>   * prescaler value brp. You can find more information in the header
>   * file linux/can/netlink.h.
>   */
> -static int can_fixup_bittiming(struct net_device *dev, struct can_bittiming *bt)
> +static int can_fixup_bittiming(struct net_device *dev, struct can_bittiming *bt,
> +			       const struct can_bittiming_const *btc)
>  {
>  	struct can_priv *priv = netdev_priv(dev);
> -	const struct can_bittiming_const *btc = priv->bittiming_const;
>  	int tseg1, alltseg;
>  	u64 brp64;
>  
> -	if (!priv->bittiming_const)
> -		return -ENOTSUPP;
> -
>  	tseg1 = bt->prop_seg + bt->phase_seg1;
>  	if (!bt->sjw)
>  		bt->sjw = 1;
> @@ -254,33 +249,29 @@ static int can_fixup_bittiming(struct net_device *dev, struct can_bittiming *bt)
>  	return 0;
>  }
>  
> -static int can_get_bittiming(struct net_device *dev, struct can_bittiming *bt)
> +static int can_get_bittiming(struct net_device *dev, struct can_bittiming *bt,
> +			     const struct can_bittiming_const *btc)
>  {
> -	struct can_priv *priv = netdev_priv(dev);
> -	int err;
> +	int err = -EINVAL;

Keep err uninitialized and make an explicit else err = -EINVAL.... see
below:

>  
>  	/* Check if the CAN device has bit-timing parameters */
> -	if (priv->bittiming_const) {
> -
> -		/* Non-expert mode? Check if the bitrate has been pre-defined */
> -		if (!bt->tq) {
> -			/* Determine bit-timing parameters */
> -			if (bt->bitrate)
> -				err = can_calc_bittiming(dev, bt);
> -			else
> -				return -EINVAL;
> -		} else {
> -			/* Check bit-timing params and calculate proper brp */
> -			if (!bt->bitrate)
> -				err = can_fixup_bittiming(dev, bt);
> -			else
> -				return -EINVAL;
> -		}
> -		if (err)
> -			return err;
> +	if (!btc)
> +		return -ENOTSUPP;
> +
> +	if (!bt->tq) {
> +		/* non-expert mode: Determine bit-timing parameters */
> +		if (bt->bitrate)

Why not:
	if (!bt->tq && bt->bitrate) {

> +			err = can_calc_bittiming(dev, bt, btc);
> +	} else {

	} else if (bt->tq && !bt->bitrate) {

> +		/*
> +		 * expert mode: Check bit-timing parameters and
> +		 * calculate proper brp and a human readable bitrate
> +		 */
> +		if (!bt->bitrate)
> +			err = can_fixup_bittiming(dev, bt, btc);
>  	}
	} else {
		err = -EINVAL;
	}
>  
> -	return 0;
> +	return err;
>  }
>  
>  /*
> @@ -674,7 +665,7 @@ static int can_changelink(struct net_device *dev,
>  		if (dev->flags & IFF_UP)
>  			return -EBUSY;
>  		memcpy(&bt, nla_data(data[IFLA_CAN_BITTIMING]), sizeof(bt));
> -		err = can_get_bittiming(dev, &bt);
> +		err = can_get_bittiming(dev, &bt, priv->bittiming_const);
>  		if (err)
>  			return err;
>  		memcpy(&priv->bittiming, &bt, sizeof(bt));
> 


-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 242 bytes --]

  reply	other threads:[~2014-02-28 10:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28 10:26 [PATCH v7 0/7] Add CAN FD infrastructure for CAN driver Oliver Hartkopp
2014-02-28 10:26 ` [PATCH v7 1/7] can: preserve skbuff protocol in can_put_echo_skb Oliver Hartkopp
2014-02-28 10:26 ` [PATCH v7 2/7] can: only send bitrate data via netlink when available Oliver Hartkopp
2014-02-28 10:26 ` [PATCH v7 3/7] can: move sanity check for bitrate and tq into can_get_bittiming Oliver Hartkopp
2014-02-28 10:26 ` [PATCH v7 4/7] can: provide a separate bittiming_const parameter to bittiming functions Oliver Hartkopp
2014-02-28 10:46   ` Marc Kleine-Budde [this message]
2014-02-28 12:31     ` Oliver Hartkopp
2014-02-28 13:02       ` Marc Kleine-Budde
2014-02-28 13:07         ` Oliver Hartkopp
2014-02-28 10:26 ` [PATCH v7 5/7] can: introduce the data bitrate configuration for CAN FD Oliver Hartkopp
2014-02-28 10:26 ` [PATCH v7 6/7] can: allow to change the device mtu for CAN FD capable devices Oliver Hartkopp
2014-02-28 10:26 ` [PATCH v7 7/7] can: add bittiming check at interface open for CAN FD 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=5310691B.1090507@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=linux-can@vger.kernel.org \
    --cc=socketcan@hartkopp.net \
    /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).