From: hch@infradead.org (Christoph Hellwig)
To: linux-riscv@lists.infradead.org
Subject: [RFC 1/3] dt-bindings: Correct RISC-V's timebase-frequency
Date: Mon, 17 Sep 2018 07:20:17 -0700 [thread overview]
Message-ID: <20180917142017.GA15588@infradead.org> (raw)
In-Reply-To: <1536962096-233842-2-git-send-email-atish.patra@wdc.com>
On Fri, Sep 14, 2018 at 02:54:54PM -0700, Atish Patra wrote:
> From: Palmer Dabbelt <palmer@sifive.com>
>
> Someone must have read the device tree specification incorrectly,
> because we were putting timebase-frequency in the wrong place. This
> corrects the issue, moving it from
Last time this was brought up we actually had realy life DTs with
the timebase-frequency under cpus and not the invidual cpu node.
I think we need to just document both possibilities and live with
them.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Atish Patra <atish.patra@wdc.com>
Cc: palmer@sifive.com, linux-riscv@lists.infradead.org,
hch@infradead.org, mark.rutland@arm.com, robh@kernel.org,
Damien.LeMoal@wdc.com, marc.zyngier@arm.com, anup@brainfault.org,
linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: [RFC 1/3] dt-bindings: Correct RISC-V's timebase-frequency
Date: Mon, 17 Sep 2018 07:20:17 -0700 [thread overview]
Message-ID: <20180917142017.GA15588@infradead.org> (raw)
In-Reply-To: <1536962096-233842-2-git-send-email-atish.patra@wdc.com>
On Fri, Sep 14, 2018 at 02:54:54PM -0700, Atish Patra wrote:
> From: Palmer Dabbelt <palmer@sifive.com>
>
> Someone must have read the device tree specification incorrectly,
> because we were putting timebase-frequency in the wrong place. This
> corrects the issue, moving it from
Last time this was brought up we actually had realy life DTs with
the timebase-frequency under cpus and not the invidual cpu node.
I think we need to just document both possibilities and live with
them.
next prev parent reply other threads:[~2018-09-17 14:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 21:54 [RFC 0/3] Timer code cleanup Atish Patra
2018-09-14 21:54 ` Atish Patra
2018-09-14 21:54 ` [RFC 1/3] dt-bindings: Correct RISC-V's timebase-frequency Atish Patra
2018-09-14 21:54 ` Atish Patra
2018-09-17 14:20 ` Christoph Hellwig [this message]
2018-09-17 14:20 ` Christoph Hellwig
2018-09-18 2:26 ` Atish Patra
2018-09-18 2:26 ` Atish Patra
2018-09-14 21:54 ` [RFC 2/3] RISC-V:Support per-hart timebase-frequency Atish Patra
2018-09-14 21:54 ` Atish Patra
2018-09-17 14:23 ` Christoph Hellwig
2018-09-17 14:23 ` Christoph Hellwig
2018-09-18 2:23 ` Atish Patra
2018-09-18 2:23 ` Atish Patra
2018-09-29 0:20 ` Palmer Dabbelt
2018-09-29 0:20 ` Palmer Dabbelt
2018-09-29 0:20 ` Palmer Dabbelt
2018-09-14 21:54 ` [RFC 3/3] RISC-V: Remove per cpu clocksource Atish Patra
2018-09-14 21:54 ` Atish Patra
2018-09-17 14:35 ` Christoph Hellwig
2018-09-17 14:35 ` Christoph Hellwig
2018-09-17 14:52 ` Thomas Gleixner
2018-09-17 14:52 ` Thomas Gleixner
2018-09-17 15:01 ` Christoph Hellwig
2018-09-17 15:01 ` Christoph Hellwig
2018-09-17 15:04 ` Thomas Gleixner
2018-09-17 15:04 ` Thomas Gleixner
2018-09-17 15:54 ` Anup Patel
2018-09-17 15:54 ` Anup Patel
2018-09-17 18:32 ` Atish Patra
2018-09-17 18:32 ` Atish Patra
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=20180917142017.GA15588@infradead.org \
--to=hch@infradead.org \
--cc=linux-riscv@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 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.