From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
linux-renesas-soc@vger.kernel.org,
Biju Das <biju.das.jz@bp.renesas.com>,
Vinod Koul <vkoul@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/3] dt-bindings: dma: rz-dmac: Document RZ/A1H SoC
Date: Fri, 4 Oct 2024 21:57:07 +0200 [thread overview]
Message-ID: <ZwBIk0DZ6on8eEIm@shikoro> (raw)
In-Reply-To: <CAMuHMdXzCYBn+MPz-tdcP7wJRkdQspU0ZmszMv4Uj7VWpTYR4A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 256 bytes --]
> According to the documentation, there is no bit in a Standby Control
> Register to control the DMAC clock. The driver doesn't care about the
> clock or its rate, so you can use P0 if you want.
Would you prefer using 'p0' or leaving this patch as is?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-10-04 19:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 12:43 [PATCH v2 0/3] dmaengine: sh: rz-dmac: add r7s72100 support Wolfram Sang
2024-10-01 12:43 ` [PATCH v2 1/3] dmaengine: sh: rz-dmac: handle configs where one address is zero Wolfram Sang
2024-10-04 15:00 ` Geert Uytterhoeven
2024-10-01 12:43 ` [PATCH v2 2/3] dt-bindings: dma: rz-dmac: Document RZ/A1H SoC Wolfram Sang
2024-10-02 6:19 ` Krzysztof Kozlowski
2024-10-02 6:37 ` Wolfram Sang
2024-10-04 14:46 ` Geert Uytterhoeven
2024-10-04 19:57 ` Wolfram Sang [this message]
2024-10-07 7:30 ` Geert Uytterhoeven
2024-10-07 7:34 ` Geert Uytterhoeven
2024-10-01 12:43 ` [PATCH v2 3/3] dmaengine: sh: rz-dmac: add r7s72100 support Wolfram Sang
2024-10-04 14:47 ` Geert Uytterhoeven
2024-11-15 14:47 ` [PATCH v2 0/3] " Geert Uytterhoeven
2024-11-15 17:08 ` Wolfram Sang
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=ZwBIk0DZ6on8eEIm@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
--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 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.