Message ID | 20230302013822.1808711-2-sboyd@kernel.org |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:5915:0:0:0:0:0 with SMTP id v21csp3979614wrd; Wed, 1 Mar 2023 17:39:42 -0800 (PST) X-Google-Smtp-Source: AK7set/hLFK5ZBs1ot/zolEET6GL245ztO0c9xRndDj05Eey5G/mqZm5zyBcqLP/xxx1oKPAfgDz X-Received: by 2002:aa7:df0b:0:b0:4bd:11d3:e86f with SMTP id c11-20020aa7df0b000000b004bd11d3e86fmr3473522edy.6.1677721182331; Wed, 01 Mar 2023 17:39:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1677721182; cv=none; d=google.com; s=arc-20160816; b=vZqoW+RIZEb1IAUxlvNIhWLaMLpm6OAM7SXgGSuYMES2dN8q9Zup3qb2dG8ylgh8kK Wr1BbvfB3A73O2qGziPb5H3zAp7xWj7VhY2wWEPmYnPvK4S+MqsxTIB0IUpG6DySwgva EQV1wAb57336r67MwDc9uXz6/1yYEsCUuXO9IiHzlLxtbYP6VUcv7N4u9SIry3ngStAY hhIxTmESoSbs/8Ss3l3rHUKtVuQjiWCFiEGSvZpKmDg+wp4DaVpS7uO985nrORs2pCoj F2u9gMNSq65QfmbFBDhBcO8GuolsF+qMbLq+zErCO7KvQEAFG+eRPLM+OZU+6xS3ONOg 50JQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=dkfreM0CCqZHeYZIGhMEOFv6eqgphqEHOeVnc5bktqY=; b=LMAi5uaryU+kYkFR2/z0igdEQkW+xWuz4D/GZM2cQp70QuQUca1aA/2/Ry5nyeY4oa kxSSd1xi49aK7LzKWbAaEQ5jY6J3eIvV69v0WtYashNDIE/HsI1wWMyROjg+dq+wlsOo pt21QevxdcVQkvXPrChFbXsxQDVQKa1wfcoc6e6tPrklpNaPN0Mp8rsUJ9PhYxQ8A2E3 Be+pniJ2lzjZNTM43uWLIrZ2zyPGu3S65pxtFSNkSO9glALsNcZui05KL1KcF49f7qtg zu2q4z+TsVZ6AtWjM2ptl3d9W7/zpCv1jB9mH99SFnsUx2MddvV9LcsykbwHbhCc0MvH lWmA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=QX5VMEDW; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id mc17-20020a170906eb5100b008b17a1f0979si16461271ejb.319.2023.03.01.17.39.17; Wed, 01 Mar 2023 17:39:42 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=QX5VMEDW; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229714AbjCBBid (ORCPT <rfc822;davidbtadokoro@gmail.com> + 99 others); Wed, 1 Mar 2023 20:38:33 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40212 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229699AbjCBBia (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Wed, 1 Mar 2023 20:38:30 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AAF8929E14; Wed, 1 Mar 2023 17:38:25 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 1E12C61542; Thu, 2 Mar 2023 01:38:25 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id CE626C43442; Thu, 2 Mar 2023 01:38:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1677721104; bh=xlmggg4SwPHgsUHI5EKsdomiaUIjY1b7gCCFhpuQ1f0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=QX5VMEDWKzXOvBrh3s5n8VNsk9WCy+BA9LU0FftVmXQFxnx9N4tmGdqqJbt4HBNC/ /Qlpzm4VHNwG1upxQs/3iAv3kEvXMUcNPICy2unmITpgwI27wshbBkaYelU99Og3/X p5YKr67RY+XlVu88alwK46oCYJX2sz1t55xB+CborNapRC+fVCStkxZLrs4vbUVQp8 VkGBUpBi7nyiEcrDtkNgaz+3/+D2JOiC74nqF8N0t5IIQy6bc7yL9zxQMfRoYpZZcU f28hGP1XZakglVR91gvvQt0gH03SKVUs98uG1rm/CYB0ImCiuK9S8Hxa9KyjMIIN1F k/5ExXHAciHDA== From: Stephen Boyd <sboyd@kernel.org> To: Michael Turquette <mturquette@baylibre.com>, Stephen Boyd <sboyd@kernel.org> Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, patches@lists.linux.dev, Brendan Higgins <brendan.higgins@linux.dev>, David Gow <davidgow@google.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, "Rafael J . Wysocki" <rafael@kernel.org>, Richard Weinberger <richard@nod.at>, Anton Ivanov <anton.ivanov@cambridgegreys.com>, Johannes Berg <johannes@sipsolutions.net>, Vincent Whitchurch <vincent.whitchurch@axis.com>, Rob Herring <robh+dt@kernel.org>, Frank Rowand <frowand.list@gmail.com>, Christian Marangi <ansuelsmth@gmail.com>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, devicetree@vger.kernel.org, linux-um@lists.infradead.org, linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com Subject: [PATCH 1/8] dt-bindings: Add linux,kunit binding Date: Wed, 1 Mar 2023 17:38:14 -0800 Message-Id: <20230302013822.1808711-2-sboyd@kernel.org> X-Mailer: git-send-email 2.39.2.722.g9855ee24e9-goog In-Reply-To: <20230302013822.1808711-1-sboyd@kernel.org> References: <20230302013822.1808711-1-sboyd@kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1759218166636995320?= X-GMAIL-MSGID: =?utf-8?q?1759218166636995320?= |
Series |
clk: Add kunit tests for fixed rate and parent data
|
|
Commit Message
Stephen Boyd
March 2, 2023, 1:38 a.m. UTC
Document the linux,kunit board compatible string. This board is loaded
into the Linux kernel when KUnit is testing devicetree dependent code.
Cc: Rob Herring <robh+dt@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Brendan Higgins <brendan.higgins@linux.dev>
Cc: David Gow <davidgow@google.com>
Signed-off-by: Stephen Boyd <sboyd@kernel.org>
---
.../bindings/kunit/linux,kunit.yaml | 24 +++++++++++++++++++
1 file changed, 24 insertions(+)
create mode 100644 Documentation/devicetree/bindings/kunit/linux,kunit.yaml
Comments
On Thu, 2 Mar 2023 at 09:38, Stephen Boyd <sboyd@kernel.org> wrote: > > Document the linux,kunit board compatible string. This board is loaded > into the Linux kernel when KUnit is testing devicetree dependent code. As with the series as a whole, this might need to change a little bit if we want to either use devicetree overlays and/or other architectures. That being said, I'm okay with having this until then: the only real topic for bikeshedding is the name. - Is KUnit best as a board name, or part of the vendor name? - Do we want to include the architecture in the name? Should it be "linux,kunit", "linux-kunit,uml", "linux,kunit-uml", etc? > > Cc: Rob Herring <robh+dt@kernel.org> > Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> > Cc: Brendan Higgins <brendan.higgins@linux.dev> > Cc: David Gow <davidgow@google.com> > Signed-off-by: Stephen Boyd <sboyd@kernel.org> > --- > .../bindings/kunit/linux,kunit.yaml | 24 +++++++++++++++++++ > 1 file changed, 24 insertions(+) > create mode 100644 Documentation/devicetree/bindings/kunit/linux,kunit.yaml > > diff --git a/Documentation/devicetree/bindings/kunit/linux,kunit.yaml b/Documentation/devicetree/bindings/kunit/linux,kunit.yaml > new file mode 100644 > index 000000000000..dfe6da4796e8 > --- /dev/null > +++ b/Documentation/devicetree/bindings/kunit/linux,kunit.yaml > @@ -0,0 +1,24 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/kunit/linux,kunit.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: KUnit > + > +maintainers: > + - Brendan Higgins <brendanhiggins@google.com> > + - David Gow <davidgow@google.com> > + > +description: > + KUnit board used to unit test the Linux kernel in User Mode Linux (UML). > + > +properties: > + $nodename: > + const: "/" > + compatible: > + const: linux,kunit > + > +additionalProperties: true > + > +... > -- > https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git/ > https://git.kernel.org/pub/scm/linux/kernel/git/sboyd/spmi.git >
Hi David, On Fri, Mar 3, 2023 at 8:16 AM David Gow <davidgow@google.com> wrote: > On Thu, 2 Mar 2023 at 09:38, Stephen Boyd <sboyd@kernel.org> wrote: > > Document the linux,kunit board compatible string. This board is loaded > > into the Linux kernel when KUnit is testing devicetree dependent code. > > As with the series as a whole, this might need to change a little bit > if we want to either use devicetree overlays and/or other > architectures. > > That being said, I'm okay with having this until then: the only real > topic for bikeshedding is the name. > - Is KUnit best as a board name, or part of the vendor name? > - Do we want to include the architecture in the name? > Should it be "linux,kunit", "linux-kunit,uml", "linux,kunit-uml", etc? I would not include an architecture (or virtualization method), as this is independent of the architecture or virtualization method. Gr{oetje,eeting}s, Geert
On Fri, 10 Mar 2023 at 07:12, Stephen Boyd <sboyd@kernel.org> wrote: > > Quoting David Gow (2023-03-02 23:14:55) > > On Thu, 2 Mar 2023 at 09:38, Stephen Boyd <sboyd@kernel.org> wrote: > > > > > > Document the linux,kunit board compatible string. This board is loaded > > > into the Linux kernel when KUnit is testing devicetree dependent code. > > > > As with the series as a whole, this might need to change a little bit > > if we want to either use devicetree overlays and/or other > > architectures. > > > > That being said, I'm okay with having this until then: the only real > > topic for bikeshedding is the name. > > - Is KUnit best as a board name, or part of the vendor name? > > - Do we want to include the architecture in the name? > > Should it be "linux,kunit", "linux-kunit,uml", "linux,kunit-uml", etc? > > I think I will drop this patch. I have overlays working. I hijacked > of_core_init() to load the testcase data from drivers/of/unittest-data > and made a container node for kunit overlays to apply to. Makes sense to me, thanks! Looking forward to seeing how the overlays work in practice!
diff --git a/Documentation/devicetree/bindings/kunit/linux,kunit.yaml b/Documentation/devicetree/bindings/kunit/linux,kunit.yaml new file mode 100644 index 000000000000..dfe6da4796e8 --- /dev/null +++ b/Documentation/devicetree/bindings/kunit/linux,kunit.yaml @@ -0,0 +1,24 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/kunit/linux,kunit.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: KUnit + +maintainers: + - Brendan Higgins <brendanhiggins@google.com> + - David Gow <davidgow@google.com> + +description: + KUnit board used to unit test the Linux kernel in User Mode Linux (UML). + +properties: + $nodename: + const: "/" + compatible: + const: linux,kunit + +additionalProperties: true + +...