public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Schultz <d.schultz@phytec.de>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, w.egorov@phytec.de
Subject: Re: [PATCH] ARM: dts: rockchip: Add dp83867 CLK_OUT muxing
Date: Tue, 6 Mar 2018 10:59:54 +0100	[thread overview]
Message-ID: <fe1d445e-e9ac-452f-e990-d4bc17bd3355@phytec.de> (raw)
In-Reply-To: <2707703.8mZIocJ1Ne@diego>

Hi,


On 03/05/2018 10:08 PM, Heiko Stübner wrote:
> Am Montag, 5. März 2018, 21:25:30 CET schrieb Heiko Stübner:
>> Am Montag, 5. März 2018, 13:45:11 CET schrieb Daniel Schultz:
>>> The CLK_O_SEL default is synchronous to XI input clock, which is 25 MHz.
>>> Set CLK_O_SEL to channel A transmit clock so we have 125 MHz on CLK_OUT.
>>>
>>> Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
>> applied for 4.17
> had to move it to 4.18 though.
>
> The change to the dt-binding header goes through the networking
> tree and will only get merged for 4.17-rc1 .
>
> So devicetree changes in a different branch aren't available at this
> point.
>
> One commonly practiced alternative is that you provide a v2
> with the actual hex values instead of the constants for 4.17
> and a follow-up patch replacing them with the constants
> that I can apply for 4.18.
It's not so urgent because the RK818 PMIC currently does not boot and 
the patch for this problem is also pending.

-- 
Mit freundlichen Grüßen,
With best regards,
   Daniel Schultz

      reply	other threads:[~2018-03-06  9:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05 12:45 [PATCH] ARM: dts: rockchip: Add dp83867 CLK_OUT muxing Daniel Schultz
2018-03-05 14:15 ` Heiko Stuebner
2018-03-05 15:57   ` Daniel Schultz
2018-03-05 17:04     ` Heiko Stübner
2018-03-05 20:25 ` Heiko Stübner
2018-03-05 21:08   ` Heiko Stübner
2018-03-06  9:59     ` Daniel Schultz [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=fe1d445e-e9ac-452f-e990-d4bc17bd3355@phytec.de \
    --to=d.schultz@phytec.de \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=w.egorov@phytec.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