devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	DTML <devicetree@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Masami Hiramatsu <masami.hiramatsu@linaro.org>,
	Jassi Brar <jaswinder.singh@linaro.org>
Subject: Re: [PATCH v2 1/6] dt-bindings: dma: uniphier-xdmac: Remove extension register region description
Date: Thu, 19 Mar 2020 23:18:29 +0900	[thread overview]
Message-ID: <CAK7LNASmZRszPB-o4pzeu0aQM4_cQBkRxwFM2T4_onHA4-1r8w@mail.gmail.com> (raw)
In-Reply-To: <1584604252-13172-2-git-send-email-hayashi.kunihiko@socionext.com>

On Thu, Mar 19, 2020 at 4:51 PM Kunihiko Hayashi
<hayashi.kunihiko@socionext.com> wrote:
>
> The address of the extension register region in example is incorrect,
> however, this extension register region is optional


On which SoC is it optional?

In your previous DT submission, every reg was,
like this:

reg = <0x5fc10000 0x1000>, <0x5fc20000 0x800>;



and you meant

reg = <0x5fc10000 0x1000>, <0x5fc12000 0x800>;

?

> and isn't currently
> referred from the driver, so the description of the region should be
> suppressed until referred by the driver.

This sounds like you plan to get it back
as you extend the driver.

I checked the datasheet. This controller has more registers,
so you split the reg into small chunks, the final form will look scary:

reg = <0x5fc10000 0x1000>, <0x5fc12000 0x800>,
      <0x5fc14000 0x100>,  <0x5fc15000 0x100>;


My question is why you did not use a single reg tuple
that covers the whole registers.

Is any other hardware reg interleaved in between?






>
> Fixes: b9fb56b6ba8a ("dt-bindings: dmaengine: Add UniPhier external DMA controller bindings")
> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
> ---
>  Documentation/devicetree/bindings/dma/socionext,uniphier-xdmac.yaml | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/dma/socionext,uniphier-xdmac.yaml b/Documentation/devicetree/bindings/dma/socionext,uniphier-xdmac.yaml
> index 86cfb59..f4c3f49 100644
> --- a/Documentation/devicetree/bindings/dma/socionext,uniphier-xdmac.yaml
> +++ b/Documentation/devicetree/bindings/dma/socionext,uniphier-xdmac.yaml
> @@ -24,7 +24,6 @@ properties:
>    reg:
>      items:
>        - description: XDMAC base register region (offset and length)
> -      - description: XDMAC extension register region (offset and length)
>
>    interrupts:
>      maxItems: 1
> @@ -54,7 +53,7 @@ examples:
>    - |
>      xdmac: dma-controller@5fc10000 {
>          compatible = "socionext,uniphier-xdmac";
> -        reg = <0x5fc10000 0x1000>, <0x5fc20000 0x800>;
> +        reg = <0x5fc10000 0x1000>;
>          interrupts = <0 188 4>;
>          #dma-cells = <2>;
>          dma-channels = <16>;
> --
> 2.7.4
>


-- 
Best Regards
Masahiro Yamada

  reply	other threads:[~2020-03-19 14:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19  7:50 [PATCH v2 0/6] Add devicetree features and fixes for UniPhier SoCs Kunihiko Hayashi
2020-03-19  7:50 ` [PATCH v2 1/6] dt-bindings: dma: uniphier-xdmac: Remove extension register region description Kunihiko Hayashi
2020-03-19 14:18   ` Masahiro Yamada [this message]
2020-03-23  2:26     ` Kunihiko Hayashi
2020-03-19  7:50 ` [PATCH v2 2/6] ARM: dts: uniphier: Add XDMAC node Kunihiko Hayashi
2020-03-19  7:50 ` [PATCH v2 3/6] arm64: " Kunihiko Hayashi
2020-03-19  7:50 ` [PATCH v2 4/6] ARM: dts: uniphier: Add ethernet aliases Kunihiko Hayashi
2020-03-19  7:50 ` [PATCH v2 5/6] arm64: " Kunihiko Hayashi
2020-03-19  7:50 ` [PATCH v2 6/6] arm64: dts: uniphier: Stabilize Ethernet RGMII mode of PXs3 ref board Kunihiko Hayashi

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=CAK7LNASmZRszPB-o4pzeu0aQM4_cQBkRxwFM2T4_onHA4-1r8w@mail.gmail.com \
    --to=masahiroy@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hayashi.kunihiko@socionext.com \
    --cc=jaswinder.singh@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=masami.hiramatsu@linaro.org \
    --cc=robh+dt@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).