All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: linux-can@vger.kernel.org
Subject: Re: [PATCH v2 1/3] can: flexcan: change RX-FIFO feature at runtime
Date: Wed, 5 Jan 2022 11:14:14 +0100	[thread overview]
Message-ID: <20220105101414.kg7mwp2uop6rsfbv@pengutronix.de> (raw)
In-Reply-To: <CABGWkvo+h2CASM7q8z3UXRofrY7enVXS6njFKnKyqRUjgkbB_A@mail.gmail.com>

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

On 05.01.2022 09:25:35, Dario Binacchi wrote:
> > Is the name "rx-fifo" acceptable? Can you think of a better name?
> 
> If I am not mistaken this series arises from the need to deactivate
> the RxFIFO only if it is acceptable not to receive the notification of
> RTR messages.

ACK

> I wonder if this can be made explicit to the user.

I was hoping that we can find a better string that better represents
what this option does.

> Do you think it makes sense to explicitly RTR ("rtr-notify") instead
> of RxFIFO (rx-fifo)? And if it makes sense to make it clear that it
> occurs at the expense of a smaller number of messages allocated for
> reception?

I see it the other way round, probably biased by the existing driver :)
The user wants to use more buffers at the expense of loosing the ability
to receive RTR messages.

I've talked to one of my colleges and we came to the conclusion that the
driver should present the user the option to opt out from RTR reception.

If the user has opted out from RTR reception the driver can do internal
optimization, such as switching from FIFO to mailbox mode.

What about "rtr-rx" or "rx-rtr"?

regards,
Marc

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2022-01-05 10:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 15:41 [PATCH v2 1/3] can: flexcan: change RX-FIFO feature at runtime Marc Kleine-Budde
2022-01-04 15:41 ` [PATCH v2 1/3] can: flexcan: move driver into separate sub directory Marc Kleine-Budde
2022-01-04 15:41 ` [PATCH v2 2/3] can: flexcan: allow to change quirks at runtime Marc Kleine-Budde
2022-01-04 15:41 ` [PATCH v2 3/3] can: flexcan: add ethtool support to change rx-fifo setting during runtime Marc Kleine-Budde
2022-01-05  8:22   ` Dario Binacchi
2022-01-05 10:18     ` Marc Kleine-Budde
2022-01-04 15:44 ` [PATCH v2 1/3] can: flexcan: change RX-FIFO feature at runtime Marc Kleine-Budde
2022-01-05  8:25 ` Dario Binacchi
2022-01-05  9:31   ` Marc Kleine-Budde
2022-01-05 10:14   ` Marc Kleine-Budde [this message]
2022-01-06 10:40     ` Dario Binacchi
2022-01-06 10:54       ` 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=20220105101414.kg7mwp2uop6rsfbv@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=linux-can@vger.kernel.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 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.