Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) client-ip=2620:137:e000::3:5;
Date:   Wed, 15 Nov 2023 16:07:07 +0100
From:   Paul Kocialkowski <paul.kocialkowski@bootlin.com>
To:     Conor Dooley <conor@kernel.org>
Cc:     Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
        Mehdi Djait <mehdi.djait@bootlin.com>, mchehab@kernel.org,
        heiko@sntech.de, hverkuil-cisco@xs4all.nl,
        krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
        conor+dt@kernel.org, linux-media@vger.kernel.org,
        devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
        thomas.petazzoni@bootlin.com, alexandre.belloni@bootlin.com,
        maxime.chevallier@bootlin.com, michael.riesch@wolfvision.net
Subject: Re: [PATCH v10 1/3] media: dt-bindings: media: add bindings for
 Rockchip CIF
Message-ID: <ZVTemwY6gvFdQMib@aptenodytes>
References: <cover.1699460637.git.mehdi.djait@bootlin.com>
 <037bcabf97294d37b271537e4b11fb88cf9bb6f6.1699460637.git.mehdi.djait@bootlin.com>
 <20231109-closable-superglue-5e7f39739cf1@spud>
 <ZU0avuRRaITV4jws@aptenodytes>
 <e5b1f0dd-0aab-4ce5-82ba-879a4d736e7e@linaro.org>
 <ZU0f33clFwlsTw16@aptenodytes>
 <20231110-appetizer-fame-2152806c7442@roley>
 <ZVJUsDb1mPVtcjdX@aptenodytes>
 <20231114-abnormal-uncross-dcebea2e82ae@squawk>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="RLyCz4Fbk+INaST5"
Content-Disposition: inline
In-Reply-To: <20231114-abnormal-uncross-dcebea2e82ae@squawk>
Precedence: bulk


--RLyCz4Fbk+INaST5
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Tue 14 Nov 23, 17:51, Conor Dooley wrote:
> On Mon, Nov 13, 2023 at 05:54:08PM +0100, Paul Kocialkowski wrote:
> =20
> > > Ultimately, I don't care what the file ends up being called when there
> > > are multiple devices documented in it. I'd ack a patch renaming to the
> > > =C5=93riginal incarnation of the IP when the documentation for that I=
P is
> > > added without a second thought.
> >=20
> > That would be agreeable to me if my proposal still ends up feeling unre=
asonable
> > to you. But I might very well take you at your word since I ended up pu=
rchasing
> > a RK3066 board in a moment of weakness last week.
>=20
> The ideal outcome I suppose would be documenting both variants. If
> you've gone ahead and bought one, give that a go.

Yeah I'll try to do that eventually, but we really want to have this series
merged as soon as possible. So it wouldn't be reasonable for us to wait for
RK3066 support.

What's your final decision for now: is it okay to keep the file named
rockchip,rk3066-cif.yaml (without this compatible in the file) or do you st=
ill
want it called rockchip,px30-vip.yaml?

Cheers,

Paul

--=20
Paul Kocialkowski, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com

--RLyCz4Fbk+INaST5
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEJZpWjZeIetVBefti3cLmz3+fv9EFAmVU3psACgkQ3cLmz3+f
v9HjEAf/SU3y3RdjGRSQQ5ldwayPyDN9QCNmqna23Z7SUj7Iy3DoWx9iAIHrXKuE
9PpvVh2nMXxoIjvjQMnmcIZgdqZoAJvDwFCrIR/a+tlwg68Gco5lPwAG00dm3vXV
kIBXjL7VLWjwV1v66SwxEvi4fXDNT6/3qbO5r83jAshhC/VsxFMyLrNSdNrIKwIJ
4w496dDQ9yv/Y0NwW2C05ibT+FAk2Av+7DxG4HzQkN1dMYLbSAn5t57Q+86FfqQf
h8Tjy6xuHtj8ja2sWFBQzyJmzqYFOzcnb28CyOmfDnz8jVmCy/kwk/WLyqK+kRqM
Bvk1pN6Xw6xFLAjrCcEq49bLqLZBNQ==
=jU15
-----END PGP SIGNATURE-----

--RLyCz4Fbk+INaST5--