From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Chris Brandt <Chris.Brandt@renesas.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: r7s72100: Add SPIBSC clocks
Date: Mon, 10 Feb 2020 13:10:54 +0100 [thread overview]
Message-ID: <CAMuHMdWsDiNaW-cX-C4SNNJep8LBzCANR-jsJJ3i2H-1Z=ytYg@mail.gmail.com> (raw)
In-Reply-To: <TY1PR01MB1562D7E98F1200B868A91F928A190@TY1PR01MB1562.jpnprd01.prod.outlook.com>
Hi Chris,
On Mon, Feb 10, 2020 at 12:31 PM Chris Brandt <Chris.Brandt@renesas.com> wrote:
> On Mon, Feb 10, 2020, Geert Uytterhoeven wrote:
> > However, I believe I cannot queue this in renesas-devel yet, as to avoid
> > a regression, the flash node in r7s72100-gr-peach.dts should gain
> > appropriate clock and power-domains properties.
> > And to avoid bisection issues, that should be combined with this patch,
> > right?
>
> Are you saying a patch series? Or 1 patch that edits both files?
I meant a single patch that modifies both files.
If the clocks go in first, the SPIBSC clock will be disabled.
If the FLASH update goes in first, the SPIBSC clock cannot be found.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@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
prev parent reply other threads:[~2020-02-10 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 16:27 [PATCH] ARM: dts: r7s72100: Add SPIBSC clocks Chris Brandt
2020-02-10 8:13 ` Geert Uytterhoeven
2020-02-10 11:31 ` Chris Brandt
2020-02-10 12:10 ` Geert Uytterhoeven [this message]
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='CAMuHMdWsDiNaW-cX-C4SNNJep8LBzCANR-jsJJ3i2H-1Z=ytYg@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=Chris.Brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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).