From: Zong Li <zong.li@sifive.com> To: robh+dt@kernel.org, paul.walmsley@sifive.com, palmer@dabbelt.com, aou@eecs.berkeley.edu, krzysztof.kozlowski@canonical.com, conor.dooley@microchip.com, geert@linux-m68k.org, bin.meng@windriver.com, green.wan@sifive.com, vkoul@kernel.org, dmaengine@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org Cc: Zong Li <zong.li@sifive.com> Subject: [PATCH v4 0/3] Determine the number of DMA channels by 'dma-channels' property Date: Mon, 17 Jan 2022 09:35:25 +0800 [thread overview] Message-ID: <cover.1642383007.git.zong.li@sifive.com> (raw) 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 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 (3): riscv: dts: Add dma-channels property in dma node dt-bindings: Add dma-channels for pdma device node dmaengine: sf-pdma: Get number of channel by device tree .../bindings/dma/sifive,fu540-c000-pdma.yaml | 7 +++++++ .../boot/dts/microchip/microchip-mpfs.dtsi | 1 + arch/riscv/boot/dts/sifive/fu540-c000.dtsi | 1 + drivers/dma/sf-pdma/sf-pdma.c | 20 ++++++++++++------- drivers/dma/sf-pdma/sf-pdma.h | 8 ++------ 5 files changed, 24 insertions(+), 13 deletions(-) -- 2.31.1
WARNING: multiple messages have this Message-ID (diff)
From: Zong Li <zong.li@sifive.com> To: robh+dt@kernel.org, paul.walmsley@sifive.com, palmer@dabbelt.com, aou@eecs.berkeley.edu, krzysztof.kozlowski@canonical.com, conor.dooley@microchip.com, geert@linux-m68k.org, bin.meng@windriver.com, green.wan@sifive.com, vkoul@kernel.org, dmaengine@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org Cc: Zong Li <zong.li@sifive.com> Subject: [PATCH v4 0/3] Determine the number of DMA channels by 'dma-channels' property Date: Mon, 17 Jan 2022 09:35:25 +0800 [thread overview] Message-ID: <cover.1642383007.git.zong.li@sifive.com> (raw) 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 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 (3): riscv: dts: Add dma-channels property in dma node dt-bindings: Add dma-channels for pdma device node dmaengine: sf-pdma: Get number of channel by device tree .../bindings/dma/sifive,fu540-c000-pdma.yaml | 7 +++++++ .../boot/dts/microchip/microchip-mpfs.dtsi | 1 + arch/riscv/boot/dts/sifive/fu540-c000.dtsi | 1 + drivers/dma/sf-pdma/sf-pdma.c | 20 ++++++++++++------- drivers/dma/sf-pdma/sf-pdma.h | 8 ++------ 5 files changed, 24 insertions(+), 13 deletions(-) -- 2.31.1 _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2022-01-17 1:35 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-17 1:35 Zong Li [this message] 2022-01-17 1:35 ` [PATCH v4 0/3] Determine the number of DMA channels by 'dma-channels' property Zong Li 2022-01-17 1:35 ` [PATCH v4 1/3] riscv: dts: Add dma-channels property in dma node Zong Li 2022-01-17 1:35 ` Zong Li 2022-01-18 15:04 ` Conor.Dooley 2022-01-18 15:04 ` Conor.Dooley 2022-01-20 18:51 ` Palmer Dabbelt 2022-01-20 18:51 ` Palmer Dabbelt 2022-01-27 7:03 ` Vinod Koul 2022-01-27 7:03 ` Vinod Koul 2022-01-27 7:35 ` Zong Li 2022-01-27 7:35 ` Zong Li 2022-01-17 1:35 ` [PATCH v4 2/3] dt-bindings: Add dma-channels for pdma device node Zong Li 2022-01-17 1:35 ` Zong Li 2022-01-20 18:51 ` Palmer Dabbelt 2022-01-20 18:51 ` Palmer Dabbelt 2022-01-21 1:57 ` Zong Li 2022-01-21 1:57 ` Zong Li 2022-01-17 1:35 ` [PATCH v4 3/3] dmaengine: sf-pdma: Get number of channel by device tree Zong Li 2022-01-17 1:35 ` Zong Li 2022-01-20 18:51 ` Palmer Dabbelt 2022-01-20 18:51 ` Palmer Dabbelt 2022-01-21 2:21 ` Zong Li 2022-01-21 2:21 ` Zong Li 2022-01-21 8:33 ` Geert Uytterhoeven 2022-01-21 8:33 ` Geert Uytterhoeven 2022-01-21 10:29 ` Zong Li 2022-01-21 10:29 ` Zong Li 2022-01-25 5:08 ` Zong Li 2022-01-25 5:08 ` Zong Li
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=cover.1642383007.git.zong.li@sifive.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: linkBe 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.