From: Judith Mendez <jm@ti.com>
To: Nishanth Menon <nm@ti.com>, <devicetree@vger.kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
William Breathitt Gray <william.gray@linaro.org>,
David Lechner <david@lechnology.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-iio@vger.kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH v2 8/8] arm64: defconfig: Enable TI eQEP Driver
Date: Thu, 30 May 2024 10:31:20 -0500 [thread overview]
Message-ID: <223d9482-ede8-4f58-b11a-d82f2556c26b@ti.com> (raw)
In-Reply-To: <ddcab8c0-3772-4134-a3bb-27729e864627@ti.com>
Hi Nishanth,
On 5/24/24 9:13 AM, Judith Mendez wrote:
> Hi Nishanth,
>
> On 5/24/24 12:59 AM, Nishanth Menon wrote:
>> On 18:15-20240523, Judith Mendez wrote:
>>> TI K3 SoC's support eQEP hardware, so enable TI eQEP driver
>>> to be built as a module.
>>
>> All the nodes seem to be only in disabled mode, is there even a single
>> board that is actually using this? if so, why isn't it enabled?
>
> I will add pinmux and enable in the board level dts file.
Question about the above... If I enable eQEP at the board level,
there will be pinmux conflicts. So, I could:
1. Leave eQEP disabled
2. Enable eQEP and disable main_uart1 at the board level dts file
3. Enable eQEP in an overlay and also disable main_uart1
Let me know which option works for you.
~ Judith
>
>>
>>>
>>> Signed-off-by: Judith Mendez <jm@ti.com>
>>> ---
>>> Changes since v1:
>>> - No change
>>> ---
>>> arch/arm64/configs/defconfig | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
>>> index 2c30d617e1802..23d11a1b20195 100644
>>> --- a/arch/arm64/configs/defconfig
>>> +++ b/arch/arm64/configs/defconfig
>>> @@ -1593,6 +1593,7 @@ CONFIG_INTERCONNECT_QCOM_SM8550=y
>>> CONFIG_INTERCONNECT_QCOM_SM8650=y
>>> CONFIG_INTERCONNECT_QCOM_X1E80100=y
>>> CONFIG_COUNTER=m
>>> +CONFIG_TI_EQEP=m
>>> CONFIG_RZ_MTU3_CNT=m
>>> CONFIG_HTE=y
>>> CONFIG_HTE_TEGRA194=y
>>> --
>>> 2.45.1
>>>
>>
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-05-30 15:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 23:15 [PATCH v2 0/8] Enable eQEP DT support for Sitara K3 platforms Judith Mendez
2024-05-23 23:15 ` [PATCH v2 1/8] counter/ti-eqep: Add new ti-am62-eqep compatible Judith Mendez
2024-05-24 21:18 ` David Lechner
2024-05-23 23:15 ` [PATCH v2 2/8] dt-bindings: counter: Add new ti,am62-eqep compatible Judith Mendez
2024-05-24 18:38 ` Conor Dooley
2024-05-24 21:30 ` Judith Mendez
2024-05-25 15:23 ` Conor Dooley
2024-05-29 17:19 ` Judith Mendez
2024-05-24 20:50 ` David Lechner
2024-05-24 20:57 ` David Lechner
2024-05-24 21:44 ` Judith Mendez
2024-05-25 17:49 ` David Lechner
2024-05-29 18:54 ` Judith Mendez
2024-05-24 21:33 ` Judith Mendez
2024-05-23 23:15 ` [PATCH v2 3/8] arm64: dts: ti: k3-am62-main: Add eQEP nodes Judith Mendez
2024-05-23 23:15 ` [PATCH v2 4/8] arm64: dts: ti: k3-am62a-main: " Judith Mendez
2024-05-23 23:15 ` [PATCH v2 5/8] arm64: dts: ti: k3-am62p-main: " Judith Mendez
2024-05-23 23:15 ` [PATCH v2 6/8] arm64: dts: ti: k3-am64-main: " Judith Mendez
2024-05-23 23:15 ` [PATCH v2 7/8] counter: ti-eqep: Allow eQEP driver to be built for K3 devices Judith Mendez
2024-05-24 21:07 ` David Lechner
2024-05-23 23:15 ` [PATCH v2 8/8] arm64: defconfig: Enable TI eQEP Driver Judith Mendez
2024-05-24 5:59 ` Nishanth Menon
2024-05-24 14:13 ` Judith Mendez
2024-05-30 15:31 ` Judith Mendez [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=223d9482-ede8-4f58-b11a-d82f2556c26b@ti.com \
--to=jm@ti.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=vigneshr@ti.com \
--cc=will@kernel.org \
--cc=william.gray@linaro.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