From: "Rob Herring (Arm)" <robh@kernel.org>
To: Olivier Benjamin <olivier.benjamin@bootlin.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org,
Nicholas Roth <nicholas@rothemail.net>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
imx@lists.linux.dev, linux-rockchip@lists.infradead.org,
Shawn Guo <shawnguo@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Ondrej Jirman <megi@xff.cz>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Fabio Estevam <festevam@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Sascha Hauer <s.hauer@pengutronix.de>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
Dragan Simic <dsimic@manjaro.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH v3 0/4] Describe the cameras in the PinePhone Pro dts
Date: Mon, 12 May 2025 07:49:33 -0500 [thread overview]
Message-ID: <174705404383.2941320.1978376350297662131.robh@kernel.org> (raw)
In-Reply-To: <20250509-camera-v3-0-dab2772d229a@bootlin.com>
On Fri, 09 May 2025 23:51:36 +0200, Olivier Benjamin wrote:
> This series adds support for the Pine64 PinePhone Pro's rear and front
> cameras in Device Tree.
> This is based on some of Ondrej Jirman's patches hosted in his tree at
> https://codeberg.org/megi/linux, but I have also fully reviewed and
> re-written the code from the RK3399 datasheet, the PinePhone Pro
> schematic, and the IMX258-0AQH5 software reference manual.
>
> I have tested these changes on my PinePhone Pro and am able to take
> photos from both cameras using libcamera's cam.
>
> Signed-off-by: Olivier Benjamin <olivier.benjamin@bootlin.com>
> ---
> Changes in v3:
> - Fixed new DTB warnings reported by Rob Herring's bot
> - Link to v2: https://lore.kernel.org/r/20250302-camera-v2-0-312b44b4a89c@bootlin.com
>
> Changes in v2:
> - Rebase on mainline
> - Change patch subject to arm64: dts: rockchip
> - Rename new regulators to fit preferred form for fixed regulators
> - Link to v1: https://lore.kernel.org/r/20250228-camera-v1-0-c51869f94e97@bootlin.com
>
> ---
> Olivier Benjamin (4):
> dt-bindings: media: ov8858: inherit video-interface-devices properties
> dt-bindings: media: imx258: inherit video-interface-devices properties
> arm64: dts: rockchip: describe I2c Bus 1 and IMX258 world camera on PinePhone Pro
> arm64: dts: rockchip: describe the OV8858 user camera on PinePhone Pro
>
> .../devicetree/bindings/media/i2c/ovti,ov8858.yaml | 4 +-
> .../devicetree/bindings/media/i2c/sony,imx258.yaml | 4 +-
> .../boot/dts/rockchip/rk3399-pinephone-pro.dts | 139 +++++++++++++++++++++
> 3 files changed, 145 insertions(+), 2 deletions(-)
> ---
> --
> Olivier Benjamin <olivier.benjamin@bootlin.com>
>
>
>
My bot found new DTB warnings on the .dts files added or changed in this
series.
Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.
If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:
pip3 install dtschema --upgrade
This patch series was applied (using b4) to base:
Base: attempting to guess base-commit...
Base: tags/v6.15-rc1-102-g2332d042e9b2 (exact match)
If this is not the correct base, please add 'base-commit' tag
(or use b4 which does this automatically)
New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/rockchip/' for 20250509-camera-v3-0-dab2772d229a@bootlin.com:
arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dtb: camera@1a (sony,imx258): Unevaluated properties are not allowed ('clock-names' was unexpected)
from schema $id: http://devicetree.org/schemas/media/i2c/sony,imx258.yaml#
prev parent reply other threads:[~2025-05-12 12:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 21:51 [PATCH v3 0/4] Describe the cameras in the PinePhone Pro dts Olivier Benjamin
2025-05-09 21:51 ` [PATCH v3 1/4] dt-bindings: media: ov8858: inherit video-interface-devices properties Olivier Benjamin
2025-05-14 20:12 ` Rob Herring (Arm)
2025-05-09 21:51 ` [PATCH v3 2/4] dt-bindings: media: imx258: " Olivier Benjamin
2025-05-14 20:12 ` Rob Herring (Arm)
2025-05-09 21:51 ` [PATCH v3 3/4] arm64: dts: rockchip: describe I2c Bus 1 and IMX258 world camera on PinePhone Pro Olivier Benjamin
2025-05-13 18:23 ` Heiko Stuebner
2025-05-14 4:59 ` Olivier Benjamin
2025-05-29 16:17 ` Olivier Benjamin
2025-05-09 21:51 ` [PATCH v3 4/4] arm64: dts: rockchip: describe the OV8858 user " Olivier Benjamin
2025-05-12 12:49 ` Rob Herring (Arm) [this message]
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=174705404383.2941320.1978376350297662131.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=festevam@gmail.com \
--cc=heiko@sntech.de \
--cc=imx@lists.linux.dev \
--cc=jacopo.mondi@ideasonboard.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=megi@xff.cz \
--cc=nicholas@rothemail.net \
--cc=olivier.benjamin@bootlin.com \
--cc=s.hauer@pengutronix.de \
--cc=sakari.ailus@linux.intel.com \
--cc=shawnguo@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