From: Rob Herring <robh@kernel.org>
To: nina_kuo@novatek.com.tw
Cc: andi.shyti@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, ben_huang@novatek.com.tw,
toby_chui@novatek.com.tw, shihpei_hsu@novatek.com.tw
Subject: Re: [PATCH v8 1/3] dt-bindings: i2c: Add Novatek NT72676 I2C controller
Date: Thu, 3 Sep 2026 11:04:34 -0500 [thread overview]
Message-ID: <20260903160434.GA3629759-robh@kernel.org> (raw)
In-Reply-To: <20260902091318.208074-2-nina_kuo@novatek.com.tw>
On Wed, Sep 02, 2026 at 05:13:16PM +0800, nina_kuo@novatek.com.tw wrote:
> From: Ben Huang <Ben_Huang@novatek.com.tw>
>
> Add Devicetree binding documentation for Novatek NT72676 I2C
> controller.
>
> Signed-off-by: Ben Huang <Ben_Huang@novatek.com.tw>
> Signed-off-by: Nina Kuo <Nina_Kuo@novatek.com.tw>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> ---
> .../bindings/i2c/novatek,nt72676-i2c.yaml | 90 +++++++++++++++++++
> 1 file changed, 90 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/i2c/novatek,nt72676-i2c.yaml
>
> diff --git a/Documentation/devicetree/bindings/i2c/novatek,nt72676-i2c.yaml b/Documentation/devicetree/bindings/i2c/novatek,nt72676-i2c.yaml
> new file mode 100644
> index 000000000000..c9dd1c0d7957
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/i2c/novatek,nt72676-i2c.yaml
> @@ -0,0 +1,90 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/i2c/novatek,nt72676-i2c.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Novatek NT72676 I2C Controller
> +
> +maintainers:
> + - Ben Huang <ben_huang@novatek.com.tw>
> + - Jason JJ Wu <jason_jj_wu@novatek.com.tw>
> +
> +description:
> + Novatek NT72676 SoC provides two I2C controller variants, generic I2C and
> + STBC I2C.
blank line between paragraphs and you need a '>' modifier on
'description'.
> + The generic I2C controllers are accessible only by the host CPU and driven
> + by a 96 MHz AHB clock.
> + On the other hand, the STBC I2C controllers can be controlled by either the
> + host CPU or STBC (Standby Controller, an 8051-based microcontroller) and
> + driven by a 12 MHz STBC clock. Authentication with STBC is required before
> + the host CPU can access the STBC I2C controller registers.
Is the programming model of the I2C controller different? If not, the
compatible should be the same.
> +
> +properties:
> + compatible:
> + enum:
> + - novatek,nt72676-i2c
> + - novatek,nt72676-stbc-i2c
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + clock-frequency:
> + default: 100000
> + enum: [ 100000, 400000 ]
> +
> + novatek,stbc-syscon:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description:
> + Phandle to the STBC system controller registers used to authenticate
> + host access and switch ownership of the STBC I2C controller.
Sounds like this could be modelled as a hwlock? That's other platforms
mediate access to shared h/w. We really only want to have these syscon
phandles as a last resort.
Rob
next prev parent reply other threads:[~2026-09-03 16:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 9:13 [PATCH v8 0/3] i2c: Add Novatek NT72676 SoC I2C controller nina_kuo
2026-09-02 9:13 ` [PATCH v8 1/3] dt-bindings: i2c: Add Novatek NT72676 " nina_kuo
2026-09-03 16:04 ` Rob Herring [this message]
2026-09-04 5:40 ` nina_kuo
2026-09-04 23:42 ` Rob Herring
2026-09-07 5:02 ` nina_kuo
2026-09-02 9:13 ` [PATCH v8 2/3] i2c: nt72676: Add Novatek NT72676 I2C controller driver nina_kuo
2026-09-02 9:29 ` sashiko-bot
2026-09-02 9:13 ` [PATCH v8 3/3] MAINTAINERS: Add entry for " nina_kuo
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=20260903160434.GA3629759-robh@kernel.org \
--to=robh@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=ben_huang@novatek.com.tw \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nina_kuo@novatek.com.tw \
--cc=shihpei_hsu@novatek.com.tw \
--cc=toby_chui@novatek.com.tw \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.