RE: [PATCH 04/12] intel-ipu3: Add user space ABI definitions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi, Sakari and Hans,

Sorry for the late response to this header file.

> -----Original Message-----
> From: Sakari Ailus [mailto:sakari.ailus@xxxxxxxxxxxxxxx]
> Sent: Wednesday, June 7, 2017 3:23 PM
> To: Hans Verkuil <hverkuil@xxxxxxxxx>
> Cc: Zhi, Yong <yong.zhi@xxxxxxxxx>; linux-media@xxxxxxxxxxxxxxx; Zheng,
> Jian Xu <jian.xu.zheng@xxxxxxxxx>; tfiga@xxxxxxxxxxxx; Mani, Rajmohan
> <rajmohan.mani@xxxxxxxxx>; Toivonen, Tuukka
> <tuukka.toivonen@xxxxxxxxx>
> Subject: Re: [PATCH 04/12] intel-ipu3: Add user space ABI definitions
> 
> Hi Hans,
> 
> On Tue, Jun 06, 2017 at 10:28:26AM +0200, Hans Verkuil wrote:
> > On 05/06/17 22:39, Yong Zhi wrote:
> >
> > Commit message missing.
> >
> > > Signed-off-by: Yong Zhi <yong.zhi@xxxxxxxxx>
> > > ---
> > >  include/uapi/linux/intel-ipu3.h | 2182
> > > +++++++++++++++++++++++++++++++++++++++
> > >  1 file changed, 2182 insertions(+)
> > >  create mode 100644 include/uapi/linux/intel-ipu3.h
> > >
> > > diff --git a/include/uapi/linux/intel-ipu3.h
> > > b/include/uapi/linux/intel-ipu3.h new file mode 100644 index
> > > 0000000..9e90aec
> > > --- /dev/null
> > > +++ b/include/uapi/linux/intel-ipu3.h
> > > @@ -0,0 +1,2182 @@
> > > +/*
> > > + * Copyright (c) 2017 Intel Corporation.
> > > + *
> > > + * This program is free software; you can redistribute it and/or
> > > + * modify it under the terms of the GNU General Public License
> > > +version
> > > + * 2 as published by the Free Software Foundation.
> > > + *
> > > + * This program is distributed in the hope that it will be useful,
> > > + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> > > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> > > + * GNU General Public License for more details.
> > > + */
> > > +
> > > +#ifndef __IPU3_UAPI_H
> > > +#define __IPU3_UAPI_H
> > > +
> > > +#include <linux/types.h>
> > > +
> > > +#define IPU3_UAPI_ISP_VEC_ELEMS				64
> > > +
> > > +#define IMGU_ABI_PAD	__aligned(IPU3_UAPI_ISP_WORD_BYTES)
> > > +#define IPU3_ALIGN
> 	__attribute__((aligned(IPU3_UAPI_ISP_WORD_BYTES)))
> > > +
> > > +#define IPU3_UAPI_ISP_WORD_BYTES			32
> > > +#define IPU3_UAPI_MAX_STRIPES				2
> > > +
> > > +/******************* ipu3_uapi_stats_3a *******************/
> > > +
> > > +#define IPU3_UAPI_MAX_BUBBLE_SIZE			10
> > > +
> > > +#define IPU3_UAPI_AE_COLORS				4
> > > +#define IPU3_UAPI_AE_BINS				256
> > > +
> > > +#define IPU3_UAPI_AWB_MD_ITEM_SIZE			8
> > > +#define IPU3_UAPI_AWB_MAX_SETS				60
> > > +#define IPU3_UAPI_AWB_SET_SIZE				0x500
> > > +#define IPU3_UAPI_AWB_SPARE_FOR_BUBBLES \
> > > +		(IPU3_UAPI_MAX_BUBBLE_SIZE * IPU3_UAPI_MAX_STRIPES *
> \
> > > +		 IPU3_UAPI_AWB_MD_ITEM_SIZE)
> > > +#define IPU3_UAPI_AWB_MAX_BUFFER_SIZE \
> > > +		(IPU3_UAPI_AWB_MAX_SETS * \
> > > +		 (IPU3_UAPI_AWB_SET_SIZE +
> IPU3_UAPI_AWB_SPARE_FOR_BUBBLES))
> > > +
> > > +#define IPU3_UAPI_AF_MAX_SETS				24
> > > +#define IPU3_UAPI_AF_MD_ITEM_SIZE			4
> > > +#define IPU3_UAPI_AF_SPARE_FOR_BUBBLES \
> > > +		(IPU3_UAPI_MAX_BUBBLE_SIZE * IPU3_UAPI_MAX_STRIPES *
> \
> > > +		 IPU3_UAPI_AF_MD_ITEM_SIZE)
> > > +#define IPU3_UAPI_AF_Y_TABLE_SET_SIZE			0x80
> > > +#define IPU3_UAPI_AF_Y_TABLE_MAX_SIZE \
> > > +	(IPU3_UAPI_AF_MAX_SETS * \
> > > +	 (IPU3_UAPI_AF_Y_TABLE_SET_SIZE +
> IPU3_UAPI_AF_SPARE_FOR_BUBBLES) * \
> > > +	 IPU3_UAPI_MAX_STRIPES)
> > > +
> > > +#define IPU3_UAPI_AWB_FR_MAX_SETS			24
> > > +#define IPU3_UAPI_AWB_FR_MD_ITEM_SIZE			8
> > > +#define IPU3_UAPI_AWB_FR_BAYER_TBL_SIZE			0x100
> > > +#define IPU3_UAPI_AWB_FR_SPARE_FOR_BUBBLES \
> > > +		(IPU3_UAPI_MAX_BUBBLE_SIZE * IPU3_UAPI_MAX_STRIPES *
> \
> > > +		IPU3_UAPI_AWB_FR_MD_ITEM_SIZE)
> > > +#define IPU3_UAPI_AWB_FR_BAYER_TABLE_MAX_SIZE \
> > > +	(IPU3_UAPI_AWB_FR_MAX_SETS * \
> > > +	(IPU3_UAPI_AWB_FR_BAYER_TBL_SIZE + \
> > > +	 IPU3_UAPI_AWB_FR_SPARE_FOR_BUBBLES) * \
> > > +	IPU3_UAPI_MAX_STRIPES)
> > > +
> > > +struct ipu3_uapi_grid_config {
> > > +	__u8 width;				/* 6 or 7 (rgbs_grd_cfg) bits
> */
> > > +	__u8 height;
> > > +	__u16 block_width_log2:3;
> > > +	__u16 block_height_log2:3;
> > > +	__u16 height_per_slice:8;			/* default value 1 */
> > > +	__u16 x_start;					/* 12 bits */
> > > +	__u16 y_start;
> > > +#define IPU3_UAPI_GRID_START_MASK			((1 << 12) - 1)
> > > +#define IPU3_UAPI_GRID_Y_START_EN			(1 << 15)
> > > +	__u16 x_end;					/* 12 bits */
> > > +	__u16 y_end;
> > > +};
> >
> > You can't use bitfields in a public API. It is up to the compiler to
> > decide how to place bitfields, so this is not a stable API.
> 
> We-ell --- it's ABI dependent, yes. The sheer number of structs with bit fields
> in the header will make using the definitions rather cumbersome if not
> unwieldy. Therefore it'd be very nice to continue using bit fields.
> 
> There are certainly caveats with bit fields but using them in the user space
> interface is certainly not unforeseen. Just grep under /usr/include/linux .
> 
> Endianness is a major factor here. That said, the Intel x86 / x86-64 systems
> this driver works with are almost as certainly little endian as the world is
> round. It'd still be good to fail compilation if anyone attempts using the
> header in a big endian system.
> 
> >
> > The other thing that is broken here is 32 vs 64 bit: many of these
> > structures have different layouts depending on that. That's not going
> > to work either.
> 
> __packed needs to be added to the structs, that's for sure. Some structs will
> need padding to maintain the current layout.
> 

Ack, will add __packed attribute in v4.

> >
> > The third part is lack of documentation. Are there public datasheets?
> > If so, then you can point to that.
> 
> There will be (format) documentation to be added to the patchset but
> unfortunately it's not available yet.
> 
> >
> > Sakari, how did we do that for the omap3? I believe part of the
> > statistics etc. was in closed documentation as well. Was it documented
> > in the header or did we just refer to that closed documentation?
> 
> There are public TRMs for OMAP3 but I'm not sure if everything is
> documented there. I wonder if Laurent has some idea about that; let's check
> with him when he's back.
> 
> There is documentation for the private IOCTLs the omap3isp driver
> implements in Documentation/media/v4l-drivers/omap3isp.rst as well as the
> header file include/uapi/linux/omap3isp.h .
> 
> --
> Regards,
> 
> Sakari Ailus
> sakari.ailus@xxxxxxxxxxxxxxx



[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux