From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Klaus Goger
<klaus.goger-SN7IsUiht6C/RdPyistoZJqQE7yCjDx5@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v3 0/2] arm64: dts: rockchip: enable I2S codec on rk3399-puma-haikou
Date: Mon, 19 Feb 2018 09:47:58 +0100 [thread overview]
Message-ID: <1877328.7ff6v7Dvk9@phil> (raw)
In-Reply-To: <20180219081855.34400-1-klaus.goger-SN7IsUiht6C/RdPyistoZJqQE7yCjDx5@public.gmane.org>
Am Montag, 19. Februar 2018, 09:18:52 CET schrieb Klaus Goger:
> Enables the audio codec on the Haikou Baseboard when used with a RK3399-Q7.
>
> Changes in v3:
> - split i2s0 move from rk3399-puma-haikou.dts to rk3399-puma.dtsi into it's
> own patch
> - use dasheѕ in node names
> - added missing vin-supply properties to regulators
> had to add an additional regulator to model this correctly
> - simple overwrite pins in i2s0_2ch_bus instead of deleting and redefining
> the node
applied both patches for 4.17, only moved the oscillator node a bit
upwards in the file.
Thanks
Heiko
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2018-02-19 8:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 8:18 [PATCH v3 0/2] arm64: dts: rockchip: enable I2S codec on rk3399-puma-haikou Klaus Goger
[not found] ` <20180219081855.34400-1-klaus.goger-SN7IsUiht6C/RdPyistoZJqQE7yCjDx5@public.gmane.org>
2018-02-19 8:18 ` [PATCH v3 1/2] arm64: dts: rockchip: move i2s0 node from baseboard to SoM Klaus Goger
2018-02-19 8:18 ` [PATCH v3 2/2] arm64: dts: rockchip: enable I2S codec on rk3399-puma-haikou Klaus Goger
2018-02-19 8:47 ` Heiko Stuebner [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=1877328.7ff6v7Dvk9@phil \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=klaus.goger-SN7IsUiht6C/RdPyistoZJqQE7yCjDx5@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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