On 9/9/2017 12:20 PM, Shreyansh Jain wrote:
> Userspace applications interact with DPAA blocks using this IOCTL driver.
>
> Signed-off-by: Geoff Thorpe <geoff.tho...@nxp.com>
> Signed-off-by: Hemant Agrawal <hemant.agra...@nxp.com>
> Signed-off-by: Shreyansh Jain <shreyansh.j...@nxp.com>
<...>
> +static int fd = -1;
> +static pthread_mutex_t fd_init_lock = PTHREAD_MUTEX_INITIALIZER;
> +
> +static int check_fd(void)
> +{
> + int ret;
> +
> + if (fd >= 0)
> + return 0;
> + ret = pthread_mutex_lock(&fd_init_lock);
Do you need to link against pthred library for this":
LDLIBS += -lpthread
<...>
> +/* The process device underlies process-wide user/kernel interactions, such
> as
> + * mapping dma_mem memory and providing accompanying ioctl()s. (This isn't
> used
> + * for portals, which use one UIO device each.).
> + */
> +#define PROCESS_PATH "/dev/fsl-usdpaa"
Who is creating this file, who is responsible to responding ioctl()
calls, there must a kernel module, right?
<...>
