From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-qt0-f193.google.com ([209.85.216.193]:35487 "EHLO mail-qt0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755260AbeCHKAr (ORCPT ); Thu, 8 Mar 2018 05:00:47 -0500 MIME-Version: 1.0 In-Reply-To: References: <1514533978-20408-1-git-send-email-zhengsq@rock-chips.com> <1514533978-20408-4-git-send-email-zhengsq@rock-chips.com> From: Jacob Chen Date: Thu, 8 Mar 2018 18:00:45 +0800 Message-ID: Subject: Re: [PATCH v5 03/16] media: rkisp1: Add user space ABI definitions To: Hans Verkuil Cc: Shunqian Zheng , "open list:ARM/Rockchip SoC..." , Linux Media Mailing List , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Mauro Carvalho Chehab , Sakari Ailus , Hans Verkuil , Tomasz Figa , Laurent Pinchart , =?UTF-8?B?6ZKf5Lul5bSH?= , Eddie Cai , Jeffy Chen , Allon Huang , devicetree@vger.kernel.org, Heiko Stuebner , robh+dt@kernel.org, Joao Pinto , Luis Oliveira , Jose Abreu Content-Type: text/plain; charset="UTF-8" Sender: linux-media-owner@vger.kernel.org List-ID: Hi Hans, 2018-02-07 20:00 GMT+08:00 Hans Verkuil : > On 12/29/17 08:52, Shunqian Zheng wrote: >> From: Jeffy Chen >> >> Add the header for userspace > > General note: I saw four cases where this documentation referred to the > datasheet. Three comments on that: > > 1) You don't say which datasheet. > 2) I assume the datasheet is under NDA? This datasheet can't be got by customers, even under NDA. > 3) You do need to give enough information so a reasonable default can be > used. I mentioned in an earlier review that creating an initial params > struct that can be used as a templete would be helpful (or even > required), and that would be a good place to put such defaults. > It don't need a default config For applcation writers, they can just init it with zero data, and only set value for the part they concerned. As for ABI, i have checked there is no mismatches. Those structures is 32 bit aligned both in 64bit/32bit env, since there is no 64bit value. "__attribute__ ((packed))" can avoid mismatches happen when we add a 64bit value to those structures. As robin said, enums and bools are not guaranteed to be consistent between different compiler, so it's a potential risk. I have replace bools with unsigned char and enums with unsigned int. > Regards, > > Hans