From: Conor Dooley <conor@kernel.org>
To: William Qiu <william.qiu@starfivetech.com>
Cc: Emil Renner Berthing <emil.renner.berthing@canonical.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
linux-mmc@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jaehoon Chung <jh80.chung@samsung.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] StarFive's SDIO/eMMC driver support
Date: Wed, 15 Feb 2023 10:22:29 +0000 [thread overview]
Message-ID: <Y+yyZaBITDmEFUyB@spud> (raw)
In-Reply-To: <3ee9b726-10db-5d05-b24a-010c8bf5b59d@starfivetech.com>
[-- Attachment #1: Type: text/plain, Size: 3325 bytes --]
On Wed, Feb 15, 2023 at 06:16:35PM +0800, William Qiu wrote:
>
>
> On 2023/2/15 18:00, Emil Renner Berthing wrote:
> > On Tue, 14 Feb 2023 at 13:21, Ulf Hansson <ulf.hansson@linaro.org> wrote:
> >>
> >> On Fri, 3 Feb 2023 at 09:19, William Qiu <william.qiu@starfivetech.com> wrote:
> >> >
> >> > Hi,
> >> >
> >> > This patchset adds initial rudimentary support for the StarFive
> >> > designware mobile storage host controller driver. And this driver will
> >> > be used in StarFive's VisionFive 2 board. The main purpose of adding
> >> > this driver is to accommodate the ultra-high speed mode of eMMC.
> >> >
> >> > The last patch should be applied after the patchset [1]:
> >> > [1] https://lore.kernel.org/all/20221220011247.35560-1-hal.feng@starfivetech.com/
> >> >
> >> > Changes since v2:
> >> > - Wraped commit message according to Linux coding style.
> >> > - Rephrased the description of the patches.
> >> > - Changed the description of syscon regsiter.
> >> > - Dropped redundant properties.
> >> >
> >> > The patch series is based on v6.1.
> >> >
> >> > William Qiu (3):
> >> > dt-bindings: mmc: Add StarFive MMC module
> >> > mmc: starfive: Add sdio/emmc driver support
> >> > riscv: dts: starfive: Add mmc node
> >> >
> >> > .../bindings/mmc/starfive,jh7110-mmc.yaml | 77 ++++++++
> >> > MAINTAINERS | 6 +
> >> > .../jh7110-starfive-visionfive-2.dtsi | 23 +++
> >> > arch/riscv/boot/dts/starfive/jh7110.dtsi | 37 ++++
> >> > drivers/mmc/host/Kconfig | 10 +
> >> > drivers/mmc/host/Makefile | 1 +
> >> > drivers/mmc/host/dw_mmc-starfive.c | 185 ++++++++++++++++++
> >> > 7 files changed, 339 insertions(+)
> >> > create mode 100644 Documentation/devicetree/bindings/mmc/starfive,jh7110-mmc.yaml
> >> > create mode 100644 drivers/mmc/host/dw_mmc-starfive.c
> >> >
> >>
> >> Patch 1 and patch 2 applied for next, thanks!
> >>
> >> Note that I fixed some checkpatch errors/warnings. Next time, please
> >> run ./scripts/checkpatch.pl before you submit your patches.
> >
> > Hi,
> >
> > Something here is not right. The bindings document "starfive,sysreg",
> > but the code is looking for "starfive,syscon".
> > William, did you test this and run dtbs_check before sending this series?
> >
> > /Emil
>
> Hi Emil,
>
> Sorry about that, it's my negligence that I did dtbs_check without
dtbs_check would be okay though, no? The binding and dts (from checking
with eyeballs!) are consistent & it is just the driver that is looking
for the wrong property name, no?
> checking the configuration of CONFIG_SOC_STARFIVE. I made a modification
> in the next version and add binding for all the syscon at the same time. Next
> time I'll make sure the check is correct.I'm sorry again for this oversight.
> I'll send v4 patch series today.
Ulf's subsystem & his rules, but I would just send a follow-on patch
fixing the driver to use the property that is in the dt-binding.
Sorta unrelated, but please remind me about the dts patch once the base
dts is merged. It's still in the RISC-V patchwork so *should* be fine,
but in case the base dts takes a while it may get automatically
archived.
Thanks,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: William Qiu <william.qiu@starfivetech.com>
Cc: Emil Renner Berthing <emil.renner.berthing@canonical.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
linux-mmc@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jaehoon Chung <jh80.chung@samsung.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] StarFive's SDIO/eMMC driver support
Date: Wed, 15 Feb 2023 10:22:29 +0000 [thread overview]
Message-ID: <Y+yyZaBITDmEFUyB@spud> (raw)
In-Reply-To: <3ee9b726-10db-5d05-b24a-010c8bf5b59d@starfivetech.com>
[-- Attachment #1.1: Type: text/plain, Size: 3325 bytes --]
On Wed, Feb 15, 2023 at 06:16:35PM +0800, William Qiu wrote:
>
>
> On 2023/2/15 18:00, Emil Renner Berthing wrote:
> > On Tue, 14 Feb 2023 at 13:21, Ulf Hansson <ulf.hansson@linaro.org> wrote:
> >>
> >> On Fri, 3 Feb 2023 at 09:19, William Qiu <william.qiu@starfivetech.com> wrote:
> >> >
> >> > Hi,
> >> >
> >> > This patchset adds initial rudimentary support for the StarFive
> >> > designware mobile storage host controller driver. And this driver will
> >> > be used in StarFive's VisionFive 2 board. The main purpose of adding
> >> > this driver is to accommodate the ultra-high speed mode of eMMC.
> >> >
> >> > The last patch should be applied after the patchset [1]:
> >> > [1] https://lore.kernel.org/all/20221220011247.35560-1-hal.feng@starfivetech.com/
> >> >
> >> > Changes since v2:
> >> > - Wraped commit message according to Linux coding style.
> >> > - Rephrased the description of the patches.
> >> > - Changed the description of syscon regsiter.
> >> > - Dropped redundant properties.
> >> >
> >> > The patch series is based on v6.1.
> >> >
> >> > William Qiu (3):
> >> > dt-bindings: mmc: Add StarFive MMC module
> >> > mmc: starfive: Add sdio/emmc driver support
> >> > riscv: dts: starfive: Add mmc node
> >> >
> >> > .../bindings/mmc/starfive,jh7110-mmc.yaml | 77 ++++++++
> >> > MAINTAINERS | 6 +
> >> > .../jh7110-starfive-visionfive-2.dtsi | 23 +++
> >> > arch/riscv/boot/dts/starfive/jh7110.dtsi | 37 ++++
> >> > drivers/mmc/host/Kconfig | 10 +
> >> > drivers/mmc/host/Makefile | 1 +
> >> > drivers/mmc/host/dw_mmc-starfive.c | 185 ++++++++++++++++++
> >> > 7 files changed, 339 insertions(+)
> >> > create mode 100644 Documentation/devicetree/bindings/mmc/starfive,jh7110-mmc.yaml
> >> > create mode 100644 drivers/mmc/host/dw_mmc-starfive.c
> >> >
> >>
> >> Patch 1 and patch 2 applied for next, thanks!
> >>
> >> Note that I fixed some checkpatch errors/warnings. Next time, please
> >> run ./scripts/checkpatch.pl before you submit your patches.
> >
> > Hi,
> >
> > Something here is not right. The bindings document "starfive,sysreg",
> > but the code is looking for "starfive,syscon".
> > William, did you test this and run dtbs_check before sending this series?
> >
> > /Emil
>
> Hi Emil,
>
> Sorry about that, it's my negligence that I did dtbs_check without
dtbs_check would be okay though, no? The binding and dts (from checking
with eyeballs!) are consistent & it is just the driver that is looking
for the wrong property name, no?
> checking the configuration of CONFIG_SOC_STARFIVE. I made a modification
> in the next version and add binding for all the syscon at the same time. Next
> time I'll make sure the check is correct.I'm sorry again for this oversight.
> I'll send v4 patch series today.
Ulf's subsystem & his rules, but I would just send a follow-on patch
fixing the driver to use the property that is in the dt-binding.
Sorta unrelated, but please remind me about the dts patch once the base
dts is merged. It's still in the RISC-V patchwork so *should* be fine,
but in case the base dts takes a while it may get automatically
archived.
Thanks,
Conor.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-02-15 10:22 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 8:19 [PATCH v3 0/3] StarFive's SDIO/eMMC driver support William Qiu
2023-02-03 8:19 ` William Qiu
2023-02-03 8:19 ` [PATCH v3 1/3] dt-bindings: mmc: Add StarFive MMC module William Qiu
2023-02-03 8:19 ` William Qiu
2023-02-03 9:00 ` Krzysztof Kozlowski
2023-02-03 9:00 ` Krzysztof Kozlowski
2023-02-03 8:19 ` [PATCH v3 2/3] mmc: starfive: Add sdio/emmc driver support William Qiu
2023-02-03 8:19 ` William Qiu
2023-02-03 8:19 ` [PATCH v3 3/3] riscv: dts: starfive: Add mmc node William Qiu
2023-02-03 8:19 ` William Qiu
2023-02-03 9:02 ` Krzysztof Kozlowski
2023-02-03 9:02 ` Krzysztof Kozlowski
2023-02-03 9:23 ` William Qiu
2023-02-03 9:23 ` William Qiu
2023-02-03 9:30 ` Krzysztof Kozlowski
2023-02-03 9:30 ` Krzysztof Kozlowski
2023-02-03 9:35 ` William Qiu
2023-02-03 9:35 ` William Qiu
2023-02-15 10:31 ` Emil Renner Berthing
2023-02-15 10:31 ` Emil Renner Berthing
2023-02-15 10:32 ` William Qiu
2023-02-15 10:32 ` William Qiu
2023-02-14 12:18 ` [PATCH v3 0/3] StarFive's SDIO/eMMC driver support Ulf Hansson
2023-02-14 12:18 ` Ulf Hansson
2023-02-15 1:56 ` William Qiu
2023-02-15 1:56 ` William Qiu
2023-02-15 10:00 ` Emil Renner Berthing
2023-02-15 10:00 ` Emil Renner Berthing
2023-02-15 10:16 ` William Qiu
2023-02-15 10:16 ` William Qiu
2023-02-15 10:22 ` Conor Dooley [this message]
2023-02-15 10:22 ` Conor Dooley
2023-02-15 10:36 ` William Qiu
2023-02-15 10:36 ` William Qiu
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=Y+yyZaBITDmEFUyB@spud \
--to=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=emil.renner.berthing@canonical.com \
--cc=jh80.chung@samsung.com \
--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=robh+dt@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.