All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Gherzan <andrei@gherzan.ro>
To: Trevor Woerner <twoerner@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-raspberrypi][PATCH v2 2/2] raspberrypi3: set core frequency
Date: Wed, 13 Apr 2016 04:51:47 +0200	[thread overview]
Message-ID: <20160413025147.GE22139@resin> (raw)
In-Reply-To: <1460411685-12573-2-git-send-email-twoerner@gmail.com>

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

On Mon, Apr 11, 2016 at 05:54:45PM -0400, Trevor Woerner wrote:
> Pegging the core frequency at 250 avoids any fluctuations of the baud rate on
> the console.
>
> See:
> 	https://www.raspberrypi.org/forums/viewtopic.php?f=107&t=138223
>
> Signed-off-by: Trevor Woerner <twoerner@gmail.com>
> ---
>  conf/machine/raspberrypi3.conf | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf
> index cb6056e..81301c3 100644
> --- a/conf/machine/raspberrypi3.conf
> +++ b/conf/machine/raspberrypi3.conf
> @@ -9,3 +9,4 @@ MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-brcm43430"
>  include conf/machine/raspberrypi2.conf
>
>  SERIAL_CONSOLE = "115200 ttyS0"
> +CORE_FREQ = "250"

I think it would be better to use enable_uart in config.txt for this
situation. Setting it to 1 would work on all the rpi versions with
current firmware (to be tested).

--
Andrei Gherzan

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

  reply	other threads:[~2016-04-13  2:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11 21:54 [meta-raspberrypi][PATCH v2 1/2] raspberrypi3: serial console Trevor Woerner
2016-04-11 21:54 ` [meta-raspberrypi][PATCH v2 2/2] raspberrypi3: set core frequency Trevor Woerner
2016-04-13  2:51   ` Andrei Gherzan [this message]
2016-04-13  2:20 ` [meta-raspberrypi][PATCH v2 1/2] raspberrypi3: serial console Andrei Gherzan
2016-04-13  2:28   ` Andrei Gherzan
2016-04-13 16:41   ` Trevor Woerner

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=20160413025147.GE22139@resin \
    --to=andrei@gherzan.ro \
    --cc=twoerner@gmail.com \
    --cc=yocto@yoctoproject.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.