mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org, Alexey Galakhov <agalakhov@gmail.com>
Subject: Re: [PATCH] Force set console baudrate
Date: Wed, 10 Jul 2013 02:57:51 +0800	[thread overview]
Message-ID: <5C73F356-67C8-4D18-B0B8-3D0BE89794A7@jcrosoft.com> (raw)
In-Reply-To: <20130709174333.GY516@pengutronix.de>


On Jul 10, 2013, at 1:43 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:

> On Tue, Jul 09, 2013 at 09:22:10PM +0600, Alexey Galakhov wrote:
>> Most serial drivers require setbrg() to be called at least once. Call them
>> just after the device has been added.
>> 
>> Signed-off-by: Alexey Galakhov <agalakhov@gmail.com>

This is wrong if you do this at boot which means you force the same baudrate
on all the console

We must do this only is enable by default of via shell

and some console may not need the setbrg call back (keyboard or fbdev as example)

Also if we want to use a rs232 for controlling a mcu the baud rate may not be the
CONFIG_BAUDRATE

so force it at register is wrong

Best Regards,
J.
> 
> Applied, thanks.
> 
> Sascha
> 
>> ---
>> common/console.c |    1 +
>> 1 file changed, 1 insertion(+)
>> 
>> diff --git a/common/console.c b/common/console.c
>> index a0a06f6..abf5322 100644
>> --- a/common/console.c
>> +++ b/common/console.c
>> @@ -147,6 +147,7 @@ int console_register(struct console_device *newcdev)
>> 		newcdev->baudrate = CONFIG_BAUDRATE;
>> 		dev_add_param_int(dev, "baudrate", console_baudrate_set,
>> 			NULL, &newcdev->baudrate, "%u", newcdev);
>> +		newcdev->setbrg(newcdev, newcdev->baudrate);
>> 	}
>> 
>> 	dev_add_param(dev, "active", console_std_set, NULL, 0);
>> -- 
>> 1.7.10.4
>> 
>> 
>> _______________________________________________
>> barebox mailing list
>> barebox@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/barebox
>> 
> 
> -- 
> Pengutronix e.K.                           |                             |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2013-07-09 18:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09 15:22 Alexey Galakhov
2013-07-09 17:43 ` Sascha Hauer
2013-07-09 18:57   ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2013-07-09 20:09     ` Alexey Galakhov
2013-07-10  8:07       ` Jean-Christophe PLAGNIOL-VILLARD
2013-07-10  8:36         ` Alexey Galakhov
2013-07-10  9:01           ` Sascha Hauer
2013-07-10  9:36             ` Alexey Galakhov
2013-07-10 10:15             ` [PATCH 1/2] Revert "Force set console baudrate" Alexey Galakhov
2013-07-10 10:15               ` [PATCH 2/2] Force set console baudrate at enable time Alexey Galakhov
2013-07-10 21:28                 ` Sascha Hauer
2013-07-11  7:13                   ` Alexey Galakhov

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=5C73F356-67C8-4D18-B0B8-3D0BE89794A7@jcrosoft.com \
    --to=plagnioj@jcrosoft.com \
    --cc=agalakhov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox