From: Jon Lin <jon.lin@rock-chips.com>
To: Johan Jonker <jbx6244@gmail.com>, broonie@kernel.org
Cc: heiko@sntech.de, linux-spi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
kernel@esmil.dk
Subject: Re: [PATCH v3 3/8] dt-bindings: spi: spi-rockchip: add description for rv1126
Date: Mon, 7 Jun 2021 14:36:01 +0800 [thread overview]
Message-ID: <9d6c9b33-2e56-430b-0ea7-df0ebc0a16b4@rock-chips.com> (raw)
In-Reply-To: <4d60a524-5a54-f972-7605-25db3b825cfa@gmail.com>
On 6/6/21 4:30 AM, Johan Jonker wrote:
> Hi Jon,
>
> Some comments. Have a look if it's useful.
>
> ===
>
> In order to get this patch reviewed by rob+dt you must include:
> robh+dt@kernel.org
> devicetree@vger.kernel.org
>
> Check your review status here:
> https://patchwork.ozlabs.org/project/devicetree-bindings/list/
>
> Get the other lists and maintainers with:
> ./scripts/get_maintainer.pl --noroles --norolestats --nogit-fallback
> --nogit <patch1> <patch2>
done.
> ===
>
> Please try to order patches like:
> (1) dt-binding - compatible addition
> (2) driver patches
> (3) devicetree node patches
>
> The script below gives a warning if the wrong order is used.
> ./scripts/checkpatch.pl --strict <patch1> <patch2>
done.
> ===
>
> The [PATCH v3 2/8] has duplicate Signed-off-by's.
>
> Signed-off-by: Jon Lin <jon.lin at rock-chips.com>
> Signed-off-by: Jon Lin <jon.lin at rock-chips.com>
>
> What has changed in version 3 ?
> Maybe add a cover letter and a change log too?
> git format-patch -v4 -8 --cover-letter HEAD
done.
> ===
>
> The commit message in [PATCH v3 4/8] has to many "applications", so
> maybe restyle a bit?
>
> Add compatible string for rv1126 to applications for potential
> applications.
done.
>
> Adding "rockchip,rv1126-spi" to rockchip_spi_dt_match[] is strictly not
> needed when using "rockchip,rk3066-spi" as fall back string.
> Could a maintainer advice?
>
> Maybe this bug of mine should revert too?? Or is it legacy? ;)
> spi: rockchip: add compatible string for px30 rk3308 rk3328
> https://lore.kernel.org/r/20200309151004.7780-1-jbx6244@gmail.com
I agree with you. If the maintainer doesn't have any comments, I will use
"rockchip,spi" as compatible names for the subsequent rk platform.
>
> ===
>
> Johan
>
> On 6/5/21 11:46 AM, Jon Lin wrote:
>> The description below will be used for rv1126.dtsi in the future
>>
>> Signed-off-by: Jon Lin <jon.lin@rock-chips.com>
>> ---
>> Documentation/devicetree/bindings/spi/spi-rockchip.yaml | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/Documentation/devicetree/bindings/spi/spi-rockchip.yaml b/Documentation/devicetree/bindings/spi/spi-rockchip.yaml
>> index 1e6cf29e6388..4ed5b72a8494 100644
>> --- a/Documentation/devicetree/bindings/spi/spi-rockchip.yaml
>> +++ b/Documentation/devicetree/bindings/spi/spi-rockchip.yaml
>> @@ -27,6 +27,7 @@ properties:
>> - items:
>> - enum:
>> - rockchip,px30-spi
>> + - rockchip,rv1126-spi
> Sort alphabetically.
>
>> - rockchip,rk3188-spi
>> - rockchip,rk3288-spi
>> - rockchip,rk3308-spi
>>
>
>
next prev parent reply other threads:[~2021-06-07 6:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 9:46 [PATCH v3 1/8] spi: rockchip: Set rx_fifo interrupt waterline base on transfer item Jon Lin
2021-06-05 9:46 ` [PATCH v3 2/8] spi: rockchip: Wait for STB status in slave mode tx_xfer Jon Lin
2021-06-05 9:46 ` [PATCH v3 3/8] dt-bindings: spi: spi-rockchip: add description for rv1126 Jon Lin
2021-06-05 20:30 ` Johan Jonker
2021-06-07 6:36 ` Jon Lin [this message]
2021-06-05 9:46 ` [PATCH v3 4/8] spi: rockchip: add compatible string " Jon Lin
2021-06-05 9:46 ` [PATCH v3 5/8] spi: rockchip: Support cs-gpio Jon Lin
2021-06-05 9:48 ` [PATCH v3 6/8] dt-bindings: spi: spi-rockchip: add description for rk3568 Jon Lin
2021-06-05 9:48 ` [PATCH v3 7/8] spi: rockchip: Add compatible string " Jon Lin
2021-06-05 9:49 ` [PATCH v3 8/8] spi: rockchip: Support SPI_CS_HIGH Jon Lin
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=9d6c9b33-2e56-430b-0ea7-df0ebc0a16b4@rock-chips.com \
--to=jon.lin@rock-chips.com \
--cc=broonie@kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=kernel@esmil.dk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-spi@vger.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®