From: Rob Herring <robh@kernel.org>
To: peteryin <peteryin.openbmc@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
johnny_huang@aspeedtech.com, joel@jms.id.au,
linux-kernel@vger.kernel.org, peteryin <peter.yin@quantatw.com>,
robh+dt@kernel.org, linux-aspeed@lists.ozlabs.org,
devicetree@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
andrew@aj.id.au, eajames@linux.ibm.com
Subject: Re: [PATCH] Title: Select GPIO command source.
Date: Wed, 23 Aug 2023 12:09:46 -0500 [thread overview]
Message-ID: <169281058628.2496450.12875634767226591718.robh@kernel.org> (raw)
In-Reply-To: <20230823160810.1067102-1-peteryin.openbmc@gmail.com>
On Thu, 24 Aug 2023 00:08:10 +0800, peteryin wrote:
> From: peteryin <peter.yin@quantatw.com>
>
> Description:
> The capability to choose the GPIO command source
> between ARM LPC and Coprocessor CPU is supported.
>
> Test Plan:
> Get Bank gpio command source
> e.g.
> cd /sys/bus/platform/drivers/aspeed-command-source/
> cat 1e780000.gpio-command-source/bank_abcd
> ARM ARM ARM ARM
>
> Set Bank gpio command source.
> e.g.
> cd /sys/bus/platform/drivers/aspeed-command-source/
>
> echo "A ARM" > 1e780000.gpio-command-source/bank_abcd
> or
> echo "A LPC" > 1e780000.gpio-command-source/bank_abcd
> or$
> echo "A COP" > 1e780000.gpio-command-source/bank_abcd
>
> Signed-off-by: peteryin <peteryin.openbmc@gmail.com>
> ---
> .../sysfs-driver-aspeed-gpio-command-source | 24 ++
> .../soc/aspeed/gpio-command-source.yaml | 58 ++++
> drivers/soc/aspeed/Kconfig | 9 +
> drivers/soc/aspeed/Makefile | 1 +
> drivers/soc/aspeed/aspeed-command-source.c | 266 ++++++++++++++++++
> 5 files changed, 358 insertions(+)
> create mode 100644 Documentation/ABI/testing/sysfs-driver-aspeed-gpio-command-source
> create mode 100644 Documentation/devicetree/bindings/soc/aspeed/gpio-command-source.yaml
> create mode 100644 drivers/soc/aspeed/aspeed-command-source.c
>
My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
on your patch (DT_CHECKER_FLAGS is new in v5.13):
yamllint warnings/errors:
./Documentation/devicetree/bindings/soc/aspeed/gpio-command-source.yaml:38:3: [error] syntax error: expected <block end>, but found '?' (syntax)
./Documentation/devicetree/bindings/soc/aspeed/gpio-command-source.yaml:39:6: [error] missing starting space in comment (comments)
dtschema/dtc warnings/errors:
make[2]: *** Deleting file 'Documentation/devicetree/bindings/soc/aspeed/gpio-command-source.example.dts'
Documentation/devicetree/bindings/soc/aspeed/gpio-command-source.yaml:38:3: expected <block end>, but found '?'
make[2]: *** [Documentation/devicetree/bindings/Makefile:26: Documentation/devicetree/bindings/soc/aspeed/gpio-command-source.example.dts] Error 1
make[2]: *** Waiting for unfinished jobs....
./Documentation/devicetree/bindings/soc/aspeed/gpio-command-source.yaml:38:3: expected <block end>, but found '?'
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/soc/aspeed/gpio-command-source.yaml: ignoring, error parsing file
make[1]: *** [/builds/robherring/dt-review-ci/linux/Makefile:1500: dt_binding_check] Error 2
make: *** [Makefile:234: __sub-make] Error 2
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20230823160810.1067102-1-peteryin.openbmc@gmail.com
The base for the series is generally the latest rc1. A different dependency
should be noted in *this* patch.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit after running the above command yourself. Note
that DT_SCHEMA_FILES can be set to your schema file to speed up checking
your schema. However, it must be unset to test all examples with your schema.
next prev parent reply other threads:[~2023-08-23 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 16:08 peteryin
2023-08-23 17:09 ` Rob Herring [this message]
2023-08-23 22:17 ` Andrew Jeffery
2023-08-24 6:41 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=169281058628.2496450.12875634767226591718.robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=johnny_huang@aspeedtech.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.yin@quantatw.com \
--cc=peteryin.openbmc@gmail.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®