From: Rob Herring <robh@kernel.org>
To: William Qiu <william.qiu@starfivetech.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-mmc@vger.kernel.org,
Emil Renner Berthing <kernel@esmil.dk>,
Jaehoon Chung <jh80.chung@samsung.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>
Subject: Re: [PATCH v2 0/3] Change tuning implementation
Date: Tue, 12 Sep 2023 12:55:47 -0500 [thread overview]
Message-ID: <20230912175547.GA993874-robh@kernel.org> (raw)
In-Reply-To: <20230912081402.51477-4-william.qiu@starfivetech.com>
On Tue, Sep 12, 2023 at 04:13:59PM +0800, William Qiu wrote:
> Hi,
>
> This series of patches changes the tuning implementation, from the
> previous way of reading and writing system controller registers to
> reading and writing UHS_REG_EXT register, thus optimizing the tuning
> of obtaining delay-chain.
>
> Changes v1->v2:
Please don't send new versions as a reply to the prior version.
> - Rebased to v6.6rc1.
> - Keeped "starfive,sysreg" in dt-bindings but removed from required.
> - Changed the function interface name.
> - Maked the code implementation more concise.
>
> The patch series is based on v6.6rc1.
>
> William Qiu (3):
> dt-bindings: mmc: Remove properties from required
> mmc: starfive: Change tuning implementation
> riscv: dts: starfive: Drop unused properties and limit frquency
>
> .../bindings/mmc/starfive,jh7110-mmc.yaml | 2 -
> .../jh7110-starfive-visionfive-2.dtsi | 4 +
> arch/riscv/boot/dts/starfive/jh7110.dtsi | 2 -
> drivers/mmc/host/dw_mmc-starfive.c | 137 +++++-------------
> 4 files changed, 44 insertions(+), 101 deletions(-)
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-09-12 17:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 8:13 [PATCH 1/3] dt-bindings: mmc: Remove properties from required William Qiu
2023-09-12 8:13 ` [PATCH 2/3] mmc: starfive: Change tuning implementation William Qiu
2023-09-12 8:13 ` [PATCH 3/3] riscv: dts: starfive: Drop unused properties and limit frquency William Qiu
2023-09-12 8:13 ` [PATCH v2 0/3] Change tuning implementation William Qiu
2023-09-12 17:55 ` Rob Herring [this message]
2023-09-12 8:14 ` [PATCH v2 1/3] dt-bindings: mmc: Remove properties from required William Qiu
2023-09-12 16:39 ` Conor Dooley
2023-09-12 8:14 ` [PATCH v2 2/3] mmc: starfive: Change tuning implementation William Qiu
2023-09-12 13:20 ` Emil Renner Berthing
2023-09-12 8:14 ` [PATCH v2 3/3] riscv: dts: starfive: Drop unused properties and limit frquency William Qiu
2023-09-12 13:23 ` Emil Renner Berthing
2023-09-13 10:50 ` William Qiu
2023-09-12 9:12 ` [PATCH 1/3] dt-bindings: mmc: Remove properties from required Emil Renner Berthing
2023-09-12 16:40 ` Conor Dooley
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=20230912175547.GA993874-robh@kernel.org \
--to=robh@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jh80.chung@samsung.com \
--cc=kernel@esmil.dk \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=ulf.hansson@linaro.org \
--cc=william.qiu@starfivetech.com \
/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;
as well as URLs for NNTP newsgroup(s).