From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch 1/1] ARM: kirkwood: stop printk TCLK value at boot for DT boards
Date: Fri, 08 Nov 2013 10:37:34 +0100 [thread overview]
Message-ID: <527CB0DE.6020303@gmail.com> (raw)
In-Reply-To: <87vc03s0l1.fsf@lebrac.rtp-net.org>
On 11/08/2013 10:29 AM, Arnaud Patard (Rtp) wrote:
> Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> writes:
>> On 11/05/2013 07:09 PM, Arnaud Patard (Rtp) wrote:
>>> Commit 2326f04321a9 (ARM: kirkwood: convert to DT irqchip and clocksource)
>>> dropped the call to kirkwood_timer_init() when booting with DT.
>>> This results in kirkwood_tclk not being set and the boot message is now:
>>>
>>> Kirkwood: MV88F6281-A0, TCLK=0
>>>
>>> This patch modifies the message for printing only the kirkwood id,
>>> as it allows to detect if we're running A0/A1/... variants with a simple
>>> dmesg.
>>
>> for DT based booting we also have the "Machine" printed right above the
>> "Kirkwood" string. Don't you think, that we can remove the pr_info
>> completely?
>
> The Machine give some valuable information as one can load wrong dtb
> (already happened here). Moreover, it's a of thing (see
> of_flat_dt_match_machine) so not something that can be decided on
> kirkwookd side.
> About possible redundancy of informations between the "Kirkwood:" and
> the "Machine" lines, the former one gives the stepping. This allows to
> know easily if kwboot has a chance to work on the serial port.
Ok, I see there is a use for it. So,
Acked-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Sebastian
next prev parent reply other threads:[~2013-11-08 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 18:09 [patch 1/1] ARM: kirkwood: stop printk TCLK value at boot for DT boards Arnaud Patard (Rtp)
2013-11-08 9:00 ` Sebastian Hesselbarth
2013-11-08 9:09 ` Andrew Lunn
2013-11-08 9:29 ` Arnaud Patard (Rtp)
2013-11-08 9:37 ` Sebastian Hesselbarth [this message]
2013-11-08 9:44 ` Andrew Lunn
2013-11-24 3:13 ` Jason Cooper
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=527CB0DE.6020303@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).