From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] dmaengine: vdma: Add 64 bit addressing support to the driver
Date: Mon, 21 Mar 2016 18:17:48 +0200 [thread overview]
Message-ID: <3681371.njDCZ2OU0Q@avalon> (raw)
In-Reply-To: <3802E9A6666DF54886E2B9CBF743BA9801C08CA1@XAP-PVEXMBX01.xlnx.xilinx.com>
Hi Anurag,
On Wednesday 23 Sep 2015 15:12:36 Anurag Kumar Vulisha wrote:
> On Monday, September 21, 2015 9:27 PM Vinod Koul wrote:
> > On Thu, Aug 27, 2015 at 09:19:18PM +0530, Anurag Kumar Vulisha wrote:
> >> This VDMA is a soft ip, which can be programmed to support
> >> 32 bit addressing or greater than 32 bit addressing.
> >>
> >> When the VDMA ip is configured for 32 bit address space the transfer
> >> start address is specified by a single register.
> >
> > would be good to specfiy which one
>
> Will change this in v3
What happened to v3 ? :-)
> >> When the VDMA core is configured for an address space greater than 32
> >> then each start address is specified by a combination of two
> >> registers. The first register specifies the LSB 32 bits of address,
> >> while the next register specifies the MSB 32 bits of address.For
> >> example,5Ch will specify the LSB 32 bits while 60h will specify the
> >> MSB 32 bits of the first start address.So we need to program two
> >> registers at a time.
> >
> > can we have spaces after full stops and commas!
>
> Will take care of this in v3 patch.
>
> >> +/* Since vdma driver is trying to write to a register offset which is
> >> +not a
> >> + * multiple of 64 bits(ex : 0x5c), we are writing as two separate 32
> >> +bits
> >> + * instead of a single 64 bit register write.
> >> + */
> >
> > This is not kernel style for multi-lines, pls refer to
> > Documentation/CodingStyle
>
> Will address this in v3 patch
>
> >> +
> >> +static inline void vdma_desc_write_64(struct xilinx_vdma_chan *chan,
> >> u32 reg,
> >> + u32 value_lsb, u32 value_msb)
> >> +{
> >> + /* Write the lsb 32 bits*/
> >> + writel(value_lsb, chan->xdev->regs + chan->desc_offset + reg);
> >> +
> >> + /* Write the msb 32 bits */
> >> + writel(value_msb, chan->xdev->regs + chan->desc_offset + reg + 4);
> >
> > why not writeq
>
> We are trying to write at a register address(ex:0x5c) which is not aligned
> on 8 bytes boundary.So if I try to use 64 bit write on it,unalignment
> fault is getting generated.To avoid that we are using two separate 32 bit
> writes. We had this discussion in previous versions of this patch with
> Laurent Pinchart .I have also added this exaplanation in the comments above
> this function.
>
> >> + err = of_property_read_u32(node, "xlnx,addrwidth", &addr_width);
> >> +
> >> + if (err < 0) {
> >> + /* Setting addr_width property to default 32 bits */
> >> + addr_width = 32;
> >> + }
> >
> > braces for a single line statement! Also space is redandant before if
> > condition
>
> Will take care of this in v3 patch
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2016-03-21 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 15:49 [PATCH v2] dmaengine: vdma: Add 64 bit addressing support to the driver Anurag Kumar Vulisha
2015-09-21 15:57 ` Vinod Koul
2015-09-23 15:12 ` Anurag Kumar Vulisha
2016-03-21 16:17 ` Laurent Pinchart [this message]
2016-03-25 9:17 ` Appana Durga Kedareswara Rao
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=3681371.njDCZ2OU0Q@avalon \
--to=laurent.pinchart@ideasonboard.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).