From: Eddie James <eajames@linux.vnet.ibm.com>
To: Arnd Bergmann <arnd@arndb.de>, Eddie James <eajames@linux.ibm.com>
Cc: linux-aspeed@lists.ozlabs.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
DTML <devicetree@vger.kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@aj.id.au>
Subject: Re: [PATCH v2 2/7] drivers/soc: Add Aspeed XDMA Engine Driver
Date: Fri, 24 May 2019 11:08:57 -0500 [thread overview]
Message-ID: <687e4a77-0df1-4982-1edd-9d0559c489fe@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAK8P3a2HSOsw33VhAk4Z8ARiYn4jG68Ec7fynKbrFWUNDo37Wg@mail.gmail.com>
On 5/21/19 7:02 AM, Arnd Bergmann wrote:
> On Mon, May 20, 2019 at 10:19 PM Eddie James <eajames@linux.ibm.com> wrote:
>> diff --git a/include/uapi/linux/aspeed-xdma.h b/include/uapi/linux/aspeed-xdma.h
>> new file mode 100644
>> index 0000000..2a4bd13
>> --- /dev/null
>> +++ b/include/uapi/linux/aspeed-xdma.h
>> @@ -0,0 +1,26 @@
>> +/* SPDX-License-Identifier: GPL-2.0+ */
>> +/* Copyright IBM Corp 2019 */
>> +
>> +#ifndef _UAPI_LINUX_ASPEED_XDMA_H_
>> +#define _UAPI_LINUX_ASPEED_XDMA_H_
>> +
>> +#include <linux/types.h>
>> +
>> +/*
>> + * aspeed_xdma_op
>> + *
>> + * upstream: boolean indicating the direction of the DMA operation; upstream
>> + * means a transfer from the BMC to the host
>> + *
>> + * host_addr: the DMA address on the host side, typically configured by PCI
>> + * subsystem
>> + *
>> + * len: the size of the transfer in bytes; it should be a multiple of 16 bytes
>> + */
>> +struct aspeed_xdma_op {
>> + __u32 upstream;
>> + __u64 host_addr;
>> + __u32 len;
>> +};
>> +
>> +#endif /* _UAPI_LINUX_ASPEED_XDMA_H_ */
> If this is a user space interface, please remove the holes in the
> data structure.
Surely it's 4-byte aligned and there won't be holes??
>
> I don't see how this is actually used in this patch, maybe you meant
> the definition to be part of another patch?
The structure is used in this patch as an argument to aspeed_xdma_start().
Thanks,
Eddie
>
> Arnd
>
next prev parent reply other threads:[~2019-05-24 16:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 20:19 [PATCH v2 0/7] drivers/soc: Add Aspeed XDMA Engine Driver Eddie James
2019-05-20 20:19 ` [PATCH v2 1/7] dt-bindings: soc: Add Aspeed XDMA engine binding documentation Eddie James
2019-05-20 20:19 ` [PATCH v2 2/7] drivers/soc: Add Aspeed XDMA Engine Driver Eddie James
2019-05-21 12:02 ` Arnd Bergmann
2019-05-24 16:08 ` Eddie James [this message]
2019-05-29 1:59 ` Andrew Jeffery
2019-05-20 20:19 ` [PATCH v2 3/7] drivers/soc: xdma: Add user interface Eddie James
2019-05-21 3:52 ` Andrew Jeffery
2019-05-20 20:19 ` [PATCH v2 4/7] drivers/soc: xdma: Add PCI device configuration sysfs Eddie James
2019-05-21 3:22 ` Andrew Jeffery
2019-05-21 12:06 ` Arnd Bergmann
2019-05-20 20:19 ` [PATCH v2 5/7] drivers/soc: xdma: Add debugfs entries Eddie James
2019-05-21 11:58 ` Arnd Bergmann
2019-05-20 20:19 ` [PATCH v2 6/7] ARM: dts: aspeed: Add XDMA Engine Eddie James
2019-05-20 20:19 ` [PATCH v2 7/7] ARM: dts: aspeed: witherspoon: Enable " Eddie James
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=687e4a77-0df1-4982-1edd-9d0559c489fe@linux.vnet.ibm.com \
--to=eajames@linux.vnet.ibm.com \
--cc=andrew@aj.id.au \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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: 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).