From: Dario Binacchi <dariobin@libero.it>
To: linux-kernel@vger.kernel.org
Cc: Alexander Stein <alexander.stein@systec-electronic.com>,
Federico Vaga <federico.vaga@gmail.com>,
Dario Binacchi <dariobin@libero.it>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Oliver Hartkopp <socketcan@hartkopp.net>,
Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
Wolfgang Grandegger <wg@grandegger.com>,
YueHaibing <yuehaibing@huawei.com>,
Zhang Qilong <zhangqilong3@huawei.com>,
linux-can@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH v2 0/6] can: c_can: add support to 64 message objects
Date: Thu, 25 Feb 2021 22:51:49 +0100 [thread overview]
Message-ID: <20210225215155.30509-1-dariobin@libero.it> (raw)
The D_CAN controller supports up to 128 messages. Until now the driver
only managed 32 messages although Sitara processors and DRA7 SOC can
handle 64.
The series was tested on a beaglebone board.
Note:
I have not changed the type of tx_field (belonging to the c_can_priv
structure) to atomic64_t because I think the atomic_t type has size
of at least 32 bits on x86 and arm, which is enough to handle 64
messages.
http://marc.info/?l=linux-can&m=139746476821294&w=2 reports the results
of tests performed just on x86 and arm architectures.
Changes in v2:
- Fix compiling error reported by kernel test robot.
- Add Reported-by tag.
- Pass larger size to alloc_candev() routine to avoid an additional
memory allocation/deallocation.
- Add message objects number to PCI driver data.
Dario Binacchi (6):
can: c_can: remove unused code
can: c_can: fix indentation
can: c_can: fix control interface used by c_can_do_tx
can: c_can: use 32-bit write to set arbitration register
can: c_can: prepare to up the message objects number
can: c_can: add support to 64 message objects
drivers/net/can/c_can/c_can.c | 77 +++++++++++++++-----------
drivers/net/can/c_can/c_can.h | 32 +++++------
drivers/net/can/c_can/c_can_pci.c | 6 +-
drivers/net/can/c_can/c_can_platform.c | 6 +-
4 files changed, 68 insertions(+), 53 deletions(-)
--
2.17.1
next reply other threads:[~2021-02-25 21:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 21:51 Dario Binacchi [this message]
2021-02-25 21:51 ` [PATCH v2 1/6] can: c_can: remove unused code Dario Binacchi
2021-02-25 21:51 ` [PATCH v2 2/6] can: c_can: fix indentation Dario Binacchi
2021-02-25 21:51 ` [PATCH v2 3/6] can: c_can: fix control interface used by c_can_do_tx Dario Binacchi
2021-02-26 8:44 ` Marc Kleine-Budde
2021-02-28 10:35 ` Dario Binacchi
2021-03-01 11:36 ` Marc Kleine-Budde
2021-03-01 17:38 ` Dario Binacchi
2021-02-25 21:51 ` [PATCH v2 4/6] can: c_can: use 32-bit write to set arbitration register Dario Binacchi
2021-02-25 21:51 ` [PATCH v2 5/6] can: c_can: prepare to up the message objects number Dario Binacchi
2021-02-26 8:33 ` Marc Kleine-Budde
2021-02-28 10:18 ` Dario Binacchi
2021-03-01 11:51 ` Marc Kleine-Budde
2021-02-26 9:21 ` Marc Kleine-Budde
2021-02-25 21:51 ` [PATCH v2 6/6] can: c_can: add support to 64 message objects Dario Binacchi
2021-02-26 8:43 ` Marc Kleine-Budde
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=20210225215155.30509-1-dariobin@libero.it \
--to=dariobin@libero.it \
--cc=alexander.stein@systec-electronic.com \
--cc=davem@davemloft.net \
--cc=federico.vaga@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=wg@grandegger.com \
--cc=yuehaibing@huawei.com \
--cc=zhangqilong3@huawei.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;
as well as URLs for NNTP newsgroup(s).