All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zong Li <zong.li@sifive.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Vinod <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	Conor Dooley <conor.dooley@microchip.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Bin Meng <bin.meng@windriver.com>,
	Green Wan <green.wan@sifive.com>,
	dmaengine <dmaengine@vger.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org List"
	<linux-kernel@vger.kernel.org>,
	linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v8 0/4] Determine the number of DMA channels by 'dma-channels' property
Date: Fri, 1 Apr 2022 13:50:50 +0800	[thread overview]
Message-ID: <CANXhq0oJKRVV2QyzJ2WV1fjcw3piyoKeiR5U-=DqsyDayixTGA@mail.gmail.com> (raw)
In-Reply-To: <mhng-5afad1be-9b06-4cd1-95e3-c21605b9086a@palmer-mbp2014>

On Fri, Apr 1, 2022 at 6:42 AM Palmer Dabbelt <palmer@dabbelt.com> wrote:
>
> On Wed, 30 Mar 2022 22:54:47 PDT (-0700), Palmer Dabbelt wrote:
> > On Wed, 30 Mar 2022 22:21:56 PDT (-0700), vkoul@kernel.org wrote:
> >> On 30-03-22, 20:15, Palmer Dabbelt wrote:
> >>> On Mon, 28 Mar 2022 02:52:21 PDT (-0700), zong.li@sifive.com wrote:
> >>> > The PDMA driver currently assumes there are four channels by default, it
> >>> > might cause the error if there is actually less than four channels.
> >>> > Change that by getting number of channel dynamically from device tree.
> >>> > For backwards-compatible, it uses the default value (i.e. 4) when there
> >>> > is no 'dma-channels' information in dts.
> >>> >
> >>> > This patch set contains the dts and dt-bindings change.
> >>> >
> >>> > Changed in v8:
> >>> >  - Rebase on master
> >>> >  - Remove modification of microchip-mpfs.dtsi
> >>> >  - Rename DMA node name of fu540-c000.dtsi
> >>> >
> >>> > Changed in v7:
> >>> >  - Rebase on tag v5.17-rc7
> >>> >  - Modify the subject of patch
> >>> >
> >>> > Changed in v6:
> >>> >  - Rebase on tag v5.17-rc6
> >>> >  - Change sf_pdma.chans[] to a flexible array member.
> >>> >
> >>> > Changed in v5:
> >>> >  - Rebase on tag v5.17-rc3
> >>> >  - Fix typo in dt-bindings and commit message
> >>> >  - Add PDMA versioning scheme for compatible
> >>> >
> >>> > Changed in v4:
> >>> >  - Remove cflags of debug use reported-by: kernel test robot <lkp@intel.com>
> >>> >
> >>> > Changed in v3:
> >>> >  - Fix allocating wrong size
> >>> >  - Return error if 'dma-channels' is larger than maximum
> >>> >
> >>> > Changed in v2:
> >>> >  - Rebase on tag v5.16
> >>> >  - Use 4 as default value of dma-channels
> >>> >
> >>> > Zong Li (4):
> >>> >   dt-bindings: dma-engine: sifive,fu540: Add dma-channels property and
> >>> >     modify compatible
> >>> >   riscv: dts: Add dma-channels property and modify compatible
> >>> >   riscv: dts: rename the node name of dma
> >>> >   dmaengine: sf-pdma: Get number of channel by device tree
> >>> >
> >>> >  .../bindings/dma/sifive,fu540-c000-pdma.yaml  | 19 +++++++++++++--
> >>> >  arch/riscv/boot/dts/sifive/fu540-c000.dtsi    |  5 ++--
> >>> >  drivers/dma/sf-pdma/sf-pdma.c                 | 24 ++++++++++++-------
> >>> >  drivers/dma/sf-pdma/sf-pdma.h                 |  8 ++-----
> >>> >  4 files changed, 38 insertions(+), 18 deletions(-)
> >>>
> >>> Thanks, these are on for-next.
> >>
> >> The drivers/dma/ should go thru dmaengine tree. During merge window I
> >> dont apply the patches
> >
> > OK, I can drop this from my tree if you'd like?
>
> Just to follow up from IRC: I'm dropping these from my tree.

Hi Palmer and Vinod,
Many thanks for your help. As all you suggested, let's go this
patchset by the dmaengine tree. Thanks a lot!

WARNING: multiple messages have this Message-ID (diff)
From: Zong Li <zong.li@sifive.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Vinod <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	 Paul Walmsley <paul.walmsley@sifive.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	 Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	 Conor Dooley <conor.dooley@microchip.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	 Bin Meng <bin.meng@windriver.com>,
	Green Wan <green.wan@sifive.com>,
	 dmaengine <dmaengine@vger.kernel.org>,
	 "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	 "linux-kernel@vger.kernel.org List"
	<linux-kernel@vger.kernel.org>,
	 linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v8 0/4] Determine the number of DMA channels by 'dma-channels' property
Date: Fri, 1 Apr 2022 13:50:50 +0800	[thread overview]
Message-ID: <CANXhq0oJKRVV2QyzJ2WV1fjcw3piyoKeiR5U-=DqsyDayixTGA@mail.gmail.com> (raw)
In-Reply-To: <mhng-5afad1be-9b06-4cd1-95e3-c21605b9086a@palmer-mbp2014>

On Fri, Apr 1, 2022 at 6:42 AM Palmer Dabbelt <palmer@dabbelt.com> wrote:
>
> On Wed, 30 Mar 2022 22:54:47 PDT (-0700), Palmer Dabbelt wrote:
> > On Wed, 30 Mar 2022 22:21:56 PDT (-0700), vkoul@kernel.org wrote:
> >> On 30-03-22, 20:15, Palmer Dabbelt wrote:
> >>> On Mon, 28 Mar 2022 02:52:21 PDT (-0700), zong.li@sifive.com wrote:
> >>> > The PDMA driver currently assumes there are four channels by default, it
> >>> > might cause the error if there is actually less than four channels.
> >>> > Change that by getting number of channel dynamically from device tree.
> >>> > For backwards-compatible, it uses the default value (i.e. 4) when there
> >>> > is no 'dma-channels' information in dts.
> >>> >
> >>> > This patch set contains the dts and dt-bindings change.
> >>> >
> >>> > Changed in v8:
> >>> >  - Rebase on master
> >>> >  - Remove modification of microchip-mpfs.dtsi
> >>> >  - Rename DMA node name of fu540-c000.dtsi
> >>> >
> >>> > Changed in v7:
> >>> >  - Rebase on tag v5.17-rc7
> >>> >  - Modify the subject of patch
> >>> >
> >>> > Changed in v6:
> >>> >  - Rebase on tag v5.17-rc6
> >>> >  - Change sf_pdma.chans[] to a flexible array member.
> >>> >
> >>> > Changed in v5:
> >>> >  - Rebase on tag v5.17-rc3
> >>> >  - Fix typo in dt-bindings and commit message
> >>> >  - Add PDMA versioning scheme for compatible
> >>> >
> >>> > Changed in v4:
> >>> >  - Remove cflags of debug use reported-by: kernel test robot <lkp@intel.com>
> >>> >
> >>> > Changed in v3:
> >>> >  - Fix allocating wrong size
> >>> >  - Return error if 'dma-channels' is larger than maximum
> >>> >
> >>> > Changed in v2:
> >>> >  - Rebase on tag v5.16
> >>> >  - Use 4 as default value of dma-channels
> >>> >
> >>> > Zong Li (4):
> >>> >   dt-bindings: dma-engine: sifive,fu540: Add dma-channels property and
> >>> >     modify compatible
> >>> >   riscv: dts: Add dma-channels property and modify compatible
> >>> >   riscv: dts: rename the node name of dma
> >>> >   dmaengine: sf-pdma: Get number of channel by device tree
> >>> >
> >>> >  .../bindings/dma/sifive,fu540-c000-pdma.yaml  | 19 +++++++++++++--
> >>> >  arch/riscv/boot/dts/sifive/fu540-c000.dtsi    |  5 ++--
> >>> >  drivers/dma/sf-pdma/sf-pdma.c                 | 24 ++++++++++++-------
> >>> >  drivers/dma/sf-pdma/sf-pdma.h                 |  8 ++-----
> >>> >  4 files changed, 38 insertions(+), 18 deletions(-)
> >>>
> >>> Thanks, these are on for-next.
> >>
> >> The drivers/dma/ should go thru dmaengine tree. During merge window I
> >> dont apply the patches
> >
> > OK, I can drop this from my tree if you'd like?
>
> Just to follow up from IRC: I'm dropping these from my tree.

Hi Palmer and Vinod,
Many thanks for your help. As all you suggested, let's go this
patchset by the dmaengine tree. Thanks a lot!

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2022-04-01  5:51 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28  9:52 [PATCH v8 0/4] Determine the number of DMA channels by 'dma-channels' property Zong Li
2022-03-28  9:52 ` Zong Li
2022-03-28  9:52 ` [PATCH v8 1/4] dt-bindings: dma-engine: sifive,fu540: Add dma-channels property and modify compatible Zong Li
2022-03-28  9:52   ` [PATCH v8 1/4] dt-bindings: dma-engine: sifive, fu540: " Zong Li
2022-03-29  1:35   ` [PATCH v8 1/4] dt-bindings: dma-engine: sifive,fu540: " Bin Meng
2022-03-29  1:35     ` Bin Meng
2022-03-28  9:52 ` [PATCH v8 2/4] riscv: dts: " Zong Li
2022-03-28  9:52   ` Zong Li
2022-03-29  1:35   ` Bin Meng
2022-03-29  1:35     ` Bin Meng
2022-03-28  9:52 ` [PATCH v8 3/4] riscv: dts: rename the node name of dma Zong Li
2022-03-28  9:52   ` Zong Li
2022-03-29  1:35   ` Bin Meng
2022-03-29  1:35     ` Bin Meng
2022-03-28  9:52 ` [PATCH v8 4/4] dmaengine: sf-pdma: Get number of channel by device tree Zong Li
2022-03-28  9:52   ` Zong Li
2022-03-29  1:35   ` Bin Meng
2022-03-29  1:35     ` Bin Meng
2022-03-31  1:06 ` [PATCH v8 0/4] Determine the number of DMA channels by 'dma-channels' property Zong Li
2022-03-31  1:06   ` Zong Li
2022-03-31  3:15 ` Palmer Dabbelt
2022-03-31  3:15   ` Palmer Dabbelt
2022-03-31  5:21   ` Vinod Koul
2022-03-31  5:21     ` Vinod Koul
2022-03-31  5:54     ` Palmer Dabbelt
2022-03-31  5:54       ` Palmer Dabbelt
2022-03-31 22:42       ` Palmer Dabbelt
2022-03-31 22:42         ` Palmer Dabbelt
2022-04-01  5:50         ` Zong Li [this message]
2022-04-01  5:50           ` Zong Li
2022-04-08  8:03     ` Zong Li
2022-04-08  8:03       ` Zong Li
2022-04-08 13:13 ` Vinod Koul
2022-04-08 13:13   ` Vinod Koul
2022-04-11  2:51   ` Zong Li
2022-04-11  2:51     ` Zong Li
2022-04-11 10:48     ` Vinod Koul
2022-04-11 10:48       ` Vinod Koul
2022-04-11 11:43       ` Zong Li
2022-04-11 11:43         ` Zong Li
2022-04-20  0:18         ` Palmer Dabbelt
2022-04-20  0:18           ` Palmer Dabbelt
2022-04-20 14:25           ` Rob Herring
2022-04-20 14:25             ` Rob Herring
2022-04-21  1:07             ` Zong Li
2022-04-21  1:07               ` Zong Li
2022-04-21  2:49             ` Palmer Dabbelt
2022-04-21  2:49               ` Palmer Dabbelt

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='CANXhq0oJKRVV2QyzJ2WV1fjcw3piyoKeiR5U-=DqsyDayixTGA@mail.gmail.com' \
    --to=zong.li@sifive.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=bin.meng@windriver.com \
    --cc=conor.dooley@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=green.wan@sifive.com \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@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.