linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: dts: r8a7794: add CAN clocks to device tree
Date: Tue, 15 Mar 2016 08:28:42 +0100	[thread overview]
Message-ID: <CAMuHMdVEoj5-ar0bNPB5XH7RtoR-v5bNDuZ87SwNzqvC670E2w@mail.gmail.com> (raw)
In-Reply-To: <20160314235659.GA23279@verge.net.au>

Hi Simon,

On Tue, Mar 15, 2016 at 12:56 AM, Simon Horman <horms@verge.net.au> wrote:
> On Mon, Mar 14, 2016 at 10:23:01AM +0100, Geert Uytterhoeven wrote:
>> On Mon, Mar 14, 2016 at 3:29 AM, Simon Horman
>> <horms+renesas@verge.net.au> wrote:
>> > --- a/arch/arm/boot/dts/r8a7794.dtsi
>> > +++ b/arch/arm/boot/dts/r8a7794.dtsi
>> > @@ -844,6 +844,24 @@
>> >                         clock-output-names = "extal";
>> >                 };
>> >
>> > +               /* External USB clock - can be overridden by the board */
>> > +               usb_extal_clk: usb_extal_clk {
>> > +                       compatible = "fixed-clock";
>> > +                       #clock-cells = <0>;
>> > +                       clock-frequency = <48000000>;
>> > +                       clock-output-names = "usb_extal";
>>
>> "clock-output-names" is optional these days, so please drop it.
>
> Thanks, I will drop it from this patch.
>
> Do we have a plan to remove it from existing nodes?
> Should I do a sweep of the Renesas DTS files?

That's up to you.

It's more churn, but from the other side, it avoids people copying deprecated
practices.

> And in particular, should it be removed from cpg_clocks ?

It's not optional for clocks with multiple outputs, cfr. the issues we had with
cpg_clocks on H3, before the advent of the CPG/MSSR driver.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2016-03-15  7:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14  2:29 [PATCH 0/2] ARM: dts: r8a7793: add CAN to device tree Simon Horman
2016-03-14  2:29 ` [PATCH 1/2] ARM: dts: r8a7794: add CAN clocks " Simon Horman
2016-03-14  9:23   ` Geert Uytterhoeven
2016-03-14 23:56     ` Simon Horman
2016-03-15  7:28       ` Geert Uytterhoeven [this message]
2016-03-15  8:02         ` Simon Horman
2016-03-14  2:29 ` [PATCH 2/2] ARM: dts: r8a7794: add CAN nodes " Simon Horman
2016-03-14  9:28   ` Geert Uytterhoeven
2016-03-15  0:23     ` Simon Horman

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=CAMuHMdVEoj5-ar0bNPB5XH7RtoR-v5bNDuZ87SwNzqvC670E2w@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --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).