All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anssi Hannula <anssi.hannula@bitwise.fi>
To: Shubhrajyoti Datta <shubhrajyoti.datta@gmail.com>
Cc: wg@grandegger.com, mkl@pengutronix.de,
	Michal Simek <michal.simek@xilinx.com>,
	linux-can@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 3/3] can: xilinx_can: add support for Xilinx CAN FD core
Date: Mon, 10 Sep 2018 15:45:51 +0300	[thread overview]
Message-ID: <cabc9821-3bb3-7709-d6ac-97bb12ba68e1@bitwise.fi> (raw)
In-Reply-To: <CAKfKVtE2Q0k9LLL-tja1Z8SL2i83sQrBo6BbxoM1tgCRZ3004Q@mail.gmail.com>

Hi,

On 10.9.2018 15:14, Shubhrajyoti Datta wrote:
> On Fri, Jul 6, 2018 at 7:50 PM Anssi Hannula <anssi.hannula@bitwise.fi> wrote:
>> Add support for Xilinx CAN FD core.
>>
>> The major difference from the previously supported cores is that there
>> are TX mailboxes instead of a TX FIFO and the RX FIFO access method is
>> different.
>>
>> We only transmit one frame at a time to prevent the HW from reordering
>> frames (it uses CAN ID priority order).
>>
>> Support for CAN FD protocol is not added yet.
>>
>> v2: Removed unnecessary "rx-mode" DT property and wrapped some long
>>     lines.
>>
>> Signed-off-by: Anssi Hannula <anssi.hannula@bitwise.fi>
>> Cc: Michal Simek <michal.simek@xilinx.com>
>> ---
>>  drivers/net/can/xilinx_can.c | 303 ++++++++++++++++++++++++++++++++++++-------
>>  1 file changed, 259 insertions(+), 44 deletions(-)
[...]
>>
>> +static const struct can_bittiming_const xcan_bittiming_const_canfd = {
>> +       .name = DRIVER_NAME,
>> +       .tseg1_min = 1,
>> +       .tseg1_max = 64,
>> +       .tseg2_min = 1,
>> +       .tseg2_max = 16,
>> +       .sjw_max = 16,
>> +       .brp_min = 1,
>> +       .brp_max = 256,
>> +       .brp_inc = 1,
>> +};
> Where is this used?
[...]
>
>> +
>> +static const struct xcan_devtype_data xcan_canfd_data = {
>> +       .flags = XCAN_FLAG_EXT_FILTERS |
>> +                XCAN_FLAG_RXMNF |
>> +                XCAN_FLAG_TX_MAILBOXES |
>> +                XCAN_FLAG_RX_FIFO_MULTI,
>> +       .bittiming_const = &xcan_bittiming_const,
> Did you intend to use xcan_bittiming_const_canfd here ?
>

Yes, good catch. I'll test on HW and then post a patch, or you can do so
if you have one ready already.

-- 
Anssi Hannula / Bitwise Oy
+358 503803997

  reply	other threads:[~2018-09-10 12:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06 14:18 [PATCH 0/3 v2] can: xilinx_can: CAN FD core support Anssi Hannula
2018-07-06 14:18 ` [PATCH 1/3] dt-bindings: can: xilinx_can: add Xilinx CAN FD bindings Anssi Hannula
2018-07-20 13:49   ` Rob Herring
2018-07-06 14:18 ` [PATCH 2/3] can: xilinx_can: refactor code in preparation for CAN FD support Anssi Hannula
2018-07-06 14:18 ` [PATCH 3/3] can: xilinx_can: add support for Xilinx CAN FD core Anssi Hannula
2018-09-10 12:14   ` Shubhrajyoti Datta
2018-09-10 12:45     ` Anssi Hannula [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-27 14:34 [PATCH 0/3] can: xilinx_can: CAN FD core support Anssi Hannula
2018-06-27 14:34 ` [PATCH 3/3] can: xilinx_can: add support for Xilinx CAN FD core Anssi Hannula

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=cabc9821-3bb3-7709-d6ac-97bb12ba68e1@bitwise.fi \
    --to=anssi.hannula@bitwise.fi \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=michal.simek@xilinx.com \
    --cc=mkl@pengutronix.de \
    --cc=robh+dt@kernel.org \
    --cc=shubhrajyoti.datta@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.