All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kurt Van Dijck <dev.kurt@vandijck-laurijssen.be>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org
Subject: Re: [PATCH 3/3] can-calc-bittiming: add mcan
Date: Thu, 24 Jun 2021 12:57:31 +0200	[thread overview]
Message-ID: <20210624105731.GB21224@x1.vandijck-laurijssen.be> (raw)
In-Reply-To: <20210624105005.2kgj6o5hwskl6rqo@pengutronix.de>

On Thu, 24 Jun 2021 12:50:05 +0200, Marc Kleine-Budde wrote:
> On 24.06.2021 05:19:54, Kurt Van Dijck wrote:
> > Signed-off-by: Kurt Van Dijck <dev.kurt@vandijck-laurijssen.be>
> > ---
> > +	}, {
> > +		.bittiming_const = {
> > +			.name = "mcan",
> 
> This is for mcan > v3.1

I don't have any earlier.
Can I just solve by putting "mcan-v3.1+"?

> 
> > +			.tseg1_min = 1,
> > +			.tseg1_max = 256,
> > +			.tseg2_min = 1,
> 
> I just re-chcked the datasheet, and tseg{1,2} min are actually 2.

Will adapt.
I clearly didn't pay enough attention to the lower limits.

> 
> > +			.tseg2_max = 128,
> > +			.sjw_max = 128,
> > +			.brp_min = 1,
> > +			.brp_max = 512,
> > +			.brp_inc = 1,
> > +		},
> > +		.ref_clk = {
> > +			{ .clk = 40000000, },
> > +		},
> > +		.printf_btr = printf_btr_mcan,
> >  	},
> >  };
> 
> Marc

btw, I just noticed I already have can-utils in my github account, I'll
create a Merge-Request for this V2 too, if you like.

Kurt

  reply	other threads:[~2021-06-24 10:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24  3:19 [PATCH 1/3] can-calc-bittiming: add stm32 bxcan Kurt Van Dijck
2021-06-24  3:19 ` [PATCH 2/3] can-calc-bittiming: add c_can Kurt Van Dijck
2021-06-24  3:19 ` [PATCH 3/3] can-calc-bittiming: add mcan Kurt Van Dijck
2021-06-24 10:50   ` Marc Kleine-Budde
2021-06-24 10:57     ` Kurt Van Dijck [this message]
2021-06-24 11:12       ` Marc Kleine-Budde
2021-06-24 11:15       ` Marc Kleine-Budde
2021-06-24  6:20 ` [PATCH 1/3] can-calc-bittiming: add stm32 bxcan Marc Kleine-Budde
2021-06-24 10:37   ` Kurt Van Dijck
2021-06-24 10:40     ` 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=20210624105731.GB21224@x1.vandijck-laurijssen.be \
    --to=dev.kurt@vandijck-laurijssen.be \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    /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.