mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Akashdeep Kaur <a-kaur@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: <vigneshr@ti.com>, <kristo@kernel.org>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<sebin.francis@ti.com>, <k-willis@ti.com>
Subject: Re: [PATCH v2] arm64: dts: ti: k3-pinctrl: Add virtual GPIO select mux macros
Date: Tue, 22 Sep 2026 16:06:01 +0530	[thread overview]
Message-ID: <adf3f06f-d2c9-424e-966b-9ef9d51e5104@ti.com> (raw)
In-Reply-To: <20260921174321.vaf2krmhnuhnmael@record>

Hi Nishanth,

On 21/09/26 23:13, Nishanth Menon wrote:
> On 12:05-20260921, Akashdeep Kaur wrote:
>> Add virtual GPIO select mux macros for configuring the vgpio_sel
...
>> @@ -3,11 +3,12 @@
>>    * This header provides constants for pinctrl bindings for TI's K3 SoC
>>    * family.
>>    *
>> - * Copyright (C) 2018-2025 Texas Instruments Incorporated - https://www.ti.com/
>> + * Copyright (C) 2018-2026 Texas Instruments Incorporated - https://www.ti.com/
> 
> Drop this for trivial changes.

Done
> 
>>    */
>>   #ifndef DTS_ARM64_TI_K3_PINCTRL_H
>>   #define DTS_ARM64_TI_K3_PINCTRL_H
>>   
>> +#define VGPIO_SEL_SHIFT         (4)
> 
> Tabs like the rest of the macros? I assume checkpatch --strict didn't catch this?
> 
> Did you check *all* k3 devices to ensure the offset is the same for all
> K3? in the next revision, please add that audit in the diffstat section.

Published the audit findings in the diffstat section of v3.
No, --strict did not catch this. Thanks for the catch! Fixed
> 
>>   #define WKUP_LVL_EN_SHIFT	(7)
>>   #define WKUP_LVL_POL_SHIFT	(8)
>>   #define DEBOUNCE_SHIFT		(11)
>> @@ -111,6 +112,11 @@
>>   #define PIN_WKUP_EN_LEVEL_HIGH		(WKUP_ENABLE | WKUP_ON_LEVEL | WKUP_LEVEL_HIGH)
>>   #define PIN_WKUP_EN			(WKUP_ENABLE | WKUP_ON_EDGE)
>>   
>> +#define PIN_VGPIO_SEL0                  (0 << VGPIO_SEL_SHIFT)
>> +#define PIN_VGPIO_SEL1                  (1 << VGPIO_SEL_SHIFT)
>> +#define PIN_VGPIO_SEL2                  (2 << VGPIO_SEL_SHIFT)
>> +#define PIN_VGPIO_SEL3                  (3 << VGPIO_SEL_SHIFT)
> 
> Same - use tabs (consistent with rest of the file) - also add
> a comment above these to indicate the user should read the trm
> corresponding to the SoC for the meaning of the values - people are
> not going to do git log to know these values should be selected
> carefully based on SoC (same value means different things on different
> SoCs).
Added a comment above as recommended. Fixed to use tabs.
> 
>> +
>>   /* Default mux configuration for gpio-ranges to use with pinctrl */
>>   #define PIN_GPIO_RANGE_IOPAD	(PIN_INPUT | 7)
>>   
>> -- 
>> 2.34.1
>>
> 
Thanks and Regards,
Akashdeep Kaur


      reply	other threads:[~2026-09-22 10:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21  6:35 Akashdeep Kaur
2026-09-21 17:43 ` Nishanth Menon
2026-09-22 10:36   ` Akashdeep Kaur [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=adf3f06f-d2c9-424e-966b-9ef9d51e5104@ti.com \
    --to=a-kaur@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=k-willis@ti.com \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=sebin.francis@ti.com \
    --cc=vigneshr@ti.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

all inboxes | Powered by JetHome®