From: Heiko Stuebner <heiko@sntech.de>
To: Douglas Anderson <dianders@chromium.org>
Cc: linux-rockchip@lists.infradead.org, briannorris@chromium.org,
mka@chromium.org, amstan@chromium.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: rockchip: Remove bogus 'i2s_clk_out' from rk3288-veyron-mickey
Date: Tue, 07 May 2019 14:01:01 +0200 [thread overview]
Message-ID: <2275852.0beATWnSof@phil> (raw)
In-Reply-To: <20190503234814.230901-1-dianders@chromium.org>
Am Samstag, 4. Mai 2019, 01:48:14 CEST schrieb Douglas Anderson:
> The rk3288-veyron-mickey device tree overrides the default "i2s" clock
> settings to add the clock for "i2s_clk_out".
>
> That clock is only present in the bindings downstream Chrome OS 3.14
> tree. Upstream the i2s port bindings doesn't specify that as a
> possible clock.
>
> Let's remove it.
>
> NOTE: for other rk3288-veyron devices this clock is consumed by
> 'maxim,max98090'. Presumably if this clock is needed for mickey it'll
> need to be consumed by something similar.
>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
applied for 5.3 with Matthias' rb.
Thanks
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Douglas Anderson <dianders@chromium.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, amstan@chromium.org,
briannorris@chromium.org, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
linux-rockchip@lists.infradead.org, mka@chromium.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: rockchip: Remove bogus 'i2s_clk_out' from rk3288-veyron-mickey
Date: Tue, 07 May 2019 14:01:01 +0200 [thread overview]
Message-ID: <2275852.0beATWnSof@phil> (raw)
In-Reply-To: <20190503234814.230901-1-dianders@chromium.org>
Am Samstag, 4. Mai 2019, 01:48:14 CEST schrieb Douglas Anderson:
> The rk3288-veyron-mickey device tree overrides the default "i2s" clock
> settings to add the clock for "i2s_clk_out".
>
> That clock is only present in the bindings downstream Chrome OS 3.14
> tree. Upstream the i2s port bindings doesn't specify that as a
> possible clock.
>
> Let's remove it.
>
> NOTE: for other rk3288-veyron devices this clock is consumed by
> 'maxim,max98090'. Presumably if this clock is needed for mickey it'll
> need to be consumed by something similar.
>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
applied for 5.3 with Matthias' rb.
Thanks
Heiko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-05-07 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 23:48 [PATCH] ARM: dts: rockchip: Remove bogus 'i2s_clk_out' from rk3288-veyron-mickey Douglas Anderson
2019-05-03 23:48 ` Douglas Anderson
2019-05-03 23:58 ` Matthias Kaehlcke
2019-05-03 23:58 ` Matthias Kaehlcke
2019-05-03 23:58 ` Matthias Kaehlcke
2019-05-07 12:01 ` Heiko Stuebner [this message]
2019-05-07 12:01 ` Heiko Stuebner
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=2275852.0beATWnSof@phil \
--to=heiko@sntech.de \
--cc=amstan@chromium.org \
--cc=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.org \
--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 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.