public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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
Date: Wed, 15 Nov 2023 16:07:07 +0100	[thread overview]
Message-ID: <ZVTemwY6gvFdQMib@aptenodytes> (raw)
In-Reply-To: <20231114-abnormal-uncross-dcebea2e82ae@squawk>

[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]

Hi,

On Tue 14 Nov 23, 17:51, Conor Dooley wrote:
> On Mon, Nov 13, 2023 at 05:54:08PM +0100, Paul Kocialkowski wrote:
>  
> > > 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
> > > œriginal incarnation of the IP when the documentation for that IP is
> > > added without a second thought.
> > 
> > That would be agreeable to me if my proposal still ends up feeling unreasonable
> > to you. But I might very well take you at your word since I ended up purchasing
> > a RK3066 board in a moment of weakness last week.
> 
> 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 still
want it called rockchip,px30-vip.yaml?

Cheers,

Paul

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-11-15 15:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08 16:38 [PATCH v10 0/3] media: rockchip: Add a driver for Rockchip's camera interface Mehdi Djait
2023-11-08 16:38 ` [PATCH v10 1/3] media: dt-bindings: media: add bindings for Rockchip CIF Mehdi Djait
2023-11-09 17:24   ` Conor Dooley
2023-11-09 17:45     ` Paul Kocialkowski
2023-11-09 17:53       ` Krzysztof Kozlowski
2023-11-09 18:07         ` Paul Kocialkowski
2023-11-10 18:23           ` Conor Dooley
2023-11-13 16:54             ` Paul Kocialkowski
2023-11-14 17:51               ` Conor Dooley
2023-11-15 15:07                 ` Paul Kocialkowski [this message]
2023-11-15 20:16                   ` Conor Dooley
2023-11-08 16:38 ` [PATCH v10 2/3] media: rockchip: Add a driver for Rockchip's camera interface Mehdi Djait
2023-11-10 12:50   ` Michael Riesch
2023-11-13 11:06     ` Mehdi Djait
2023-11-13 15:41       ` Michael Riesch
2023-11-10 14:33   ` Michael Riesch
2023-11-13 15:28     ` Mehdi Djait
2023-11-13 16:05       ` Michael Riesch
2023-11-15  9:16         ` Mehdi Djait
2023-11-08 16:38 ` [PATCH v10 3/3] arm64: dts: rockchip: Add the " Mehdi Djait

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=ZVTemwY6gvFdQMib@aptenodytes \
    --to=paul.kocialkowski@bootlin.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=maxime.chevallier@bootlin.com \
    --cc=mchehab@kernel.org \
    --cc=mehdi.djait@bootlin.com \
    --cc=michael.riesch@wolfvision.net \
    --cc=robh+dt@kernel.org \
    --cc=thomas.petazzoni@bootlin.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