From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Jyan Chou [周芷安]" <jyanchou@realtek.com>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"jh80.chung@samsung.com" <jh80.chung@samsung.com>,
"riteshh@codeaurora.org" <riteshh@codeaurora.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>
Cc: "conor+dt@kernel.org" <conor+dt@kernel.org>,
"asutoshd@codeaurora.org" <asutoshd@codeaurora.org>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"briannorris@chromium.org" <briannorris@chromium.org>,
"doug@schmorgal.com" <doug@schmorgal.com>,
"tonyhuang.sunplus@gmail.com" <tonyhuang.sunplus@gmail.com>,
"abel.vesa@linaro.org" <abel.vesa@linaro.org>,
"william.qiu@starfivetech.com" <william.qiu@starfivetech.com>
Subject: Re: [PATCH v7][4/4] dt-bindings: mmc: Add dt-bindings for realtek mmc driver
Date: Wed, 22 Nov 2023 08:36:40 +0100 [thread overview]
Message-ID: <31927a2b-4b14-406b-8db0-511ec4779d4f@linaro.org> (raw)
In-Reply-To: <4551fbf03e3349eb8eaa336d505a5384@realtek.com>
On 22/11/2023 03:54, Jyan Chou [周芷安] wrote:
>> + clocks = <&cc 22>, <&cc 26>, <&cc 121>, <&cc 122>;
>> + clock-names = "biu", "ciu", "vp0", "vp1";
>
>> Where is the DTS implementing this binding?
>
>> I said it once:
>
>>> I asked you to test the bindings. This also means that you must test
>>> your DTS against bindings. Your bindings, DTS and driver do not match,
>>> therefore let's be a bit more clear:
>>>
>>> NAK, till you upstream your DTS.
>
>> I still do not see DTS anywhere. Please link it.
>
> Sorry for asking. Which dts do we need to link it? The device tree we use for our SOC?
>
> or realtek,rtd-dw-cqe-emmc.example.dts? Thanks.
The patch adding this device node to any upstream DTS. I am not speaking
about example, but about upstream DTS using this MMC.
As I wrote last time, I don't believe you test bindings and DTS and I
had proofs of that. Therefore I expect you to upstream DTS of your product.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-11-22 7:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 9:10 [PATCH V7][0/4] Add DesignWare Mobile mmc driver Jyan Chou
2023-11-21 9:10 ` [PATCH v7][1/4] mmc: solve DMA boundary limitation of CQHCI driver Jyan Chou
2023-11-21 9:10 ` [PATCH v7][2/4] mmc: Add Synopsys DesignWare mmc cmdq host driver Jyan Chou
2023-11-22 0:20 ` kernel test robot
2023-11-22 14:48 ` kernel test robot
2023-11-27 12:51 ` Philipp Zabel
2023-11-28 7:05 ` Jyan Chou [周芷安]
2023-11-28 10:53 ` Arnd Bergmann
2023-11-27 13:02 ` Christian Loehle
2023-11-28 6:58 ` Jyan Chou [周芷安]
2023-11-28 18:05 ` Adrian Hunter
2023-12-05 9:19 ` Jyan Chou [周芷安]
2023-12-05 11:26 ` Adrian Hunter
2023-12-11 10:37 ` Jyan Chou [周芷安]
2023-12-11 10:45 ` Adrian Hunter
2023-11-21 9:11 ` [PATCH v7][3/4] mmc: Add dw mobile mmc cmdq rtk driver Jyan Chou
2023-11-21 9:11 ` [PATCH v7][4/4] dt-bindings: mmc: Add dt-bindings for realtek mmc driver Jyan Chou
2023-11-21 9:35 ` Krzysztof Kozlowski
2023-11-22 2:54 ` Jyan Chou [周芷安]
2023-11-22 7:36 ` Krzysztof Kozlowski [this message]
2023-11-22 8:33 ` Jyan Chou [周芷安]
2023-11-22 8:45 ` Krzysztof Kozlowski
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=31927a2b-4b14-406b-8db0-511ec4779d4f@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=abel.vesa@linaro.org \
--cc=adrian.hunter@intel.com \
--cc=arnd@arndb.de \
--cc=asutoshd@codeaurora.org \
--cc=briannorris@chromium.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=doug@schmorgal.com \
--cc=jh80.chung@samsung.com \
--cc=jyanchou@realtek.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=riteshh@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=tonyhuang.sunplus@gmail.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).