Hi Krzysztof, On Thu, Oct 12, 2023 at 09:47:31AM +0200, Krzysztof Kozlowski wrote: > On 12/10/2023 03:20, Laurent Pinchart wrote: > > From: Paul Elder <paul.elder@xxxxxxxxxxxxxxxx> > > > > The THP7312 is an external ISP from THine. Add DT bindings for it. > > > > Signed-off-by: Paul Elder <paul.elder@xxxxxxxxxxxxxxxx> > > Co-developed-by: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx> > > Signed-off-by: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx> > > --- > > .../bindings/media/i2c/thine,thp7312.yaml | 225 ++++++++++++++++++ > > MAINTAINERS | 7 + > > 2 files changed, 232 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/media/i2c/thine,thp7312.yaml > > > > diff --git a/Documentation/devicetree/bindings/media/i2c/thine,thp7312.yaml b/Documentation/devicetree/bindings/media/i2c/thine,thp7312.yaml > > new file mode 100644 > > index 000000000000..053b28fb0a89 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/media/i2c/thine,thp7312.yaml > > @@ -0,0 +1,225 @@ > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > > +# Copyright (c) 2023 Ideas on Board > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/media/i2c/thine,thp7312.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: THine THP7312 > > + > > +maintainers: > > + - Paul Elder <paul.elder@@ideasonboard.com> > > + > > +description: > > + The THP7312 is a standalone ISP controlled over i2c, and is capable of > > + various image processing and correction functions, including 3A control. It > > + can be connected to CMOS image sensors from various vendors, supporting both > > + MIPI CSI-2 and parallel interfaces. It can also output on either MIPI CSI-2 > > + or parallel. The hardware is capable of transmitting and receiving MIPI > > + interlaved data strams with data types or multiple virtual channel > > + identifiers. > > + > > +allOf: > > + - $ref: ../video-interface-devices.yaml# > > + > > +properties: > > + compatible: > > + const: thine,thp7312 > > + > > + reg: > > + maxItems: 1 > > + description: I2C device address > > Nothing improved here. I'll drop the description. > > + > > + clocks: > > + maxItems: 1 > > + description: CLKI clock input > > + > > + thine,boot-mode: > > + $ref: /schemas/types.yaml#/definitions/uint32 > > + description: > > + Boot mode of the THP7312. 0 is for standard streaming mode, for the > > + THP7312 to be used as an ISP. 1 is for firmware flashing mode. > > Why, for a given board, would you always boot device in one specific > mode but not the other? This does not look like property of DT. The device has two boot mode pins, and it operates differently depending on its boot mode. The pins are typically hardwired, on development boards you commonly have DIP switches, and on production systems test pads that allow modifying the boot mode on the production line. The driver needs to know the boot mode to interact with the device appropriately. I haven't found a good way to interogate the device at runtime to figure out the boot mode, but I'm still trying. If that doesn't succeed, we need to convey it through the device tree. > > + > > + reset-gpios: > > + maxItems: 1 > > + description: > > + Reference to the GPIO connected to the RESET_N pin, if any. > > + Must be released (set high) after all supplies are applied. > > + > > + vddcore-supply: > > + description: > > + 1.2V supply for core, PLL, MIPI rx and MIPI tx. > > + > > + vhtermrx-supply: > > + description: > > + Supply for input (RX). 1.8V for MIPI, or 1.8/2.8/3.3V for parallel. > > + > > + vddtx-supply: > > + description: > > + Supply for output (TX). 1.8V for MIPI, or 1.8/2.8/3.3V for parallel. > > + > > + vddhost-supply: > > + description: > > + Supply for host interface. 1.8V, 2.8V, or 3.3V. > > + > > + vddcmos-supply: > > + description: > > + Supply for sensor interface. 1.8V, 2.8V, or 3.3V. > > + > > + vddgpio_0-supply: > > And more of ignored feedback. I stop now. > > This is a friendly reminder during the review process. > > It seems my previous comments were not fully addressed. Maybe my > feedback got lost between the quotes, maybe you just forgot to apply it. > Please go back to the previous discussion and either implement all > requested changes or keep discussing them. I took over the patch series and may have missed some comments. I'll double check and make sure to address all feedback (or raise questions in replies) for v3. It would be helpful if you could complete the review, or there will then be a v4 to address the second half of the DT bindings review :-S Your time and efforts are appreciated, I'm sorry for the human error here. -- Regards, Laurent Pinchart
