From: <Conor.Dooley@microchip.com>
To: <palmer@rivosinc.com>, <krzysztof.kozlowski@linaro.org>,
<Conor.Dooley@microchip.com>, <damien.lemoal@opensource.wdc.com>
Cc: <daniel.lezcano@linaro.org>, <Eugeniy.Paltsev@synopsys.com>,
<sam@ravnborg.org>, <daniel@ffwll.ch>, <paul.walmsley@sifive.com>,
<vkoul@kernel.org>, <airlied@linux.ie>, <palmer@dabbelt.com>,
<aou@eecs.berkeley.edu>, <robh+dt@kernel.org>,
<masahiroy@kernel.org>, <geert@linux-m68k.org>,
<niklas.cassel@wdc.com>, <dillon.minfei@gmail.com>,
<dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <dmaengine@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <fancer.lancer@gmail.com>,
<thierry.reding@gmail.com>
Subject: Re: [PATCH v5 04/13] dt-bindings: memory-controllers: add canaan k210 sram controller
Date: Tue, 12 Jul 2022 16:04:55 +0000 [thread overview]
Message-ID: <1f63684c-c549-a726-b046-1197ef94d540@microchip.com> (raw)
In-Reply-To: <eeed43cf-7bd6-9d77-9e1f-e018a236a058@linaro.org>
On 12/07/2022 16:59, Krzysztof Kozlowski wrote:
> On 12/07/2022 17:54, Conor.Dooley@microchip.com wrote:
>> On 11/07/2022 00:21, Damien Le Moal wrote:
>>> On 7/11/22 04:39, Conor.Dooley@microchip.com wrote:
>>>> Damien, Krzysztof,
>>>>
>>>> I know this particular version has not been posted for all that
>>>> long, but this binding is (functionally) unchanged for a few
>>>> versions now. Are you happy with this approach Damien?
>>>> U-Boot only cares about the compatible & the clocks property,
>>>> not the regs etc.
>>>>
>>>> I (lazily) tested it in U-Boot with the following diff:
>>>
>>> If both the kernel and u-boot still work as expected with this change, I
>>> am OK with it.
>>
>> It's all yours so Krzysztof :)
>
> It's too late in the cycle for me to pick it up. If you have alternate
> tree to take it through, go ahead with:
>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
> Otherwise, I'll take it after the merge window of v5.20, so in ~1 month
> according to crystal ball.
Cool, thanks Krzysztof. I know it is late in the game for v5.20.
Part of me is hoping that Palmer can take it with the dts patches,
going to bump all the outstanding & reviewed riscv dts patches when
I send my PR this weekend.
If not, I'll remind you in a month. Thanks,
Conor.
next prev parent reply other threads:[~2022-07-12 16:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 21:52 [PATCH v5 00/13] Canaan devicetree fixes Conor Dooley
2022-07-05 21:52 ` [PATCH v5 01/13] dt-bindings: display: convert ilitek,ili9341.txt to dt-schema Conor Dooley
2022-07-05 21:52 ` [PATCH v5 02/13] dt-bindings: display: ili9341: document canaan kd233's lcd Conor Dooley
2022-07-12 7:56 ` Conor.Dooley
2022-07-05 21:52 ` [PATCH v5 03/13] dt-bindings: dma: dw-axi-dmac: extend the number of interrupts Conor Dooley
2022-07-06 5:45 ` Vinod Koul
2022-07-18 15:12 ` Ben Dooks
2022-07-18 15:23 ` Conor.Dooley
2022-07-05 21:52 ` [PATCH v5 04/13] dt-bindings: memory-controllers: add canaan k210 sram controller Conor Dooley
2022-07-06 14:48 ` Rob Herring
2022-07-10 19:39 ` Conor.Dooley
2022-07-10 23:21 ` Damien Le Moal
2022-07-12 15:54 ` Conor.Dooley
2022-07-12 15:59 ` Krzysztof Kozlowski
2022-07-12 16:04 ` Conor.Dooley [this message]
2022-08-16 9:27 ` Krzysztof Kozlowski
2022-08-16 9:31 ` Conor.Dooley
2022-07-05 21:52 ` [PATCH v5 05/13] riscv: dts: canaan: fix the k210's memory node Conor Dooley
2022-07-05 21:52 ` [PATCH v5 06/13] riscv: dts: canaan: fix the k210's timer nodes Conor Dooley
2022-07-05 21:52 ` [PATCH v5 07/13] riscv: dts: canaan: fix mmc node names Conor Dooley
2022-07-05 21:52 ` [PATCH v5 08/13] riscv: dts: canaan: fix kd233 display spi frequency Conor Dooley
2022-07-05 21:52 ` [PATCH v5 09/13] riscv: dts: canaan: use custom compatible for k210 i2s Conor Dooley
2022-07-05 21:52 ` [PATCH v5 10/13] riscv: dts: canaan: remove spi-max-frequency from controllers Conor Dooley
2022-07-05 21:52 ` [PATCH v5 11/13] riscv: dts: canaan: fix bus {ranges,reg} warnings Conor Dooley
2022-07-05 21:52 ` [PATCH v5 12/13] riscv: dts: canaan: add specific compatible for kd233's LCD Conor Dooley
2022-07-05 21:52 ` [PATCH v5 13/13] riscv: dts: canaan: build all devicetress if SOC_CANAAN Conor Dooley
2022-07-06 8:03 ` [PATCH v5 00/13] Canaan devicetree fixes Geert Uytterhoeven
2022-07-06 8:21 ` Conor.Dooley
2022-07-06 11:55 ` Damien Le Moal
2022-07-06 12:01 ` Conor.Dooley
2022-07-06 8:09 ` Geert Uytterhoeven
2022-07-14 22:04 ` Palmer Dabbelt
2022-07-14 22:11 ` Conor.Dooley
2022-08-05 17:51 ` Conor.Dooley
2022-08-10 22:01 ` Palmer Dabbelt
2022-08-11 6:26 ` Conor.Dooley
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=1f63684c-c549-a726-b046-1197ef94d540@microchip.com \
--to=conor.dooley@microchip.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=airlied@linux.ie \
--cc=aou@eecs.berkeley.edu \
--cc=damien.lemoal@opensource.wdc.com \
--cc=daniel.lezcano@linaro.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dillon.minfei@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=fancer.lancer@gmail.com \
--cc=geert@linux-m68k.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=masahiroy@kernel.org \
--cc=niklas.cassel@wdc.com \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.com \
--cc=vkoul@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).