Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp114583iob; Tue, 17 May 2022 20:42:23 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzwbTT2oT4+QP8KK9I933o/xgeJSorTYfOQQVHhpahZV+7l2kJuY9TxswUP9/a7vXOq8O8g X-Received: by 2002:a17:90b:1809:b0:1dc:1597:20c with SMTP id lw9-20020a17090b180900b001dc1597020cmr28367233pjb.36.1652845343785; Tue, 17 May 2022 20:42:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652845343; cv=none; d=google.com; s=arc-20160816; b=WRrZZkASIZvnTBLhNaaPh78A2xXHmSd1/GlpBDRgl51Cix3oKcMMLw5Mof4kDMph+e YjoVRrzQ0d5u0TO4qgIQd9epW2+WNOLlJPgvChbNuEUjmaM6idVEc8qiza2V2OeLFfq1 cIzKFYyjc2PdxC3Klg7Btf368jwb8TYOQ9qUylEW4G+lQXsm1tACVWwOF+Dysi3nLpdp QYoPvtjPek+PGgTsrYIT5NLAeJcmUvd02K5GzZm0bCzodW/EN9BQ2t9Y1tCRTHQktULl ZkSFHpwjr/XKD5gu7ntVqWF2q/nCxU+leurz4o22bQt+35Qs1oqs7Q01Dzt4k+dIU9JW dMug== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=N19iji7Rx7bk//VnPQnTCrAIz0LW6vHaLxFF0YKeWQU=; b=PVnzMDat11h4C2Bv8NCirtQpUPFIPZPOrKao3pPZgPkJUoaog9rOkmlHof2vEk5Wet ifdDeoqomX/dkwH8DG0LRzuCnXt7/Hp9C0n5KC4kmuoMFUsjxpP7+2faqg8A/sUllgTA jsVR3n5AbMefz+QBqj/FvHN6tZdf99kik29z2V7w6P0yFEooM8AbYPJJP6qBQlNhoLzf A5aYxAmtbVZGs/BJoD17VMyjXkhQpuND4Fnbn7r3e3iZ/VR+1q9VAaXrRtNdDbdU7lyO JJq44HpBwtFJlIgNxjLqOVaDljuqrRvdJYXoZ8+k7OFRtKLsTrrNGt3Hxx36PSv7Tpl8 P8Pg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@collabora.com header.s=mail header.b=XsuIX+SC; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id c23-20020a63da17000000b003c1bb53b4b1si1109025pgh.248.2022.05.17.20.42.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 17 May 2022 20:42:23 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; dkim=pass header.i=@collabora.com header.s=mail header.b=XsuIX+SC; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id C6C286D38C; Tue, 17 May 2022 20:29:48 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1343845AbiEQKzY (ORCPT + 99 others); Tue, 17 May 2022 06:55:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46858 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233495AbiEQKzV (ORCPT ); Tue, 17 May 2022 06:55:21 -0400 Received: from bhuna.collabora.co.uk (bhuna.collabora.co.uk [46.235.227.227]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1C8A93E5C4; Tue, 17 May 2022 03:55:20 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: shreeya) with ESMTPSA id 733811F417F4 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1652784919; bh=OzW1IAdicjiRJe7jjcmuiLDwRUkXPi2uk9eLVcRy3/U=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=XsuIX+SCjnh9NhpU3jHgJJhEIq5NU9r/7/sC9RotLk/4tWeZSGzliBEa5tHryMAzh X7i87+rMQQYbRrT9j+0Vi0+M89k9d60ACL/rAR/rEGWjXdxjOjYflS75CNN24tzngh MSucP55dULCl8vIULj9QNMPxUJsltkdp9otHweppLO6uzSajxqpMinseEiOTcGef06 da8cTb4eDm7B//gutbd/F+W/74c2daYbvoq1/ZM8SpvSZFQ8QO/ZcIjT4uA722mav0 +Ti0qZa+AY1/LUlkTBRf7r9W2ezEFEiTc62SRSK01Uo6u8PAfVZXflErEA3fjhOUHY hFyypKN8iayjQ== Message-ID: Date: Tue, 17 May 2022 16:24:54 +0530 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 Subject: Re: [PATCH v4 3/3] iio: light: Add support for ltrf216a sensor Content-Language: en-US To: Dmitry Osipenko , jic23@kernel.org, lars@metafoo.de, robh+dt@kernel.org, Zhigang.Shi@liteon.com, krisman@collabora.com Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, kernel@collabora.com, alvaro.soliverez@collabora.com References: <20220511094024.175994-1-shreeya.patel@collabora.com> <20220511094024.175994-4-shreeya.patel@collabora.com> From: Shreeya Patel In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,RDNS_NONE,SPF_HELO_NONE, T_SCC_BODY_TEXT_LINE,UNPARSEABLE_RELAY autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 13/05/22 06:00, Dmitry Osipenko wrote: > 11.05.2022 12:40, Shreeya Patel пишет: >> +static int ltrf216a_set_int_time(struct ltrf216a_data *data, int itime) >> +{ >> + int i, ret, index = -1; >> + u8 reg_val; >> + >> + for (i = 0; i < ARRAY_SIZE(ltrf216a_int_time_available); i++) { >> + if (ltrf216a_int_time_available[i][1] == itime) { >> + index = i; >> + break; >> + } >> + } >> + >> + if (index < 0) >> + return -EINVAL; >> + >> + reg_val = ltrf216a_int_time_reg[index][1]; >> + data->int_time_fac = ltrf216a_int_time_reg[index][0]; >> + >> + ret = i2c_smbus_write_byte_data(data->client, LTRF216A_ALS_MEAS_RES, reg_val); >> + if (ret < 0) >> + return ret; > Should the data->int_time_fac be updated only if I2C write was successful? Yes, thanks for pointing it out. It should be updated only if write is successful. > I'm not sure what reading of LTRF216A_CLEAR_DATA reg does, but if it > clears the measured data, then shouldn't the data be cleared after > changing the config? LTRF216A_CLEAR_DATA isn't used for clearing the measured data. Name is a bit confusing and even I assumed it is being used for clearing the data. But from the datasheet, it seems that clear data registers provides light intensity data related to infrared and ultravoilet. We are currently not using this anywhere in the driver so we could remove the cleardata readings for now. Thanks, Shreeya Patel >> + data->int_time = itime; >> + >> + return 0; >> +} >