From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 3/8] dmaengine: bcm2835: use shared interrupt for channel 11 to 14.
Date: Wed, 13 Jan 2016 19:13:38 +0530 [thread overview]
Message-ID: <20160113134338.GH11130@localhost> (raw)
In-Reply-To: <56965178.7070700@martin.sperl.org>
On Wed, Jan 13, 2016 at 02:30:32PM +0100, Martin Sperl wrote:
> On 13.01.2016 13:26, Vinod Koul wrote:
> >On Thu, Jan 07, 2016 at 05:33:01PM +0000, kernel at martin.sperl.org wrote:
> >>@@ -638,13 +666,21 @@ static int bcm2835_dma_probe(struct platform_device *pdev)
> >> goto err_no_dma;
> >> }
> >>
> >>- for (i = 0; i < pdev->num_resources; i++) {
> >>- irq = platform_get_irq(pdev, i);
> >>+ for (i = 0; i <= BCM2835_DMA_MAX_CHANNEL_NUMBER; i++) {
> >>+ if (BCM2835_DMA_IRQ_SHARED_MASK & BIT(i)) {
> >
> >Ideally this should be done thru DT data and not hard coded in kernel. I
> >dont think this assumption will hold good for next gen of this device, so
> >better to get this from DT!
>
> The ideal solution would be breaking the DT in such a way that we could
> define a register range and interrupt per dma-channel looking something
> like this:
>
> diff --git a/arch/arm/boot/dts/bcm2835.dtsi b/arch/arm/boot/dts/bcm2835.dtsi
> index 83d9787..9526b91 100644
> --- a/arch/arm/boot/dts/bcm2835.dtsi
> +++ b/arch/arm/boot/dts/bcm2835.dtsi
> @@ -31,8 +31,28 @@
>
> dma: dma at 7e007000 {
> compatible = "brcm,bcm2835-dma";
> - reg = <0x7e007000 0xf00>;
> - interrupts = <1 16>,
> + reg = <0x7e007f00 0x100>, /* status reg */
> + <0x7e007000 0x100>,
> + <0x7e007100 0x100>,
> + <0x7e007200 0x100>,
> + <0x7e007300 0x100>,
> + <0x7e007400 0x100>,
> + <0x7e007500 0x100>,
> + <0x7e007600 0x100>,
> + <0x7e007700 0x100>,
> + <0x7e007800 0x100>,
> + <0x7e007900 0x100>,
> + <0x7e007a00 0x100>,
> + <0x7e007b00 0x100>,
> + <0x7e007c00 0x100>,
> + <0x7e007d00 0x100>,
> + <0x7e007e00 0x100>,
> + /* dma channel 15 uses a different base */
> + <0x7ee05000 0x100>;
> + interrupts = <1 28>, /* catch all DMA-interrupts */
> + /* dma channel 0-10 interrupts */
> + <1 16>,
> <1 17>,
> <1 18>,
> <1 19>,
> @@ -43,9 +63,30 @@
> <1 24>,
> <1 25>,
> <1 26>,
> + /* dma channel 11-14 share irq */
> <1 27>,
> - <1 28>;
> -
> + <1 27>,
> + <1 27>,
> + <1 27>,
> + /* no irq support for dma channel 15 */
> + < 0 >;
> + dma-names = "shared",
> + "dma0",
> + "dma1",
> + "dma2",
> + "dma3",
> + "dma4",
> + "dma5",
> + "dma6",
> + "dma7",
> + "dma8",
> + "dma9",
> + "dma10",
> + "dma11",
> + "dma12",
> + "dma13",
> + "dma14",
> + "dma15";
> #dma-cells = <1>;
> brcm,dma-channel-mask = <0x7f35>;
> (or similar)
>
> This actually would allow us to make "brcm,dma-channel-mask" redundant,
> as we could remove those dma channels that are owned by the firmware
> directly from the list.
>
> That way we could also map other capabilities via the DT.
>
> It would also allow a transparent addition of additional dma channels
> with newer versions of the HW - mostly - by modifying the DT.
Precisely
>
> But that would be frowned upon, so I had to come up with the approach
> taken, which makes the following assumptions:
DT was designed to move this info and hardcoding from kernel into
DT, so why cant we do that?
> * the DT maps only the interrupts that are assigned to the HW block
> * the driver knows about the number of DMA channels in HW
> * the driver knows about the mapping of shared interrupts
> (11-14 share irq).
>
> It is not optimal, but at least it works with the least amount of
> change to the DT - and what about all those assumptions that we
> would need to hard-code to be backwards compatible to the DT without?
>
> I guess we could replace BCM2835_DMA_MAX_CHANNEL_NUMBER with:
> /* we do not support dma channel 15 with this driver */
> #define BCM2835_DMA_MAX_CHANNEL_SUPPORTED 14
> ...
> for (i = 0;
> i <= min_t(int, flv(chans_available),
> BCM2835_DMA_MAX_CHANNEL_SUPPORTED);
> i++) {
>
> So which way would you prefer this to go - I got another few days
> before I leave on vacation.
I still think DT is the right way to go here, unless I hear some other
convincing answer..
--
~Vinod
next prev parent reply other threads:[~2016-01-13 13:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 17:32 [PATCH V2 0/8] dmaengine: bcm2835: enhancement of driver kernel at martin.sperl.org
2016-01-07 17:32 ` [PATCH V2 1/8] dmaengine: bcm2835: set residue_granularity field kernel at martin.sperl.org
2016-01-28 19:53 ` Eric Anholt
2016-01-07 17:33 ` [PATCH V2 2/8] dmaengine: bcm2835: remove unnecessary masking of dma channels kernel at martin.sperl.org
2016-01-30 3:08 ` Eric Anholt
2016-01-07 17:33 ` [PATCH V2 3/8] dmaengine: bcm2835: use shared interrupt for channel 11 to 14 kernel at martin.sperl.org
2016-01-13 12:26 ` Vinod Koul
2016-01-13 13:30 ` Martin Sperl
2016-01-13 13:43 ` Vinod Koul [this message]
2016-01-13 14:24 ` Martin Sperl
2016-01-14 4:07 ` Vinod Koul
2016-01-14 8:48 ` Martin Sperl
2016-02-29 17:10 ` Martin Sperl
2016-03-03 15:45 ` Vinod Koul
2016-02-18 4:09 ` Eric Anholt
2016-01-07 17:33 ` [PATCH V2 4/8] dmaengine: bcm2835: add additional defines for DMA-registers kernel at martin.sperl.org
2016-01-13 12:32 ` Vinod Koul
2016-02-18 4:18 ` Eric Anholt
2016-01-07 17:33 ` [PATCH V2 5/8] dmaengine: bcm2835: move cyclic member from bcm2835_chan into bcm2835_desc kernel at martin.sperl.org
2016-02-18 4:19 ` Eric Anholt
2016-01-07 17:33 ` [PATCH V2 6/8] dmaengine: bcm2835: move controlblock chain generation into separate method kernel at martin.sperl.org
2016-01-13 13:23 ` Vinod Koul
2016-01-13 13:38 ` Martin Sperl
2016-02-18 3:24 ` Eric Anholt
2016-02-29 18:14 ` Martin Sperl
2016-01-07 17:33 ` [PATCH V2 7/8] dmaengine: bcm2835: add slave_sg support to bcm2835-dma kernel at martin.sperl.org
2016-02-18 4:39 ` Eric Anholt
2016-01-07 17:33 ` [PATCH V2 8/8] dmaengine: bcm2835: add dma_memcopy " kernel at martin.sperl.org
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=20160113134338.GH11130@localhost \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.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).