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 A82EFC433EF for ; Tue, 29 Mar 2022 17:15:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240092AbiC2RQt (ORCPT ); Tue, 29 Mar 2022 13:16:49 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50776 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236314AbiC2RQp (ORCPT ); Tue, 29 Mar 2022 13:16:45 -0400 Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A22F4606F9 for ; Tue, 29 Mar 2022 10:15:02 -0700 (PDT) Received: by mail-ej1-x636.google.com with SMTP id yy13so36504693ejb.2 for ; Tue, 29 Mar 2022 10:15:02 -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=u4/Xoq8QX2+BSN1akZ5eJ0B56WB/4G+OnIBGzph+8D8=; b=Uqle8LLPZRhi7EFrBAFaa3v0GJirU8cirdL4/0+sEr4luHTyY44LMh/eNY2bjY14q4 aYAHCvphytwYlzNtmOVjY5J4zofpkdMkXDH27OhFhaSXwqoLQmnrckfUaxTK7keEbL9a vFfm5O4zrJEMHp+P3J/Lab5BUDEWoYXhs/oswOmVGtVQwyE15ol0UN/UR3+qI/Nht4dH yHJ1loyFFR4NMMEhc5VaHdSzS+uoWlngIPdGKGZ3MBO6Tz8dcC7tnhnZ/bPvLUERAe7W lIpZ9vj6gg93r/xmvrzO9tKZG2p3ZtLRRwodCX8rEUemAUhC+DOftKx/q/jL1LABxcW6 g5dg== 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=u4/Xoq8QX2+BSN1akZ5eJ0B56WB/4G+OnIBGzph+8D8=; b=viKC35eav560UCbUvvCTdn3lAlOVxGWiNzl+raaE8czLcCyj0XwwHvLwy+uMyrchXa Xgj6Gb+w1ndH/CeeKgcEPTjCkaQQvJq17cTknl2mJLCc9q6VTSMMPFXM/9D0PIr43Blu ZDfC3d6HI+gYccoLaX3Qsf+udgxTWDW2weeTspecsUNWhOQRQezfzJcJ4cR6pPEVu5/e pORZ7I3RAAaLKiPshKyxK8GsQEQQQAw07CsjrFMxXFEvQAluDccGQRhIQrqGkxFBGheo +nMeGUzL/6vTpNPlW1L6QrL4r7Q+LqQf+YceJ1O1AluhdR0GCbDrMH0MxrrQ4WLfNlST EQWw== X-Gm-Message-State: AOAM532hDcZdY1/MVbkokoJSdcIKBkSeYwN44Qfm1B3+sM6JzoWxdCQ0 iJswzvOvGVjl05+07uGeypFL5Q== X-Google-Smtp-Source: ABdhPJyO+8+whle+3kOlbJHCsgtYjuqBeH8vGylEvAwP94rgXmdsghv9CEj0b2o9qYXnTEPXWCihvg== X-Received: by 2002:a17:907:6093:b0:6e0:dabf:1a9f with SMTP id ht19-20020a170907609300b006e0dabf1a9fmr20867752ejc.424.1648574100077; Tue, 29 Mar 2022 10:15:00 -0700 (PDT) Received: from [192.168.0.162] (xdsl-188-155-201-27.adslplus.ch. [188.155.201.27]) by smtp.gmail.com with ESMTPSA id e26-20020a50ec9a000000b004193fe50151sm8782747edr.9.2022.03.29.10.14.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 29 Mar 2022 10:14:59 -0700 (PDT) Message-ID: Date: Tue, 29 Mar 2022 19:14:58 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: [PATCH RFC] dt-bindings: PCI: mediatek-gen3: Remove clock-names Content-Language: en-US To: Jianjun Wang , Bjorn Helgaas , Rob Herring , Matthias Brugger Cc: Ryder Lee , linux-pci@vger.kernel.org, linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, "allen-kh . cheng" References: <20220329071526.10298-1-jianjun.wang@mediatek.com> From: Krzysztof Kozlowski In-Reply-To: <20220329071526.10298-1-jianjun.wang@mediatek.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 29/03/2022 09:15, Jianjun Wang wrote: > Some SoC may have different clocks (e.g. MT8192 uses clock 'top_133m', > but MT8195 use clock 'peri_mem' instead), since these clocks do not have > any timing dependencies and the PCIe controller driver uses > 'devm_clk_bulk_get_all' to gets all of them, remove 'clock-names' in > dt-bindings file for compatible with different SoCs. One driver behaves like this, other different. Driver implementation might not be a reliable source. :) The clock entries are expected to be ordered and fixed, so clock-names should stay. Best regards, Krzysztof