devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: vinod.koul@intel.com, fabio.estevam@freescale.com,
	b38343@freescale.com, robh+dt@kernel.org, pawel.moll@arm.com,
	mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
	galak@codeaurora.org, dan.j.williams@intel.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	dmaengine@vger.kernel.org
Subject: Re: [PATCH] dmaengine: imx-sdma: Add DMA event remapping for imx6sx-sdma
Date: Mon, 20 Apr 2015 10:34:33 -0700	[thread overview]
Message-ID: <20150420173433.GA6920@Asurada> (raw)
In-Reply-To: <20150420094541.GL6325@pengutronix.de>

Hi Sascha,

Thank you for the comments.

On Mon, Apr 20, 2015 at 11:45:41AM +0200, Sascha Hauer wrote:
> On Tue, Apr 14, 2015 at 10:39:11PM -0700, Nicolin Chen wrote:
> > The SDMA on imx6sx has a few DMA event remapping configurations
> > inside the GPR (General Purpose Register) of that SoC. When users
> > want to use a non-default DMA event, they need to configure the
> > GPR register. So this patch gives an interface of the GPR and
> > implements it in the SDMA driver so as to finish the DMA event
> > remapping.
> > 
> > Signed-off-by: Nicolin Chen <nicoleotsuka@gmail.com>

> > diff --git a/Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt b/Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt
> > index dc8d3aa..03315a6 100644
> > --- a/Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt
> > +++ b/Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt
> > @@ -8,6 +8,7 @@ Required properties:
> >        "fsl,imx51-sdma"
> >        "fsl,imx53-sdma"
> >        "fsl,imx6q-sdma"
> > +      "fsl,imx6sx-sdma"
> >    The -to variants should be preferred since they allow to determine the
> >    correct ROM script addresses needed for the driver to work without additional
> >    firmware.
> > @@ -19,6 +20,14 @@ Required properties:
> >  - fsl,sdma-ram-script-name : Should contain the full path of SDMA RAM
> >    scripts firmware
> >  
> > +Optional properties:
> > +- fsl, sdma-event-remap : List of one or more DMA event remapping
> > +  configurations. Its format: <&gpr addr shift val>
> > +	gpr : the gpr phandle
> > +	addr : the register address of the GPR
> > +	shift : the bit shift of the GPR register
> > +	val : the value of that bit
> 
> This binding allows arbitrary register writes to the GPR register space.
> I don't think we want to allow that. A binding for this if necessary at
> all must be higher level.

I was actually wondering where could be the best place to put this in.
But I couldn't figure out a better place than this driver while being
worried about the violation as you mentioned.

But what could be that higher level?

Thank you
Nicolin

  reply	other threads:[~2015-04-20 17:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15  5:39 [PATCH] dmaengine: imx-sdma: Add DMA event remapping for imx6sx-sdma Nicolin Chen
     [not found] ` <1429076351-4429-1-git-send-email-nicoleotsuka-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-04-20  9:45   ` Sascha Hauer
2015-04-20 17:34     ` Nicolin Chen [this message]
2015-04-27  7:09       ` Sascha Hauer

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=20150420173433.GA6920@Asurada \
    --to=nicoleotsuka@gmail.com \
    --cc=b38343@freescale.com \
    --cc=dan.j.williams@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=fabio.estevam@freescale.com \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=vinod.koul@intel.com \
    /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).