Netdev List
 help / color / mirror / Atom feed
From: Franklin S Cooper Jr <fcooper-l0cyMroinI0@public.gmane.org>
To: Sergei Shtylyov
	<sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>,
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	<linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	<wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>,
	<mkl-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
	<robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	<quentin.schulz-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
	<dev.kurt-yI9piX4KPfawT/RRk36CISFp6vIno51x@public.gmane.org>,
	<andrew-g2DYL2Zd6BY@public.gmane.org>,
	<socketcan-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
Subject: Re: [PATCH v4 1/4] can: dev: Add support for limiting configured bitrate
Date: Thu, 17 Aug 2017 12:54:48 -0500	[thread overview]
Message-ID: <b1082666-6cdf-374e-2c83-8d520e0996ad@ti.com> (raw)
In-Reply-To: <9a6f4fdf-a4f6-283b-0e5a-693cc7d263ef-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>



On 08/10/2017 05:05 AM, Sergei Shtylyov wrote:
> Hello!
> 
> On 8/10/2017 3:59 AM, Franklin S Cooper Jr wrote:
> 
>> Various CAN or CAN-FD IP may be able to run at a faster rate than
>> what the transceiver the CAN node is connected to. This can lead to
>> unexpected errors. However, CAN transceivers typically have fixed
>> limitations and provide no means to discover these limitations at
>> runtime. Therefore, add support for a can-transceiver node that
>> can be reused by other CAN peripheral drivers to determine for both
>> CAN and CAN-FD what the max bitrate that can be used. If the user
>> tries to configure CAN to pass these maximum bitrates it will throw
>> an error.
>>
>> Signed-off-by: Franklin S Cooper Jr <fcooper-l0cyMroinI0@public.gmane.org>
>> ---
>> Version 4 changes:
>> Used can-transceiver instead of fixed-transceiver.
>>
>>   drivers/net/can/dev.c   | 50
>> +++++++++++++++++++++++++++++++++++++++++++++++++
>>   include/linux/can/dev.h |  5 +++++
>>   2 files changed, 55 insertions(+)
>>
>> diff --git a/drivers/net/can/dev.c b/drivers/net/can/dev.c
>> index 365a8cc..372108f 100644
>> --- a/drivers/net/can/dev.c
>> +++ b/drivers/net/can/dev.c
> [...]
>> @@ -814,6 +815,39 @@ int open_candev(struct net_device *dev)
>>   }
>>   EXPORT_SYMBOL_GPL(open_candev);
>>   +#ifdef CONFIG_OF
>> +/*
>> + * Common function that can be used to understand the limitation of
>> + * a transceiver when it provides no means to determine these
>> limitations
>> + * at runtime.
>> + */
>> +void of_can_transceiver(struct net_device *dev)
>> +{
>> +    struct device_node *dn;
>> +    struct can_priv *priv = netdev_priv(dev);
>> +    struct device_node *np;
>> +    unsigned int max_bitrate;
>> +    int ret;
>> +
>> +    np = dev->dev.parent->of_node;
> 
>    I'd do that as an initializer.

Ok
> 
>> +
>> +    dn = of_get_child_by_name(np, "can-transceiver");
>> +    if (!dn)
>> +        return;
>> +
>> +    max_bitrate = 0;
>> +    ret = of_property_read_u32(dn, "max-bitrate", &max_bitrate);
> 
>    I'd initialize max_bitrate to 0 as iff of_property_read_u32() fails,
> it'll leave the variable unset...>
>> +
>> +    if (max_bitrate > 0) {
> 
>    You risk checking unset variable here.

Four lines up I am already setting max_bitrate to a default value of 0.

> 
>> +        priv->max_bitrate = max_bitrate;
>> +        priv->is_bitrate_limited = true;
>> +    } else if (ret != -EINVAL) {
>> +        netdev_warn(dev, "Invalid value for transceiver max bitrate\n");
>> +    }
>> +}
>> +EXPORT_SYMBOL(of_can_transceiver);
>> +#endif
>> +
>>   /*
>>    * Common close function for cleanup before the device gets closed.
>>    *
> [...]
> 
> MBR, Sergei
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-08-17 17:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-10  0:59 [PATCH v4 0/4] can: Support transceiver based bit rate limit Franklin S Cooper Jr
2017-08-10  0:59 ` [PATCH v4 1/4] can: dev: Add support for limiting configured bitrate Franklin S Cooper Jr
2017-08-10 10:05   ` Sergei Shtylyov
     [not found]     ` <9a6f4fdf-a4f6-283b-0e5a-693cc7d263ef-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2017-08-17 17:54       ` Franklin S Cooper Jr [this message]
2017-08-17 18:09         ` Sergei Shtylyov
     [not found]   ` <20170810005916.27163-2-fcooper-l0cyMroinI0@public.gmane.org>
2017-08-10 15:29     ` Marc Kleine-Budde
     [not found]       ` <4a96c6a8-b8c5-24a1-5e99-44751a0ae987-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2017-08-17 18:05         ` Franklin S Cooper Jr
     [not found] ` <20170810005916.27163-1-fcooper-l0cyMroinI0@public.gmane.org>
2017-08-10  0:59   ` [PATCH v4 2/4] dt-bindings: can: can-transceiver: Document new binding Franklin S Cooper Jr
2017-08-17 15:10     ` Rob Herring
2017-08-10  0:59 ` [PATCH v4 3/4] dt-bindings: can: m_can: Document new can transceiver binding Franklin S Cooper Jr
2017-08-17 15:10   ` Rob Herring
2017-08-10  0:59 ` [PATCH v4 4/4] can: m_can: Add call to of_can_transceiver Franklin S Cooper Jr

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=b1082666-6cdf-374e-2c83-8d520e0996ad@ti.com \
    --to=fcooper-l0cymroini0@public.gmane.org \
    --cc=andrew-g2DYL2Zd6BY@public.gmane.org \
    --cc=dev.kurt-yI9piX4KPfawT/RRk36CISFp6vIno51x@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mkl-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=quentin.schulz-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
    --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org \
    --cc=socketcan-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org \
    --cc=wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.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