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 51251CCA47F for ; Mon, 4 Jul 2022 07:21:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229826AbiGDHVk (ORCPT ); Mon, 4 Jul 2022 03:21:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48524 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232837AbiGDHVj (ORCPT ); Mon, 4 Jul 2022 03:21:39 -0400 Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A7C725F4E for ; Mon, 4 Jul 2022 00:21:37 -0700 (PDT) Received: by mail-lf1-x12d.google.com with SMTP id t24so14281913lfr.4 for ; Mon, 04 Jul 2022 00:21:37 -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:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=vln6HYgiS3ToTvJf9Q6ri+cW27TKxOvsHNd6WycR420=; b=eoA4egyRuz1FU+dmRUIeJh0HTBAZQs5Unex7A+9NMQ7tbPwSXDKUYSW9bCUMYEwP6N VzVQ+DmicZJglQFaE6rpnuAH+038u4AFz1O6cX+auJnidMYHnvkWW4l35ZdAA6MIZEXh lFugyazM5acdQIO78FISQtbZDjGQ46b8rfiCRL13dBp9I+qDvTNNeX1q2OeCVP4wbYk+ Rhq7G4nQct7sjAumoq8FYP3QfuPEJhvXCHmQ72kxC8x2SjH+Y/9GQ8D4IYPsEvGcGosM IgUJGUGgz+8809WVZnv97am9NezaggPdWd4XJ/sGaKUWbLhEJRUKVnXy5/ZJy6K5fjgo Hk/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:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=vln6HYgiS3ToTvJf9Q6ri+cW27TKxOvsHNd6WycR420=; b=KgNjQR9aajKhBHN9bmJ7m0Ltv4JI6W2XxizzBmJZ5i2RNDSlH8vUEAIfJu+4pjcQWN eKQG4D/9Z3GCn+Zc3PGmeoUIzvFaWOdF8hhbcI4nLuM56yuqPe4mdsNQ8vHkQ0HrfmUc FvNxTUYGtSSE/LkuORwMWhOw/uvEfnvXBg/H3iiNDctHBshntLQ84updyLaCVSKqGGQw wjB0NNHv2ZeEspOG/1tku2Td7hTG7ynujzTlw4WkP2KmZS1zXMDZldu9QnHwrf/b18rJ vDMlpLosa3wNTSGsg6xGhC0vKq1fbOXEduF5oRTmPBeu3A6ftrefnm3DXT/lGhUyRP2+ XFvA== X-Gm-Message-State: AJIora/Xs9+4CxAfHcMgGaelHxB3IPOpKeHOuN1Ed539hBAM8ZlUtbqm 2f7s1QOrWH1bdXbuN3pcy1TpYQ== X-Google-Smtp-Source: AGRyM1vwulbGf0wEriyCwvzBATzx/6SXMvjbcrsCvVa6M/FuBcUc/A1FI7JhSiDe2KlM+1Tgtc4Obg== X-Received: by 2002:a05:6512:3b06:b0:481:507e:e3a0 with SMTP id f6-20020a0565123b0600b00481507ee3a0mr15079502lfv.616.1656919296028; Mon, 04 Jul 2022 00:21:36 -0700 (PDT) Received: from [192.168.1.52] ([84.20.121.239]) by smtp.gmail.com with ESMTPSA id bi16-20020a05651c231000b0025a66b3fc45sm4853780ljb.97.2022.07.04.00.21.34 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 04 Jul 2022 00:21:35 -0700 (PDT) Message-ID: <2b6427ba-9afc-b1b4-0862-6857bb346878@linaro.org> Date: Mon, 4 Jul 2022 09:21:34 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: [PATCH v2 0/2] dt-bindings: hwinfo: group devices and add s5pv210-chipid Content-Language: en-US To: Geert Uytterhoeven Cc: Magnus Damm , Rob Herring , 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 References: <20220703183449.12917-1-krzysztof.kozlowski@linaro.org> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 04/07/2022 09:18, 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. >> >> 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? If it is too specific, some other similar drivers won't perfectly match thus they will be placed again under dt-bindings/soc. I was thinking about name "socinfo", but on the other hand why limiting to SoC? I think there are many more devices which provide some kind of read-only hardware information (type, revision, product ID, model etc), therefore - hwinfo. Thanks for the feedback. Best regards, Krzysztof