From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Franklin S Cooper Jr <fcooper@ti.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
netdev@vger.kernel.org, linux-can@vger.kernel.org,
wg@grandegger.com, mkl@pengutronix.de, robh+dt@kernel.org,
quentin.schulz@free-electrons.com,
dev.kurt@vandijck-laurijssen.be, andrew@lunn.ch,
socketcan@hartkopp.net
Subject: Re: [PATCH v4 1/4] can: dev: Add support for limiting configured bitrate
Date: Thu, 17 Aug 2017 21:09:43 +0300 [thread overview]
Message-ID: <c6f5667d-f5c0-956d-7067-87a4de0d79c7@cogentembedded.com> (raw)
In-Reply-To: <b1082666-6cdf-374e-2c83-8d520e0996ad@ti.com>
Hello!
On 08/17/2017 08:54 PM, 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@ti.com>
>>> ---
>>> 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.
Oops, sorry. Don't know how I missed that. Better done as initializer too
though...
MBR, Sergei
next prev parent reply other threads:[~2017-08-17 18:09 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
2017-08-17 17:54 ` Franklin S Cooper Jr
2017-08-17 18:09 ` Sergei Shtylyov [this message]
2017-08-10 15:29 ` Marc Kleine-Budde
2017-08-17 18:05 ` Franklin S Cooper Jr
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=c6f5667d-f5c0-956d-7067-87a4de0d79c7@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=andrew@lunn.ch \
--cc=dev.kurt@vandijck-laurijssen.be \
--cc=devicetree@vger.kernel.org \
--cc=fcooper@ti.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=quentin.schulz@free-electrons.com \
--cc=robh+dt@kernel.org \
--cc=socketcan@hartkopp.net \
--cc=wg@grandegger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®