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 BD006C43334 for ; Tue, 5 Jul 2022 14:51:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230042AbiGEOvM (ORCPT ); Tue, 5 Jul 2022 10:51:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44684 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229492AbiGEOvL (ORCPT ); Tue, 5 Jul 2022 10:51:11 -0400 Received: from mail-io1-f44.google.com (mail-io1-f44.google.com [209.85.166.44]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2FEA413E10; Tue, 5 Jul 2022 07:51:11 -0700 (PDT) Received: by mail-io1-f44.google.com with SMTP id l24so11288089ion.13; Tue, 05 Jul 2022 07:51:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=4pr9idqRA1hITkupO1aLjT1dL1RQ3YrTUVMjd+qhvbk=; b=n+nzCT8v6lUIkuTShVwTvgoItpDBz9PHXlN1JzvvCwlZapw9ZVknukX8bC6jVsTp4H JZvkmHzsSUxQT5ehQDIQMn/RsSIAAk5NvoS4YnAo092zzbMcoYuxVUQ/+Ak3oHzxKu3N UIuftk+rP90yPYWVO49reDqqIPktdJLZfNqhqRZ8bFzHVVvU0QB2siMAJ8wl349ZAulH LH0SZu7BUZpVSq68RTCAgDaqvpMvTuUCwA7iMYJ/4lIivG2OjroACwaksg5yEHVatSAG Q/NLgSjeItkMv/wVU7JAav4Gp7GLPuZciKXBUYClB8XyD+SQwFWW12s8DuVJGppJOZtC Ai6g== X-Gm-Message-State: AJIora/i61bmDgFLWovC39plUbpSyWdybD4Q7o6f5SjUV+NnfAxpPwhP u2/WJWC2lvFb7eut1n3x+g== X-Google-Smtp-Source: AGRyM1usxj6oworCSQ3my3IZbWYltLVQEQI3Tbb80lTn0GWANP6QD16VjKVUHzGUJq5sHQwNSOmlmQ== X-Received: by 2002:a5d:914b:0:b0:672:6629:bfa2 with SMTP id y11-20020a5d914b000000b006726629bfa2mr18823204ioq.159.1657032670453; Tue, 05 Jul 2022 07:51:10 -0700 (PDT) Received: from robh.at.kernel.org ([64.188.179.248]) by smtp.gmail.com with ESMTPSA id o62-20020a022241000000b00339de279a5bsm14776485jao.126.2022.07.05.07.51.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 05 Jul 2022 07:51:10 -0700 (PDT) Received: (nullmailer pid 2089291 invoked by uid 1000); Tue, 05 Jul 2022 14:51:08 -0000 Date: Tue, 5 Jul 2022 08:51:08 -0600 From: Rob Herring To: Geert Uytterhoeven , Krzysztof Kozlowski Cc: Magnus Damm , Krzysztof Kozlowski , Alim Akhtar , Nishanth Menon , Vignesh Raghavendra , Tero Kristo , Linux-Renesas , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Linux Kernel Mailing List , Linux ARM , linux-samsung-soc Subject: Re: [PATCH v2 0/2] dt-bindings: hwinfo: group devices and add s5pv210-chipid Message-ID: <20220705145108.GA2083998-robh@kernel.org> References: <20220703183449.12917-1-krzysztof.kozlowski@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-samsung-soc@vger.kernel.org On Mon, Jul 04, 2022 at 09:18:31AM +0200, Geert Uytterhoeven wrote: > Hi Krzysztof, > > On Sun, Jul 3, 2022 at 8:35 PM Krzysztof Kozlowski > wrote: > > As suggested by Rob [1], I organized a bit bindings for SoC devices having > > similar purpose - chip identification. What's the base? It didn't apply for me. > > > > These sometimes are put under nvmem directory, although in that case the > > purpose is usually broader than just chipid. > > Thanks for your series! > > > dt-bindings: hwinfo: group Chip ID-like devices > > dt-bindings: hwinfo: samsung,s5pv210-chipid: add S5PV210 ChipID > > So why not call it "chipid"? > "hwinfo" sounds too generic to me; aren't all DT bindings hardware > information? I'm fine with hwinfo as the color of the shed. I don't think we should encode where the information comes from. Rob 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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 4C981C433EF for ; Tue, 5 Jul 2022 14:52:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=3ss/5upH2fIbowbVUAcr6mlT2edi4t6XdBMNtsHSRao=; b=yGj8qcefohofOn Tkdl43G0qjspc9Z87znYYafi4TiLH+Nk9/kFz7Pv6VmAjGPlOhRAnfqbGTzuiorUenCoPY+JA3by7 O5K1abKoLKmZUnGrFI3fEDR8C1A9Ds9yqE8BLZfyiLHb66o99LZUb0iYK154nQ2u4XmX4fFyPgHdK iuuKPu5c680LG/2jcxNaWdlJJU0NOetULdnAbwMnBafLF/qNE9WwHoB/K9L4BuqwOExYLHPxEEJyX mjzkcT1k1xOPYyRMrBZ7OQmKMCxIrEMZhMvWiVvVnae3encGBrGYnBSvKn8jCABDXkIj0n7+0BYpb ysYwlQIV0Gtv+Qt1iuVw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1o8jtS-000xHS-R3; Tue, 05 Jul 2022 14:51:14 +0000 Received: from mail-io1-f48.google.com ([209.85.166.48]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1o8jtP-000xGb-QM for linux-arm-kernel@lists.infradead.org; Tue, 05 Jul 2022 14:51:13 +0000 Received: by mail-io1-f48.google.com with SMTP id y18so11311951iof.2 for ; Tue, 05 Jul 2022 07:51:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=4pr9idqRA1hITkupO1aLjT1dL1RQ3YrTUVMjd+qhvbk=; b=mY52Ez7znqZkKYKoXdTpFhZoMP8PG4cyclGdGLj+urQEaaAtutBEEhU/Os797zfMaa KBwrcrl/z30eqjb6dw8mPU2SGR+uy42hYSQ344KxnNkLZXpEtJAg/AP1fgklzTRcGrAa ssrie1U90vDXmV4xBDJsKM2TuVGMWKCTQqof7VDLI5k6E8JowZmwzMSDI3hAP+rc11AC 35g86jtJW+lUkZZLatZCuFfYRvDymQhouWJZHugH3zieLLJvHQH1fcsuLwFXQ2TVUDup HgFb7Jk4XjK++L1wqB+vv1vBUKSTYWNMxggYkMOwvjBPtE3GlI3H3jUGCmQZPmqarYZZ bCaQ== X-Gm-Message-State: AJIora+/NiyYMPorr+mWS+/CQsCI3MC8SbVeA2tXx+3qCb0EJW4gTHe1 tJxCJTT57uREaAOdrkn9iw== X-Google-Smtp-Source: AGRyM1usxj6oworCSQ3my3IZbWYltLVQEQI3Tbb80lTn0GWANP6QD16VjKVUHzGUJq5sHQwNSOmlmQ== X-Received: by 2002:a5d:914b:0:b0:672:6629:bfa2 with SMTP id y11-20020a5d914b000000b006726629bfa2mr18823204ioq.159.1657032670453; Tue, 05 Jul 2022 07:51:10 -0700 (PDT) Received: from robh.at.kernel.org ([64.188.179.248]) by smtp.gmail.com with ESMTPSA id o62-20020a022241000000b00339de279a5bsm14776485jao.126.2022.07.05.07.51.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 05 Jul 2022 07:51:10 -0700 (PDT) Received: (nullmailer pid 2089291 invoked by uid 1000); Tue, 05 Jul 2022 14:51:08 -0000 Date: Tue, 5 Jul 2022 08:51:08 -0600 From: Rob Herring To: Geert Uytterhoeven , Krzysztof Kozlowski Cc: Magnus Damm , Krzysztof Kozlowski , Alim Akhtar , Nishanth Menon , Vignesh Raghavendra , Tero Kristo , Linux-Renesas , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Linux Kernel Mailing List , Linux ARM , linux-samsung-soc Subject: Re: [PATCH v2 0/2] dt-bindings: hwinfo: group devices and add s5pv210-chipid Message-ID: <20220705145108.GA2083998-robh@kernel.org> References: <20220703183449.12917-1-krzysztof.kozlowski@linaro.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220705_075111_894656_52875348 X-CRM114-Status: GOOD ( 16.78 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, Jul 04, 2022 at 09:18:31AM +0200, Geert Uytterhoeven wrote: > Hi Krzysztof, > > On Sun, Jul 3, 2022 at 8:35 PM Krzysztof Kozlowski > wrote: > > As suggested by Rob [1], I organized a bit bindings for SoC devices having > > similar purpose - chip identification. What's the base? It didn't apply for me. > > > > These sometimes are put under nvmem directory, although in that case the > > purpose is usually broader than just chipid. > > Thanks for your series! > > > dt-bindings: hwinfo: group Chip ID-like devices > > dt-bindings: hwinfo: samsung,s5pv210-chipid: add S5PV210 ChipID > > So why not call it "chipid"? > "hwinfo" sounds too generic to me; aren't all DT bindings hardware > information? I'm fine with hwinfo as the color of the shed. I don't think we should encode where the information comes from. Rob _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel