Message ID | 20230203081913.81968-1-william.qiu@starfivetech.com |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:adf:eb09:0:0:0:0:0 with SMTP id s9csp710926wrn; Fri, 3 Feb 2023 00:22:30 -0800 (PST) X-Google-Smtp-Source: AK7set+YoUK4bajfBN+5Tit1hDK2FpuE1DD/Re4pD4C2iad/4ih0Q4yM3rJK4HJ586kJ3EBjKz8b X-Received: by 2002:aa7:d792:0:b0:48f:fcc9:665e with SMTP id s18-20020aa7d792000000b0048ffcc9665emr3690027edq.0.1675412550009; Fri, 03 Feb 2023 00:22:30 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1675412549; cv=none; d=google.com; s=arc-20160816; b=Sw4MQRAh76f65dUtb80FtZW4wIBXK9bGcMbhwk0VIgiBVAfSWyQyHsgfA+LJfAxbjP bMQvhaXB/heUbEz3KPqTrh3RJzhLsiC8ZOlwkOhxFFcND8j/y371QFLpRc4bO1Pcqfyi VOhacxdOqgLhwJWUn5/fSetUEoLJi2FeD3cugk9ADOLGaGRsypQRmGks0HtwFOz/TU1T +Lj5I9R5m8YWCLLPJpBGNpXY1pHJGi8IqctPYCWIzA0MBYpWUsZVFA+3+8O8V4SLcSZQ e4vrYOlqGYJpl2KOScaqPPTnUCoB4vtnfAtCOKAHsU/dbDsvKNOg2rewtWP4vs+PmdqZ XXDQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from; bh=qLZEtDBZtLXAA1H17NmZgUp4XwAMFJY/qfwWSTXl5x8=; b=M/nRWJQF6iLtXLNuZwnN4iuNtf8jMCr8XxkYip8DYGtBfbqgQYhctLynKGKNbdTDYW jkkpAf5wlAbPNpNVIBy6tYuD5eheSu9/lhExVd+DZxOcNrYLg8K/GZSxnC0pi6b5puFI 6W6p8Chwgdw9RUZ2eWRuk14WqDnKRubj4WGA7U1ARt2J9S06iGcoItPKhHUvF62JHuy+ x9WCaILtxadmbeZhk4jPIKDY0AkanmNva6n3l/w0MTUV1wBmUXE/SMuBBNXFeedH/p8n ChxpGK5ghfPUIhUGhVMCQvJsyTidX2kVYeS0rx2OjnErAVav/Bc/HQD5jZCBOrQsiqSY GrSw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id d12-20020aa7d5cc000000b004a222dd2973si1862607eds.158.2023.02.03.00.22.06; Fri, 03 Feb 2023 00:22:29 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232678AbjBCIVa convert rfc822-to-8bit (ORCPT <rfc822;il.mystafa@gmail.com> + 99 others); Fri, 3 Feb 2023 03:21:30 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56424 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232999AbjBCIVI (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Fri, 3 Feb 2023 03:21:08 -0500 Received: from fd01.gateway.ufhost.com (fd01.gateway.ufhost.com [61.152.239.71]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7A96D6A73B; Fri, 3 Feb 2023 00:19:37 -0800 (PST) Received: from EXMBX166.cuchost.com (unknown [175.102.18.54]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "EXMBX166", Issuer "EXMBX166" (not verified)) by fd01.gateway.ufhost.com (Postfix) with ESMTP id F0C7224E1D1; Fri, 3 Feb 2023 16:19:14 +0800 (CST) Received: from EXMBX168.cuchost.com (172.16.6.78) by EXMBX166.cuchost.com (172.16.6.76) with Microsoft SMTP Server (TLS) id 15.0.1497.42; Fri, 3 Feb 2023 16:19:15 +0800 Received: from williamqiu-virtual-machine.starfivetech.com (171.223.208.138) by EXMBX168.cuchost.com (172.16.6.78) with Microsoft SMTP Server (TLS) id 15.0.1497.42; Fri, 3 Feb 2023 16:19:13 +0800 From: William Qiu <william.qiu@starfivetech.com> To: <linux-riscv@lists.infradead.org>, <devicetree@vger.kernel.org>, <linux-mmc@vger.kernel.org> CC: Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Jaehoon Chung <jh80.chung@samsung.com>, Ulf Hansson <ulf.hansson@linaro.org>, William Qiu <william.qiu@starfivetech.com>, <linux-kernel@vger.kernel.org> Subject: [PATCH v3 0/3] StarFive's SDIO/eMMC driver support Date: Fri, 3 Feb 2023 16:19:10 +0800 Message-ID: <20230203081913.81968-1-william.qiu@starfivetech.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [171.223.208.138] X-ClientProxiedBy: EXCAS064.cuchost.com (172.16.6.24) To EXMBX168.cuchost.com (172.16.6.78) X-YovoleRuleAgent: yovoleflag Content-Transfer-Encoding: 8BIT X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_MSPIKE_H2, SPF_HELO_PASS,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1756797389843541058?= X-GMAIL-MSGID: =?utf-8?q?1756797389843541058?= |
Series |
StarFive's SDIO/eMMC driver support
|
|
Message
William Qiu
Feb. 3, 2023, 8:19 a.m. UTC
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 -- 2.34.1
Comments
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. Kind regards Uffe
On 2023/2/14 20:18, Ulf Hansson 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. > > Kind regards > Uffe z Hi Uffe, Sorry about that, I'll check the patches before submit next time. Thanks for taking time reviewing this patch series. Best Regards William
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 > Kind regards > Uffe > > _______________________________________________ > linux-riscv mailing list > linux-riscv@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-riscv
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 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. Best Regards William > >> Kind regards >> Uffe >> >> _______________________________________________ >> linux-riscv mailing list >> linux-riscv@lists.infradead.org >> http://lists.infradead.org/mailman/listinfo/linux-riscv
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.
On 2023/2/15 18:22, Conor Dooley wrote: > 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? > It was my negligence that I didn't test the function >> 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. > I'll do it then. Thanks, William