Message-ID: <88a036a2-2848-41d3-a0fb-48ee14604850@kernel.org>
Date: Wed, 31 Jan 2024 09:18:10 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: "Corona, Ernesto" <ernesto.corona@...el.com>,
 "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
 "linux-arm-kernel@...ts.infradead.org"
 <linux-arm-kernel@...ts.infradead.org>,
 "linux-aspeed@...ts.ozlabs.org" <linux-aspeed@...ts.ozlabs.org>
Cc: "'oleksandrs@...lanox.com'" <oleksandrs@...lanox.com>,
 "'jiri@...dia.com'" <jiri@...dia.com>,
 "Castro, Omar Eduardo" <omar.eduardo.castro@...el.com>,
 "'omar.eduardo.castro@...ux.intel.com'"
 <omar.eduardo.castro@...ux.intel.com>, "'robh@...nel.org'"
 <robh@...nel.org>, "'corbet@....net'" <corbet@....net>,
 "'mchehab+samsung@...nel.org'" <mchehab+samsung@...nel.org>,
 "'alexandre.belloni@...tlin.com'" <alexandre.belloni@...tlin.com>,
 "'tytso@....edu'" <tytso@....edu>, "'arnd@...db.de'" <arnd@...db.de>,
 "'ebiggers@...gle.com'" <ebiggers@...gle.com>,
 "'mark.rutland@....com'" <mark.rutland@....com>,
 "'joel@....id.au'" <joel@....id.au>, "'andrew@...id.au'" <andrew@...id.au>,
 "Filary, Steven A" <steven.a.filary@...el.com>,
 "'vadimp@...lanox.com'" <vadimp@...lanox.com>,
 "'amithash@...com'" <amithash@...com>, "'patrickw3@...com'"
 <patrickw3@...com>, "Chen, Luke" <luke_chen@...eedtech.com>,
 "'billy_tsai@...eedtech.com'" <billy_tsai@...eedtech.com>,
 "'rgrs@...tonmail.com'" <rgrs@...tonmail.com>
Subject: Re: [PATCH 30 2/7] Add binding for Aspeed SOC

On 31/01/2024 00:30, Corona, Ernesto wrote:
> Aspeed AST2400, AST2500 and AST2600 JTAG controller driver.
> 
> Signed-off-by: Oleksandr Shamray <oleksandrs@...lanox.com>
> Signed-off-by: Jiri Pirko <jiri@...dia.com>
> Signed-off-by: Ernesto Corona <ernesto.corona@...el.com>
> Signed-off-by: Omar Castro <omar.eduardo.castro@...ux.intel.com>
> Acked-by: Rob Herring <robh@...nel.org>

1. There are so many wrong things with this submission that you should
drop the tag.

Please provide lore link where you received this tag. Quick look at lore
suggests you faked it.

2. Please use subject prefixes matching the subsystem. You can get them
for example with `git log --oneline -- DIRECTORY_OR_FILE` on the
directory your patch is touching.

3. Please use scripts/get_maintainers.pl to get a list of necessary
people and lists to CC. It might happen, that command when run on an
older kernel, gives you outdated entries. Therefore please be sure you
base your patches on recent Linux kernel.

Tools like b4 or scripts_getmaintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, use mainline), work on fork of kernel (don't, use
mainline) or you ignore some maintainers (really don't). Just use b4 and
everything should be fine, although remember about `b4 prep
--auto-to-cc` if you added new patches to the patchset.

You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling. Performing review on untested code might be
a waste of time, thus I will skip this patch entirely till you follow
the process allowing the patch to be tested.

Please kindly resend and include all necessary To/Cc entries.



> Cc: Jonathan Corbet <corbet@....net>
> Cc: Mauro Carvalho Chehab <mchehab+samsung@...nel.org>
> Cc: Alexandre Belloni <alexandre.belloni@...tlin.com>
> Cc: "Theodore Ts'o" <tytso@....edu>
> Cc: Arnd Bergmann <arnd@...db.de>
> Cc: Eric Biggers <ebiggers@...gle.com>
> Cc: Mark Rutland <mark.rutland@....com>
> Cc: Joel Stanley <joel@....id.au>
> Cc: Andrew Jeffery <andrew@...id.au>
> Cc: Steven Filary <steven.a.filary@...el.com>
> Cc: Vadim Pasternak <vadimp@...lanox.com>
> Cc: Amithash Prasad <amithash@...com>
> Cc: Patrick Williams <patrickw3@...com>
> Cc: Luke Chen <luke_chen@...eedtech.com>
> Cc: Billy Tsai <billy_tsai@...eedtech.com>
> Cc: Rgrs <rgrs@...tonmail.com>
> ---
> v29->v30
> Comments pointed by Steven Filary <steven.a.filary@...el.com>
> - Add Suport for 26xx series
> 
> v28->v29
> Comments pointed by Ernesto Corona <ernesto.corona@...el.com>
> - Change documentation to the new dt-bindings yaml format.
> 
> v27->v28
> v26->v27
> v25->v26
> v24->v25
> v23->v24
> v22->v23
> v21->v22
> v20->v21
> v19->v20
> v18->v19
> 
> v17->v18
> v16->v17
> v15->v16
> Comments pointed by Joel Stanley <joel.stan@...il.com>
> - change clocks = <&clk_apb> to proper clocks = <&syscon ASPEED_CLK_APB>
> - add reset descriptions in bindings file
> 
> v14->v15
> v13->v14
> v12->v13
> v11->v12
> v10->v11
> v9->v10
> v8->v9
> v7->v8
> Comments pointed by pointed by Joel Stanley <joel.stan@...il.com>
> - Change compatible string to ast2400 and ast2000
> 
> V6->v7
> Comments pointed by Tobias Klauser <tklauser@...tanz.ch>
>  - Fix spell "Doccumentation" -> "Documentation"
> 
> v5->v6
> Comments pointed by Tobias Klauser <tklauser@...tanz.ch>
> - Small nit: s/documentation/Documentation/
> 
> v4->v5
> 
> V3->v4
> Comments pointed by Rob Herring <robh@...nel.org>
> - delete unnecessary "status" and "reg-shift" descriptions in
>   bindings file
> 
> v2->v3
> Comments pointed by Rob Herring <robh@...nel.org>
> - split Aspeed jtag driver and binding to separate patches
> - delete unnecessary "status" and "reg-shift" descriptions in
>   bindings file
> ---
>  .../devicetree/bindings/jtag/aspeed-jtag.yaml | 85 +++++++++++++++++++
>  1 file changed, 85 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/jtag/aspeed-jtag.yaml
> 
> diff --git a/Documentation/devicetree/bindings/jtag/aspeed-jtag.yaml b/Documentation/devicetree/bindings/jtag/aspeed-jtag.yaml
> new file mode 100644
> index 000000000000..1a412e83b81b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/jtag/aspeed-jtag.yaml

Use filename matching compatibles, so aspeed,jtag.yaml

> @@ -0,0 +1,85 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/jtag/aspeed-jtag.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Aspeed JTAG driver for ast2400, ast2500 and ast2600 SoC
> +
> +description:
> +  Driver adds support of Aspeed 24/25/2600 series SOC JTAG controller.
> +  Driver implements the following jtag ops
> +    freq_get
> +    freq_set
> +    status_get
> +    status_set
> +    xfer
> +    mode_set
> +    bitbang
> +    enable
> +    disable
> +
> +  It has been tested on Mellanox system with BMC equipped with
> +  Aspeed 2520 SoC for programming CPLD devices.
> +
> +  It has also been tested on Intel system using Aspeed 25xx SoC
> +  for JTAG communication.
> +
> +  Tested on Intel system using Aspeed 26xx SoC for JTAG communication.
> +
> +maintainers:
> +  - Oleksandr Shamray <oleksandrs@...lanox.com>
> +  - Jiri Pirko <jiri@...dia.com>
> +  - Ernesto Corona<ernesto.corona@...el.com>
> +
> +properties:
> +  compatible:
> +    oneOf:

Drop

> +      - items:

Drop

> +          - enum:
> +              - aspeed,ast2400-jtag
> +              - aspeed,ast2500-jtag
> +              - aspeed,ast2600-jtag
> +
> +

Just one blank line. Since this was not tested, I will skip review of
the rest.

Best regards,
Krzysztof

Powered by blists - more mailing lists