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 54FA7C433EF for ; Wed, 6 Apr 2022 12:10:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231815AbiDFML7 (ORCPT ); Wed, 6 Apr 2022 08:11:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36178 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231575AbiDFMLu (ORCPT ); Wed, 6 Apr 2022 08:11:50 -0400 Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 97AF840FFAB for ; Wed, 6 Apr 2022 00:55:59 -0700 (PDT) Received: by mail-ed1-x534.google.com with SMTP id c42so1623618edf.3 for ; Wed, 06 Apr 2022 00:55:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=message-id:date:mime-version:user-agent:subject:content-language :from:to:cc:references:in-reply-to:content-transfer-encoding; bh=7r2ffZ+ymB7DSx9Uk93kfN7lmzvxR8eXYAcNA9ceeys=; b=zxFruS8gRL4tPtU8Ut5n9NTDlAjFzRntseZuBWseA3iiTjEkVVbIBatFpgMTJbydoN RM+y5vY/M6WExNM9DIWWTxua06tXakZqJk0uvOu9DkFPsijYYv+NI6C/50DIFmKVa2W6 Nf9YbvhOHYPxyhPSknarhpoLXa6M7mz3hZA79uJUnMcMuYbC/Y7mgMyRzUERjwppCZv7 A+7eWm6Ovx4+l44bjrukgViG+oGEua7/hVvndipD5EflBZxz28tGMFpSUeKVCkdXnIA7 2Du3YqWSjeqyoUVc3a9bykwvyf95KU2gzkx6Qq/2L/aTChNA1iGqtSXSXQ10CrSTscr2 xR+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:from:to:cc:references:in-reply-to :content-transfer-encoding; bh=7r2ffZ+ymB7DSx9Uk93kfN7lmzvxR8eXYAcNA9ceeys=; b=rXOj8XELl1fgc7k++FPVL3ukKfOcrpkzaRs1nXbS5Kkjphl5kiIH/7+2DDIz70ElP0 cYJ70a815mEcG+aazSoeOBl4ybKfVfCPJXTyMfAW5YPgBS54pcGAiC8HHKLwJsSOAn20 r8/tJBDOJWWw6Z4EB8RdepsaH/cW2vKt6kLLGA4pLBLEhZAy5BZR4bIwuRdbeXR10fPe HFG2dyd9BKu6H7mLzTMLAyMoJ6LckDOfs2fIRzQw6eibmKLdM/KF2wVjujQAPLuh6KzC jCA5C2c3VC+ndMF9ua7pxNXOi1NAidIvW//NydtNqynH/9on+KCjiERcMT2VOxDSgQ+w bpvg== X-Gm-Message-State: AOAM5312dVgRh0POAgOtl5de2Tex/Ld358ZE5LW7ZFcJ35iaFrOnYWJ8 +C1EmO32Pc/Mrois86zgKzj+Tw== X-Google-Smtp-Source: ABdhPJzz9acBp2KtEvdtZLSTA2T1pnx8GCYRU6b4yCNpabNmCToBUtduaSjaDpyT7qBPsD4vc0i8nQ== X-Received: by 2002:a50:9d47:0:b0:40f:9d3d:97b6 with SMTP id j7-20020a509d47000000b0040f9d3d97b6mr7487089edk.392.1649231758115; Wed, 06 Apr 2022 00:55:58 -0700 (PDT) Received: from [192.168.0.182] (xdsl-188-155-201-27.adslplus.ch. [188.155.201.27]) by smtp.gmail.com with ESMTPSA id qq21-20020a17090720d500b006e7eec5c96csm3485199ejb.0.2022.04.06.00.55.57 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Apr 2022 00:55:57 -0700 (PDT) Message-ID: Date: Wed, 6 Apr 2022 09:55:56 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: [PATCH 1/2] i2c: add binding to prevent device detection Content-Language: en-US From: Krzysztof Kozlowski To: Vincent Whitchurch Cc: "wsa@kernel.org" , kernel , "linux-i2c@vger.kernel.org" , "devicetree@vger.kernel.org" , "krzk+dt@kernel.org" , "robh+dt@kernel.org" , "linux-kernel@vger.kernel.org" References: <20220405121627.1560949-1-vincent.whitchurch@axis.com> <20220405121627.1560949-2-vincent.whitchurch@axis.com> <20220405141255.GD28574@axis.com> <315c957b-8d22-dcef-a5b8-36e92f0897be@linaro.org> In-Reply-To: <315c957b-8d22-dcef-a5b8-36e92f0897be@linaro.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 06/04/2022 09:26, Krzysztof Kozlowski wrote: >> >> I'm having a hard time drawing the line between hardware and the >> "system" here. The bus being completely described in devicetree doesn't >> sound like a hardware property to me, but, yes, I can change the >> description to say that. > > Then you need to come up with better description. :) By system I > understood here Operating System, therefore a Software piece or pieces. > Bindings should not rather focus on hardware instead of referencing > software. Ah... I meant: Bindings should rather focus on hardware instead of referencing software. > Software actually not matter for the bindings... There is > quite clear distinction between hardware and operating system... > > Can you explain why do you think "bus being completely described" is not > a hardware description? Bindings and DTS describe hardware, so one of > parts of such description is whether nodes and other properties are > present. If all child nodes are present in DT - no-detect - and this is > a purely hardware point of view. No software here. Best regards, Krzysztof