From: Eugeniy.Paltsev@synopsys.com (Eugeniy Paltsev)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH v5 2/2] DW DMAC: add multi-block property to device tree
Date: Fri, 25 Nov 2016 11:40:31 +0000 [thread overview]
Message-ID: <1480074030.2534.46.camel@synopsys.com> (raw)
In-Reply-To: <1480003098.20074.18.camel@linux.intel.com>
On Thu, 2016-11-24@17:58 +0200, Andy Shevchenko wrote:
> On Thu, 2016-11-24@17:52 +0200, Andy Shevchenko wrote:
> >
> > On Thu, 2016-11-24@18:04 +0300, Eugeniy Paltsev wrote:
> > >
> > > Several versions of DW DMAC have multi block transfers hardware
> > > support. Hardware support of multi block transfers is disabled
> > > by default if we use DT to configure DMAC and software emulation
> > > of multi block transfers used instead.
> > > Add multi-block property, so it is possible to enable hardware
> > > multi block transfers (if present) via DT.
> > >
> > > Switch from per device is_nollp variable to multi_block array
> > > to be able enable/disable multi block transfers separately per
> > > channel.
> > Thanks for an update. Basically I'm fine with this one.
> >
> > So, we still have question about autoconfiguration in SPEAr SoCs,
> > and
> > your ARC SoC but it's a different story. I would expect once you
> > will
> > clarify it.
> >
> > Another one is minor listed below, otherwise
> >
> > Acked-by: Andy Shevchenko <andriy.shevchenko at linux.intel.com>
> >
> > >
> > > @@ -152,6 +154,11 @@ dw_dma_parse_dt(struct platform_device
> > > *pdev)
> > > ? pdata->data_width[tmp] = BIT(arr[tmp] &
> > > 0x07);
> > > ? }
> > > ?
> > > + if (!of_property_read_u32_array(np, "multi-block", chan,
> > > nr_channels)) {
> > > + for (tmp = 0; tmp < nr_channels; tmp++)
> > > + pdata->multi_block[tmp] = chan[tmp];
> > ...mb (as short of multi-block) would suit better.
> Oh, sorry, guys, but one more important thing. If there is no such
> property, keep a default to "supported". Otherwise you will break old
> (working) DTBs.
Should I remove explicit declaration "multi-block" property from
existing DTS (which I added during v5 patch iteration)?
I mean that:
---------------------->8-----------------------
+ multi-block = <1 1 1 1 1 1 1 1>;
---------------------->8-----------------------
We don't actually need it, if we use use 1 ("supported") as "multi-
block" property default value.
--
?Paltsev Eugeniy
WARNING: multiple messages have this Message-ID (diff)
From: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
To: "andriy.shevchenko@linux.intel.com" <andriy.shevchenko@linux.intel.com>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"christian.ruppert@alitech.com" <christian.ruppert@alitech.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"vinod.koul@intel.com" <vinod.koul@intel.com>,
"vireshk@kernel.org" <vireshk@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"shiraz.linux.kernel@gmail.com" <shiraz.linux.kernel@gmail.com>
Subject: Re: [PATCH v5 2/2] DW DMAC: add multi-block property to device tree
Date: Fri, 25 Nov 2016 11:40:31 +0000 [thread overview]
Message-ID: <1480074030.2534.46.camel@synopsys.com> (raw)
In-Reply-To: <1480003098.20074.18.camel@linux.intel.com>
On Thu, 2016-11-24 at 17:58 +0200, Andy Shevchenko wrote:
> On Thu, 2016-11-24 at 17:52 +0200, Andy Shevchenko wrote:
> >
> > On Thu, 2016-11-24 at 18:04 +0300, Eugeniy Paltsev wrote:
> > >
> > > Several versions of DW DMAC have multi block transfers hardware
> > > support. Hardware support of multi block transfers is disabled
> > > by default if we use DT to configure DMAC and software emulation
> > > of multi block transfers used instead.
> > > Add multi-block property, so it is possible to enable hardware
> > > multi block transfers (if present) via DT.
> > >
> > > Switch from per device is_nollp variable to multi_block array
> > > to be able enable/disable multi block transfers separately per
> > > channel.
> > Thanks for an update. Basically I'm fine with this one.
> >
> > So, we still have question about autoconfiguration in SPEAr SoCs,
> > and
> > your ARC SoC but it's a different story. I would expect once you
> > will
> > clarify it.
> >
> > Another one is minor listed below, otherwise
> >
> > Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> >
> > >
> > > @@ -152,6 +154,11 @@ dw_dma_parse_dt(struct platform_device
> > > *pdev)
> > > pdata->data_width[tmp] = BIT(arr[tmp] &
> > > 0x07);
> > > }
> > >
> > > + if (!of_property_read_u32_array(np, "multi-block", chan,
> > > nr_channels)) {
> > > + for (tmp = 0; tmp < nr_channels; tmp++)
> > > + pdata->multi_block[tmp] = chan[tmp];
> > ...mb (as short of multi-block) would suit better.
> Oh, sorry, guys, but one more important thing. If there is no such
> property, keep a default to "supported". Otherwise you will break old
> (working) DTBs.
Should I remove explicit declaration "multi-block" property from
existing DTS (which I added during v5 patch iteration)?
I mean that:
---------------------->8-----------------------
+ multi-block = <1 1 1 1 1 1 1 1>;
---------------------->8-----------------------
We don't actually need it, if we use use 1 ("supported") as "multi-
block" property default value.
--
Paltsev Eugeniy
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
WARNING: multiple messages have this Message-ID (diff)
From: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
To: "andriy.shevchenko@linux.intel.com" <andriy.shevchenko@linux.intel.com>
Cc: "vinod.koul@intel.com" <vinod.koul@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"shiraz.linux.kernel@gmail.com" <shiraz.linux.kernel@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"vireshk@kernel.org" <vireshk@kernel.org>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"christian.ruppert@alitech.com" <christian.ruppert@alitech.com>,
"arnd@arndb.de" <arnd@arndb.de>
Subject: Re: [PATCH v5 2/2] DW DMAC: add multi-block property to device tree
Date: Fri, 25 Nov 2016 11:40:31 +0000 [thread overview]
Message-ID: <1480074030.2534.46.camel@synopsys.com> (raw)
In-Reply-To: <1480003098.20074.18.camel@linux.intel.com>
On Thu, 2016-11-24 at 17:58 +0200, Andy Shevchenko wrote:
> On Thu, 2016-11-24 at 17:52 +0200, Andy Shevchenko wrote:
> >
> > On Thu, 2016-11-24 at 18:04 +0300, Eugeniy Paltsev wrote:
> > >
> > > Several versions of DW DMAC have multi block transfers hardware
> > > support. Hardware support of multi block transfers is disabled
> > > by default if we use DT to configure DMAC and software emulation
> > > of multi block transfers used instead.
> > > Add multi-block property, so it is possible to enable hardware
> > > multi block transfers (if present) via DT.
> > >
> > > Switch from per device is_nollp variable to multi_block array
> > > to be able enable/disable multi block transfers separately per
> > > channel.
> > Thanks for an update. Basically I'm fine with this one.
> >
> > So, we still have question about autoconfiguration in SPEAr SoCs,
> > and
> > your ARC SoC but it's a different story. I would expect once you
> > will
> > clarify it.
> >
> > Another one is minor listed below, otherwise
> >
> > Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> >
> > >
> > > @@ -152,6 +154,11 @@ dw_dma_parse_dt(struct platform_device
> > > *pdev)
> > > pdata->data_width[tmp] = BIT(arr[tmp] &
> > > 0x07);
> > > }
> > >
> > > + if (!of_property_read_u32_array(np, "multi-block", chan,
> > > nr_channels)) {
> > > + for (tmp = 0; tmp < nr_channels; tmp++)
> > > + pdata->multi_block[tmp] = chan[tmp];
> > ...mb (as short of multi-block) would suit better.
> Oh, sorry, guys, but one more important thing. If there is no such
> property, keep a default to "supported". Otherwise you will break old
> (working) DTBs.
Should I remove explicit declaration "multi-block" property from
existing DTS (which I added during v5 patch iteration)?
I mean that:
---------------------->8-----------------------
+ multi-block = <1 1 1 1 1 1 1 1>;
---------------------->8-----------------------
We don't actually need it, if we use use 1 ("supported") as "multi-
block" property default value.
--
Paltsev Eugeniy
next prev parent reply other threads:[~2016-11-25 11:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 15:04 [PATCH v5 0/2] DW DMAC: update device tree Eugeniy Paltsev
2016-11-24 15:04 ` Eugeniy Paltsev
2016-11-24 15:04 ` [PATCH v5 1/2] DW DMAC: enable memory-to-memory transfers support Eugeniy Paltsev
2016-11-24 15:04 ` Eugeniy Paltsev
2016-11-24 15:04 ` Eugeniy Paltsev
2016-11-24 15:04 ` [PATCH v5 2/2] DW DMAC: add multi-block property to device tree Eugeniy Paltsev
2016-11-24 15:04 ` Eugeniy Paltsev
2016-11-24 15:04 ` Eugeniy Paltsev
2016-11-24 15:52 ` Andy Shevchenko
2016-11-24 15:52 ` Andy Shevchenko
2016-11-24 15:52 ` Andy Shevchenko
2016-11-24 15:58 ` Andy Shevchenko
2016-11-24 15:58 ` Andy Shevchenko
2016-11-24 15:58 ` Andy Shevchenko
2016-11-25 11:40 ` Eugeniy Paltsev [this message]
2016-11-25 11:40 ` Eugeniy Paltsev
2016-11-25 11:40 ` Eugeniy Paltsev
2016-11-25 11:48 ` Andy Shevchenko
2016-11-25 11:48 ` Andy Shevchenko
2016-11-25 11:48 ` Andy Shevchenko
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=1480074030.2534.46.camel@synopsys.com \
--to=eugeniy.paltsev@synopsys.com \
--cc=linux-snps-arc@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 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.