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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 393BCECAAD8 for ; Wed, 21 Sep 2022 13:19:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230217AbiIUNTM (ORCPT ); Wed, 21 Sep 2022 09:19:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38394 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229845AbiIUNTJ (ORCPT ); Wed, 21 Sep 2022 09:19:09 -0400 Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5123890C5F for ; Wed, 21 Sep 2022 06:19:08 -0700 (PDT) Received: by mail-lf1-x129.google.com with SMTP id o2so9141867lfc.10 for ; Wed, 21 Sep 2022 06:19:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date; bh=YVB1Kvz4KXx+KTfyw8w+Xp2A1fATvwLiAC4PObmzkH4=; b=EU2oEl8/dHBl2Kk6XwGi+QOaB5DgZyI61e+mLa64+CLgSGLTK2NN+IT+32aDwgdiYL iA3EEZTNET0rUYDq8/y96dcLvKaRw/gGVbDQrUo2h425XCNPsgeJccNVScdTeKkG+cRx tbQncLoxOe7QXqAo+K4BzjuP+wqcv+xKKmQjjT7lQyio2uUTlKsYqx8+x3Ek5rt1b+Xt HSrOwCjeBMng6kJvTgksCFpdAVtWCftIQ2l14uAUgmHcQsVz6d0Q0d1cAJm1/2ErfrW8 VCsWqfuXZGgaHbNE5J4G+rBecs3d/+iyXJwdInDLY7vjvq2PjY5HE1vrO7kNXNoUGweU qerA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date; bh=YVB1Kvz4KXx+KTfyw8w+Xp2A1fATvwLiAC4PObmzkH4=; b=kQcCVEkTi2QILQJ520HvySWdWtflU2dfpY6PiWwRqqB3eZ34O48GS0W3riSyr/Xvdc 7w+IpYn4Q5E/wi7BV85e1yodDFfYAgWYE/87/ke5R4S65tXFeJIUon2N17OhH+2aaol0 rMbLdvVLfBt4wxhruW13HCEf14VP0bDxXkn/yuOX73o0oeiQtj6nBi4JMXBfDxbeABGs 4Y48RO319IjnF4WOtxsDzyitD889dpAljp/xxlzkL+TE+viyq/UC+Us5CdVQ2bV+wHdz 7CIgBn5T8qRSaLWn6vOv1Vr9Bqx2nYbhnQXaQQBJZbyhz596jO6JdqRI0DH9lxvHlWCg 3vdw== X-Gm-Message-State: ACrzQf1hGYms9IupIvVGQvbISCVIbw3LdcbTISzbQy2TsjEDv09YAaC0 pJuQvii84AzhkLKl5Hv+J2CdGg== X-Google-Smtp-Source: AMsMyM6irXewtTFRf+tz3B1tmQ1RJQuEf2CWgBWeNL4RR4+2Soiwa8OF1ZTI74mqcvH83Ma8YbyF/Q== X-Received: by 2002:a05:6512:706:b0:498:b7ea:f2e8 with SMTP id b6-20020a056512070600b00498b7eaf2e8mr10200319lfs.570.1663766346581; Wed, 21 Sep 2022 06:19:06 -0700 (PDT) Received: from [192.168.0.21] (78-11-189-27.static.ip.netia.com.pl. [78.11.189.27]) by smtp.gmail.com with ESMTPSA id x8-20020a056512078800b0049468f9e697sm422248lfr.236.2022.09.21.06.19.05 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 21 Sep 2022 06:19:05 -0700 (PDT) Message-ID: <10464d03-0dd5-fec2-31ce-02af25a407da@linaro.org> Date: Wed, 21 Sep 2022 15:19:04 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Subject: Re: [PATCH v5 8/8] i2c: i2c-mlxbf.c: Update binding devicetree To: Asmaa Mnebhi Cc: Wolfram Sang , "linux-kernel@vger.kernel.org" , "robh@kernel.org" , "devicetree@vger.kernel.org" , "linux-i2c@vger.kernel.org" , Khalil Blaiech References: <20220920174736.9766-1-asmaa@nvidia.com> <20220920174736.9766-9-asmaa@nvidia.com> <20220921065506.6cu6p2cpu3zfhtie@krzk-bin> Content-Language: en-US From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 21/09/2022 15:12, Asmaa Mnebhi wrote: > I have a question for you and Wolfram, we don’t use device trees and are not planning to use device trees; we only use ACPI tables. But I think when Khalil submitted the first version of the i2c-mlxbf.c driver, it was requested from him to add devicetree support. Do you know why? Is it possible to remove the device tree support and so this doc? or is devicetree support a requirement regardless of the actual implementation? I don't think I am the right person to answer your question. I don't know why you do things and did things in your driver. I also I do not have any interest in your driver supporting anything. However if you do support DT, I have interest in its correctness. Best regards, Krzysztof