[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <414faffd-cbe3-a784-1f6f-4e2eb325be58@canonical.com>
Date: Wed, 22 Dec 2021 12:33:46 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To: Sam Protsenko <semen.protsenko@...aro.org>
Cc: Jaewon Kim <jaewon02.kim@...sung.com>,
Chanho Park <chanho61.park@...sung.com>,
David Virag <virag.david003@...il.com>,
Youngmin Nam <youngmin.nam@...sung.com>,
Tomasz Figa <tomasz.figa@...il.com>,
Chanwoo Choi <cw00.choi@...sung.com>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Daniel Palmer <daniel@...f.com>,
Hao Fang <fanghao11@...wei.com>,
linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org,
Rob Herring <robh+dt@...nel.org>,
Sylwester Nawrocki <s.nawrocki@...sung.com>
Subject: Re: [PATCH v5 1/2] arm64: dts: exynos: Add initial Exynos850 SoC
support
On 21/12/2021 15:30, Sam Protsenko wrote:
> On Tue, 21 Dec 2021 at 16:24, Sam Protsenko <semen.protsenko@...aro.org> wrote:
>>
(...)
>> diff --git a/arch/arm64/boot/dts/exynos/exynos850.dtsi b/arch/arm64/boot/dts/exynos/exynos850.dtsi
>> new file mode 100644
>> index 000000000000..2abbb972b610
>> --- /dev/null
>> +++ b/arch/arm64/boot/dts/exynos/exynos850.dtsi
>> @@ -0,0 +1,759 @@
>> +// SPDX-License-Identifier: GPL-2.0
>> +/*
>> + * Samsung Exynos850 SoC device tree source
>> + *
>> + * Copyright (C) 2018 Samsung Electronics Co., Ltd.
>> + * Copyright (C) 2021 Linaro Ltd.
>> + *
>> + * Samsung Exynos850 SoC device nodes are listed in this file.
>> + * Exynos850 based board files can include this file and provide
>> + * values for board specific bindings.
>> + */
>> +
>> +#include <dt-bindings/clock/exynos850.h>
>> +#include <dt-bindings/interrupt-controller/arm-gic.h>
>> +#include <dt-bindings/soc/samsung,exynos-usi.h>
>> +
>> +/* TODO: Remove this once corresponding clock bindings are added */
>
> Krzysztof,
>
> What would be the best time for me to send the removal of this
> workaround? Is it right after v5.17 release?
The best time is after the merge window, so when v5.17-rc1 is released.
Best regards,
Krzysztof
Powered by blists - more mailing lists