mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: David Heidelberg <david@ixit.cz>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sdm845-oneplus: Enable known blocks and add placeholders
Date: Wed, 17 Dec 2025 16:28:04 +0100	[thread overview]
Message-ID: <5f1282b2-2447-4ce8-a943-90c88e7f5835@oss.qualcomm.com> (raw)
In-Reply-To: <5199fe6a-550a-4366-bee2-d4ab08ed248b@ixit.cz>

On 12/17/25 4:00 PM, David Heidelberg wrote:
> On 17/12/2025 13:04, Konrad Dybcio wrote:
>> On 12/16/25 9:34 PM, David Heidelberg via B4 Relay wrote:
>>> From: David Heidelberg <david@ixit.cz>
>>>
>>> We know these devices are present; most of them are supported by
>>> downstream and are close to the mainline kernels.
>>>
>>> This adds placeholders for:
>>>   - front camera (imx371)
>>>   - rear cameras (imx519, imx376k)
>>>   - actuators
>>>   - NFC node on i2c3
>>>
>>> This is very handy when rebasing the integration tree with
>>> support for multiple different blocks at the same time.
>>>
>>> Signed-off-by: David Heidelberg <david@ixit.cz>
>>> ---
>>
>> [...]
>>
>>> +&i2c3 {
>>> +    clock-frequency = <400000>;
>>> +
>>> +    status = "okay";
>>> +
>>> +    /* nxp,nxp-nci-i2c @28 */
>>
>> This seems fairly straightforward to enable - could you just
>> do that instead?
> 
> I have patch for it in-tree, but most likely not correct. See notes in:
> 
> https://gitlab.com/sdm845/sdm845-next/-/commit/eeb765bb1166e020a771ed712fec76b56da229ee
> 
> For now, I can only confirm the device is on the i2c address.

Taking a look at just the names of the sdm845-qrd.dtsi/sony modifications for
their sdm845 phones in downstream which I presume have the exact same chip anyway:

notes based on observation and driver (drivers/nfc/nq-nci.c)

        nq@28 {
                compatible = "qcom,nq-nci";
                reg = <0x28>;
                qcom,nq-irq = <&tlmm 63 0x00>; // interrupt, duplicated below
                qcom,nq-ven = <&tlmm 12 0x00>; // voltage enable, ACTIVE_HIGH
                qcom,nq-firm = <&tlmm 62 0x00>; // firmware download, ACTIVE_HIGH
                qcom,nq-clkreq = <&pm8998_gpios 21 0x00>; // clock enable, INPUT
                qcom,nq-esepwr = <&tlmm 116 0x00>; // eSE power enable, ACTIVE_HIGH
                interrupt-parent = <&tlmm>;
                interrupts = <63 0>;
		[... blurb ...]
        };


   pm8998_gpio_21: pm8998_gpio_21 {
                pins = "gpio21";
                function = "normal";
                input-enable;
                bias-pull-down;
                power-source = <1>;
        };


        /* GPIO_62: NFC_DWLD_EN */
        sdm_gpio_62: sdm_gpio_62 {
                mux {
                        pins = "gpio62";
                        function = "gpio";
                };

                config {
                        pins = "gpio62";
                        drive-strength = <2>;
                        bias-disable;
                        output-low;
                };
        };


        /* GPIO_63: NFC_IRQ */
        sdm_gpio_63: sdm_gpio_63 {
                mux {
                        pins = "gpio63";
                        function = "gpio";
                };

                config {
                        pins = "gpio63";
                        drive-strength = <2>;
                        bias-pull-down;
                        input-enable;
                };
        };


        /* GPIO_12 : NFC_VEN */
        sdm_gpio_12: sdm_gpio_12 {
                mux {
                        pins = "gpio12";
                        function = "gpio";
                };

                config {
                        pins = "gpio12";
                        drive-strength = <2>;
                        bias-disable;
                        output-low;
                };
        };

Konrad

  reply	other threads:[~2025-12-17 15:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-16 20:34 David Heidelberg via B4 Relay
2025-12-17 12:04 ` Konrad Dybcio
2025-12-17 15:00   ` David Heidelberg
2025-12-17 15:28     ` Konrad Dybcio [this message]
2025-12-18 22:30       ` David Heidelberg
2025-12-19 10:49         ` Konrad Dybcio

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=5f1282b2-2447-4ce8-a943-90c88e7f5835@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=david@ixit.cz \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh@kernel.org \
    /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

all inboxes | Powered by JetHome®