From: Andi Shyti <andi@etezian.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
Alim Akhtar <alim.akhtar@samsung.com>,
Arnd Bergmann <arnd@arndb.de>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Pankaj Dubey <pankaj.dubey@samsung.com>,
Seung-Woo Kim <sw0312.kim@samsung.com>,
linux-kernel@vger.kernel.org, Inki Dae <inki.dae@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Rob Herring <robh+dt@kernel.org>, Kukjin Kim <kgene@kernel.org>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH v3] dt-bindings: arm: Explicitly mark Samsung Exynos SoC as unstable
Date: Fri, 31 Aug 2018 13:40:48 +0300 [thread overview]
Message-ID: <20180831104048.GA6545@jack.zhora.eu> (raw)
In-Reply-To: <20180830180205.18121-1-krzk@kernel.org>
Hi Krzysztof,
On Thu, Aug 30, 2018 at 08:02:05PM +0200, Krzysztof Kozlowski wrote:
> Samsung Exynos SoCs and boards related bindings evolved since the initial
> introduction, but initially the bindings were minimal and a bit incomplete
> (they never described all the hardware modules available in the SoCs).
> Since then some significant (not fully compatible) changes have been
> already committed a few times (like gpio replaced by pinctrl, display ddc,
> mfc reserved memory, some core clocks added to various hardware modules,
> added more required nodes).
>
> On the other side there are no boards which have device tree embedded in
> the bootloader. Device tree blob is always compiled from the kernel tree
> and updated together with the kernel image.
>
> Thus to avoid further adding a bunch of workarounds for old/missing
> bindings, make development of new platforms easier and allow to make
> cleanup of the existing code and device tree files, lets mark some
> Samsung Exynos SoC platform bindings as unstable. This means that
> bindings can may change at any time and users should use the dtb file
^^^^^^^
you have a typo here, other than that I agree with the patch:
Acked-by: Andi Shyti <andi@etezian.org>
Thanks,
Andi
WARNING: multiple messages have this Message-ID (diff)
From: andi@etezian.org (Andi Shyti)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] dt-bindings: arm: Explicitly mark Samsung Exynos SoC as unstable
Date: Fri, 31 Aug 2018 13:40:48 +0300 [thread overview]
Message-ID: <20180831104048.GA6545@jack.zhora.eu> (raw)
In-Reply-To: <20180830180205.18121-1-krzk@kernel.org>
Hi Krzysztof,
On Thu, Aug 30, 2018 at 08:02:05PM +0200, Krzysztof Kozlowski wrote:
> Samsung Exynos SoCs and boards related bindings evolved since the initial
> introduction, but initially the bindings were minimal and a bit incomplete
> (they never described all the hardware modules available in the SoCs).
> Since then some significant (not fully compatible) changes have been
> already committed a few times (like gpio replaced by pinctrl, display ddc,
> mfc reserved memory, some core clocks added to various hardware modules,
> added more required nodes).
>
> On the other side there are no boards which have device tree embedded in
> the bootloader. Device tree blob is always compiled from the kernel tree
> and updated together with the kernel image.
>
> Thus to avoid further adding a bunch of workarounds for old/missing
> bindings, make development of new platforms easier and allow to make
> cleanup of the existing code and device tree files, lets mark some
> Samsung Exynos SoC platform bindings as unstable. This means that
> bindings can may change at any time and users should use the dtb file
^^^^^^^
you have a typo here, other than that I agree with the patch:
Acked-by: Andi Shyti <andi@etezian.org>
Thanks,
Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi Shyti <andi@etezian.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Kukjin Kim <kgene@kernel.org>,
Pankaj Dubey <pankaj.dubey@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Chanwoo Choi <cw00.choi@samsung.com>,
Seung-Woo Kim <sw0312.kim@samsung.com>,
Inki Dae <inki.dae@samsung.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH v3] dt-bindings: arm: Explicitly mark Samsung Exynos SoC as unstable
Date: Fri, 31 Aug 2018 13:40:48 +0300 [thread overview]
Message-ID: <20180831104048.GA6545@jack.zhora.eu> (raw)
In-Reply-To: <20180830180205.18121-1-krzk@kernel.org>
Hi Krzysztof,
On Thu, Aug 30, 2018 at 08:02:05PM +0200, Krzysztof Kozlowski wrote:
> Samsung Exynos SoCs and boards related bindings evolved since the initial
> introduction, but initially the bindings were minimal and a bit incomplete
> (they never described all the hardware modules available in the SoCs).
> Since then some significant (not fully compatible) changes have been
> already committed a few times (like gpio replaced by pinctrl, display ddc,
> mfc reserved memory, some core clocks added to various hardware modules,
> added more required nodes).
>
> On the other side there are no boards which have device tree embedded in
> the bootloader. Device tree blob is always compiled from the kernel tree
> and updated together with the kernel image.
>
> Thus to avoid further adding a bunch of workarounds for old/missing
> bindings, make development of new platforms easier and allow to make
> cleanup of the existing code and device tree files, lets mark some
> Samsung Exynos SoC platform bindings as unstable. This means that
> bindings can may change at any time and users should use the dtb file
^^^^^^^
you have a typo here, other than that I agree with the patch:
Acked-by: Andi Shyti <andi@etezian.org>
Thanks,
Andi
next prev parent reply other threads:[~2018-08-31 10:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 18:02 [PATCH v3] dt-bindings: arm: Explicitly mark Samsung Exynos SoC as unstable Krzysztof Kozlowski
2018-08-30 18:02 ` Krzysztof Kozlowski
2018-08-31 10:40 ` Andi Shyti [this message]
2018-08-31 10:40 ` Andi Shyti
2018-08-31 10:40 ` Andi Shyti
2018-08-31 14:02 ` Krzysztof Kozlowski
2018-08-31 14:02 ` Krzysztof Kozlowski
2018-09-10 19:55 ` Rob Herring
2018-09-10 19:55 ` Rob Herring
2018-09-17 15:57 ` Krzysztof Kozlowski
2018-09-17 15:57 ` Krzysztof Kozlowski
2018-09-23 13:46 ` Olof Johansson
2018-09-23 13:46 ` Olof Johansson
2018-09-24 17:16 ` Krzysztof Kozlowski
2018-09-24 17:16 ` Krzysztof Kozlowski
2018-09-26 3:55 ` Olof Johansson
2018-09-26 3:55 ` Olof Johansson
2018-09-26 14:04 ` Rob Herring
2018-09-26 14:04 ` Rob Herring
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=20180831104048.GA6545@jack.zhora.eu \
--to=andi@etezian.org \
--cc=alim.akhtar@samsung.com \
--cc=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=inki.dae@samsung.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=pankaj.dubey@samsung.com \
--cc=robh+dt@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=sw0312.kim@samsung.com \
/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.