From: Rob Herring <robh@kernel.org>
To: Mathis Foerst <mathis.foerst@mt.com>
Cc: linux-kernel@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
manuel.traut@mt.com, mathis.foerst@zuehlke.com
Subject: Re: [PATCH v3 1/6] media: dt-bindings: mt9m114: Add onnn,slew-rate DT-binding
Date: Wed, 5 Mar 2025 07:08:21 -0600 [thread overview]
Message-ID: <20250305130821.GA1374586-robh@kernel.org> (raw)
In-Reply-To: <20250305101453.708270-2-mathis.foerst@mt.com>
On Wed, Mar 05, 2025 at 11:14:48AM +0100, Mathis Foerst wrote:
> The MT9M114 supports the different slew rates (0 to 7) on the output pads.
> At the moment, this is hardcoded to 7 (the fastest rate).
> The user might want to change this values due to EMC requirements.
>
> Add the 'onnn,slew-rate' property to the MT9M114 DT-bindings for selecting
> the desired slew rate.
>
> Signed-off-by: Mathis Foerst <mathis.foerst@mt.com>
> ---
> .../devicetree/bindings/media/i2c/onnn,mt9m114.yaml | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/media/i2c/onnn,mt9m114.yaml b/Documentation/devicetree/bindings/media/i2c/onnn,mt9m114.yaml
> index f6b87892068a..c184bc04b743 100644
> --- a/Documentation/devicetree/bindings/media/i2c/onnn,mt9m114.yaml
> +++ b/Documentation/devicetree/bindings/media/i2c/onnn,mt9m114.yaml
> @@ -70,6 +70,15 @@ properties:
> - bus-type
> - link-frequencies
>
> + onnn,slew-rate:
Just 'slew-rate' which is already defined in the pinctrl binding.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description:
> + Slew rate ot the output pads DOUT[7:0], LINE_VALID, FRAME_VALID and
> + PIXCLK. Higher values imply steeper voltage-flanks on the pads.
> + minimum: 0
> + maximum: 7
> + default: 7
> +
> required:
> - compatible
> - reg
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-03-05 13:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 10:14 [PATCH v3 0/6] MT9M114 driver bugfix and improvements Mathis Foerst
2025-03-05 10:14 ` [PATCH v3 1/6] media: dt-bindings: mt9m114: Add onnn,slew-rate DT-binding Mathis Foerst
2025-03-05 13:08 ` Rob Herring [this message]
2025-03-07 9:41 ` Mathis Foerst
2025-03-05 10:14 ` [PATCH v3 2/6] media: mt9m114: Bypass PLL if required Mathis Foerst
2025-03-05 10:14 ` [PATCH v3 3/6] media: mt9m114: Factor out mt9m114_configure_pa Mathis Foerst
2025-03-05 10:14 ` [PATCH v3 4/6] media: mt9m114: Allow set_selection while streaming Mathis Foerst
2025-03-05 10:14 ` [PATCH v3 5/6] media: mt9m114: Fix deadlock in get_frame_interval/set_frame_interval Mathis Foerst
2025-03-05 10:14 ` [PATCH v3 6/6] media: mt9m114: Set pad-slew-rate Mathis Foerst
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=20250305130821.GA1374586-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=manuel.traut@mt.com \
--cc=mathis.foerst@mt.com \
--cc=mathis.foerst@zuehlke.com \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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