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: Sven Schuchmann <schuchmann@schleissheimer.de>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: mcp251xfd No Oscillator (clock) defined
Date: Sun, 6 Dec 2020 20:26:25 +0100	[thread overview]
Message-ID: <20201206192625.GB15319@x1.vandijck-laurijssen.be> (raw)
In-Reply-To: <611813e9-943a-33be-4e9b-5cb1397ac5d9@pengutronix.de>

On Sun, 06 Dec 2020 11:32:39 +0100, Marc Kleine-Budde wrote:
> On 12/6/20 11:18 AM, Sven Schuchmann wrote:
> > 
> > $ sudo dtoverlay spi0-1cs cs0_pin=24
> > $ sudo dtoverlay mcp251xfd spi0-1 oscillator=40000000 speed=20000000 interrupt=18
> 
> Better add the overlays statically in the bootloader via config.txt:

why is it better in the bootloader than from linux?

I personnaly favor loading overlays from linux, where there are way more
possibilities to determing which overlays to load.

Kurt

  parent reply	other threads:[~2020-12-06 19:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-06 10:18 mcp251xfd No Oscillator (clock) defined Sven Schuchmann
2020-12-06 10:32 ` Marc Kleine-Budde
2020-12-06 12:40   ` AW: " Sven Schuchmann
2020-12-06 12:57     ` Marc Kleine-Budde
2020-12-06 14:56     ` Patrick Menschel
2020-12-06 16:28       ` AW: " Sven Schuchmann
2020-12-06 18:31       ` Marc Kleine-Budde
2020-12-06 19:15         ` Patrick Menschel
2020-12-06 19:26   ` Kurt Van Dijck [this message]
2020-12-06 19:34     ` Marc Kleine-Budde
2020-12-06 19:56       ` AW: " Sven Schuchmann
2020-12-06 20:14         ` Marc Kleine-Budde
2020-12-06 20:36           ` AW: " Sven Schuchmann
2020-12-06 20:48             ` Marc Kleine-Budde
2020-12-06 21:23               ` AW: " Sven Schuchmann
2020-12-06 22:00                 ` Marc Kleine-Budde
2020-12-07  9:35                   ` AW: " Sven Schuchmann

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=20201206192625.GB15319@x1.vandijck-laurijssen.be \
    --to=dev.kurt@vandijck-laurijssen.be \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=schuchmann@schleissheimer.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.