From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-15.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E547FC433F5 for ; Tue, 21 Sep 2021 11:34:34 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C242B61186 for ; Tue, 21 Sep 2021 11:34:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232386AbhIULgB (ORCPT ); Tue, 21 Sep 2021 07:36:01 -0400 Received: from perceval.ideasonboard.com ([213.167.242.64]:40030 "EHLO perceval.ideasonboard.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229474AbhIULgB (ORCPT ); Tue, 21 Sep 2021 07:36:01 -0400 Received: from pendragon.ideasonboard.com (62-78-145-57.bb.dnainternet.fi [62.78.145.57]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id 82E272BA; Tue, 21 Sep 2021 13:34:31 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1632224072; bh=YehxWHHvd2yMOMQGC3eNWYHgGaI2Mgpxz1mm3tYyt40=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=HGWc+atcv4Xz6M/DjHSelFxflkmrIf9NZN7SkM5x3rYBEsYsciGnrHZPzjcn+Sfa+ wTnqxpc8lR2fzqmkhoTDBMNEHTIfDwm3mrC+M21vuhVlYgn4zg/3JH+5Xxhl+Nef3V cxpqNCEYUTqLGbzbn75holiPTUMXYYVLbaitoNW0= Date: Tue, 21 Sep 2021 14:33:59 +0300 From: Laurent Pinchart To: Bingbu Cao , bingbu.cao@intel.com Cc: Jean-Michel Hautbois , Tian Shu Qiu , sakari.ailus@linux.intel.com, linux-media@vger.kernel.org, Tomasz Figa Subject: Re: [RFC PATCH] media: staging: ipu3-imgu: add the AWB memory layout Message-ID: References: <20210831185140.77400-1-jeanmichel.hautbois@ideasonboard.com> <491ab306-2b40-3b3e-fc46-d7af2de3db26@ideasonboard.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <491ab306-2b40-3b3e-fc46-d7af2de3db26@ideasonboard.com> Precedence: bulk List-ID: X-Mailing-List: linux-media@vger.kernel.org Hello, On Thu, Sep 09, 2021 at 07:52:46AM +0200, Jean-Michel Hautbois wrote: > On 09/09/2021 04:19, Bingbu Cao wrote: > > On 9/8/21 4:17 PM, Laurent Pinchart wrote: > >> On Wed, Sep 01, 2021 at 12:34:00AM +0300, Laurent Pinchart wrote: > >>> On Tue, Aug 31, 2021 at 08:51:40PM +0200, Jean-Michel Hautbois wrote: > >>>> While parsing the RAW AWB metadata, the AWB layout was missing to fully > >>>> understand which byte corresponds to which feature. Make the field names > >>>> and usage explicit, as it is used by the userspace applications. > >>>> > >>>> Signed-off-by: Jean-Michel Hautbois > >>>> --- > >>>> This structure layout is defined in CrOs: > >>>> https://chromium.googlesource.com/chromiumos/platform/arc-camera/+/refs/heads/master/hal/intel/include/ia_imaging/awb_public.h > >>>> > >>>> There are a few things not really understood right now: > >>>> - Is sat_ratio a full scale ratio (I can't get more than some values out > >>>> of it, is it a ratio of 25%, 50%, 75%, 100% ?) > >>>> - What are the real minimum and maximum values for the grid size ? From > >>>> CrOs it appears to be [16, 80] for width and [16, 60] for height while > >>>> in this file it seems to be [16, 160] for width and not really defined > >>>> for height AFAICT ? > >>>> - Same for the block_width_log2 and block_height_log2 which are [3, 7] > >>>> in this file and [3, 6] in the awb_public.h header ? > > Do you have any clue for those questions please :-) ? This is becoming a blocker, it would be really nice if we could have answers to these questions. The grid size constraints are the most immediate priority, but understanding the sat_ratio value will be next veyr shortly. > >>>> > >>>> .../media/ipu3/include/uapi/intel-ipu3.h | 38 ++++++++++++++----- > >>>> 1 file changed, 29 insertions(+), 9 deletions(-) > >>>> > >>>> diff --git a/drivers/staging/media/ipu3/include/uapi/intel-ipu3.h b/drivers/staging/media/ipu3/include/uapi/intel-ipu3.h > >>>> index fa3d6ee5adf2..83191aff2ddd 100644 > >>>> --- a/drivers/staging/media/ipu3/include/uapi/intel-ipu3.h > >>>> +++ b/drivers/staging/media/ipu3/include/uapi/intel-ipu3.h > >>>> @@ -61,20 +61,40 @@ struct ipu3_uapi_grid_config { > >>>> __u16 y_end; > >>>> } __packed; > >>>> > >>>> +/** > >>>> + * struct ipu3_uapi_awb_raw_buffer - Memory layout for each cell in AWB > >>>> + * > >>>> + * @Gr_avg: Green average for red lines in the cell. > >>>> + * @R_avg: Red average in the cell. > >>>> + * @B_avg: Blue average in the cell. > >>>> + * @Gb_avg: Green average for blue lines in the cell. > >>>> + * @sat_ratio: Saturation ratio in the cell. > >>>> + * @padding0: Unused byte for padding. > >>>> + * @padding1: Unused byte for padding. > >>>> + * @padding2: Unused byte for padding. > >>>> + */ > >>>> +struct ipu3_uapi_awb_raw_buffer { > >>>> + unsigned char Gr_avg; > >>>> + unsigned char R_avg; > >>>> + unsigned char B_avg; > >>>> + unsigned char Gb_avg; > >>>> + unsigned char sat_ratio; > >>>> + unsigned char padding0; > >>>> + unsigned char padding1; > >>>> + unsigned char padding2; > > > > It is fine for me to define and exposure the awb memory layout in uAPI. > > > > nit: use __u8 here? > > Sure ! > > >>>> +} __packed; > >>>> + > >>>> /* > >>>> * The grid based data is divided into "slices" called set, each slice of setX > >>>> * refers to ipu3_uapi_grid_config width * height_per_slice. > >>>> */ > >>>> #define IPU3_UAPI_AWB_MAX_SETS 60 > >>>> -/* Based on grid size 80 * 60 and cell size 16 x 16 */ > >>>> -#define IPU3_UAPI_AWB_SET_SIZE 1280 > >>>> -#define IPU3_UAPI_AWB_MD_ITEM_SIZE 8 > >>>> -#define IPU3_UAPI_AWB_SPARE_FOR_BUBBLES \ > >>>> - (IPU3_UAPI_MAX_BUBBLE_SIZE * IPU3_UAPI_MAX_STRIPES * \ > >>>> - IPU3_UAPI_AWB_MD_ITEM_SIZE) > >>>> +#define AWB_PUBLIC_NUM_OF_ITEMS_IN_SET 160 > >>>> +/* Based on max grid height + Spare for bubbles */ > >>>> +#define AWB_PUBLIC_NUM_OF_SETS_IN_BUFFER IPU3_UAPI_AWB_MAX_SETS + \ > >>>> + (IPU3_UAPI_MAX_BUBBLE_SIZE * IPU3_UAPI_MAX_STRIPES) > >>>> #define IPU3_UAPI_AWB_MAX_BUFFER_SIZE \ > >>>> - (IPU3_UAPI_AWB_MAX_SETS * \ > >>>> - (IPU3_UAPI_AWB_SET_SIZE + IPU3_UAPI_AWB_SPARE_FOR_BUBBLES)) > >>>> + AWB_PUBLIC_NUM_OF_SETS_IN_BUFFER * AWB_PUBLIC_NUM_OF_ITEMS_IN_SET > > > > It's better to update the name of 'IPU3_UAPI_AWB_MAX_BUFFER_SIZE' to align current > > definition. > > > >>>> > >>>> /** > >>>> * struct ipu3_uapi_awb_raw_buffer - AWB raw buffer > >>>> @@ -83,7 +103,7 @@ struct ipu3_uapi_grid_config { > >>>> * the average values for each color channel. > >>>> */ > >>>> struct ipu3_uapi_awb_raw_buffer { > >>>> - __u8 meta_data[IPU3_UAPI_AWB_MAX_BUFFER_SIZE] > >>>> + struct ipu3_uapi_awb_raw_buffer meta_data[IPU3_UAPI_AWB_MAX_BUFFER_SIZE] > >>>> __attribute__((aligned(32))); > >>>> } __packed; > >>>> -- Regards, Laurent Pinchart