Received-SPF: pass (google.com: domain of linux-kernel+bounces-122461-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Date: Thu, 28 Mar 2024 06:28:32 +0000
From: Conor Dooley <conor@kernel.org>
To: Changhuang Liang <changhuang.liang@starfivetech.com>
CC: Conor Dooley <conor.dooley@microchip.com>,
 Mauro Carvalho Chehab <mchehab@kernel.org>, Rob Herring <robh+dt@kernel.org>,
 Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
 Conor Dooley <conor+dt@kernel.org>, Emil Renner Berthing <kernel@esmil.dk>,
 Paul Walmsley <paul.walmsley@sifive.com>,
 Palmer Dabbelt <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu>,
 Jack Zhu <jack.zhu@starfivetech.com>,
 "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
 "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
 "linux-riscv@lists.infradead.org" <linux-riscv@lists.infradead.org>,
 "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: =?UTF-8?Q?Re=3A_=E5=9B=9E=E5=A4=8D=3A_=E5=9B=9E=E5=A4=8D=3A_?=
 =?UTF-8?Q?=E5=9B=9E=E5=A4=8D=3A_=5BPATCH_v?=
 =?UTF-8?Q?1_1/2=5D_dt-bindings=3A_medi?=
 =?UTF-8?Q?a=3A_starfive=3A_Match_driver_and_yaml_property_names?=
User-Agent: K-9 Mail for Android
In-Reply-To: <SHXPR01MB0671EA5AED87CE14113148E7F23BA@SHXPR01MB0671.CHNPR01.prod.partner.outlook.cn>
References: <20240119100639.84029-1-changhuang.liang@starfivetech.com> <20240119100639.84029-2-changhuang.liang@starfivetech.com> <20240119-despair-festival-59ab2d4d896b@wendy> <SHXPR01MB0671E2150D9A2707F12E0901F270A@SHXPR01MB0671.CHNPR01.prod.partner.outlook.cn> <20240119-preamble-calm-7724e17fcebc@wendy> <BJXPR01MB0662E6EEEEF888BD90A1FCE5F275A@BJXPR01MB0662.CHNPR01.prod.partner.outlook.cn> <20240122-uncivil-almost-631137081fd9@spud> <20240327-unlucky-bulge-2bf99a8649be@spud> <SHXPR01MB0671EA5AED87CE14113148E7F23BA@SHXPR01MB0671.CHNPR01.prod.partner.outlook.cn>
Message-ID: <C3D2F0B5-CB35-488E-842E-D049CA067475@kernel.org>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable


On 28 March 2024 01:06:42 GMT, Changhuang Liang <changhuang=2Eliang@starfi=
vetech=2Ecom> wrote:
>Hi, Conor,
>
>> On Mon, Jan 22, 2024 at 08:24:51AM +0000, Conor Dooley wrote:
>[=2E=2E=2E]
>> > > > > > Do these clocks etc exist but are not used by the driver?
>> > > > > >
>> > > > > > Or do they not exist at all?
>> > > > > >
>> > > > > > The two are very different!
>> > > >
>> > > > > These clocks etc exist but are not used by the driver=2E
>> > > >
>> > > > That's not an acceptable reason for removing them from the
>> > > > binding=2E If they exist, they should be documented, regardless o=
f
>> > > > whether the driver makes use of them=2E NAK=2E
>> > >
>> > > If so, how to avoid the warning of dtbs_check=2E
>> >
>> > By also adding the clocks, resets and interrupts to the dts=2E
>>=20
>> Going through patchwork stuff now that the merge window is done=2E I'm =
gonna
>> mark the dts patch as changes requeted=2E The binding (and dts) should
>> describe all of the clocks the hardware has, whether or not you choose =
to use
>> them all in software does not matter=2E Can you please resend the dts p=
atch,
>> with all of the clocks, resets and interrupts present?
>>=20
>
>You have applied the dts patch=2E
>https://lore=2Ekernel=2Eorg/all/20240219032741=2E18387-1-changhuang=2Elia=
ng@starfivetech=2Ecom/

Oh, sorry for the noise then=2E I guess I was
mislead by patchwork marking this as new :)