All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@kernel.org>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
	linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	Kevin Hilman <khilman@baylibre.com>,
	devicetree@vger.kernel.org,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH 2/2] ARM: dts: omap4: panda: cleanup bluetooth
Date: Tue, 7 Jan 2025 14:33:55 +0200	[thread overview]
Message-ID: <4e2312b8-78d2-4dec-9911-8fd513eeef25@kernel.org> (raw)
In-Reply-To: <20250104194158.06449a3e@akair>



On 04/01/2025 20:41, Andreas Kemnade wrote:
> Hello Roger,
> 
> Am Sat, 4 Jan 2025 19:29:44 +0200
> schrieb Roger Quadros <rogerq@kernel.org>:
> 
>> Hello Andreas,
>>
>> On 30/12/2024 01:01, Andreas Kemnade wrote:
>>> Bluetooth is available on the other Panda board versions, too, so move
>>> stuff to common and specify the needed clock properly.
>>>
>>> Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
>>> ---
>>>  .../boot/dts/ti/omap/omap4-panda-common.dtsi  | 30 +++++++++++++++--
>>>  arch/arm/boot/dts/ti/omap/omap4-panda-es.dts  | 32 -------------------
>>>  2 files changed, 28 insertions(+), 34 deletions(-)
>>>
>>> diff --git a/arch/arm/boot/dts/ti/omap/omap4-panda-common.dtsi b/arch/arm/boot/dts/ti/omap/omap4-panda-common.dtsi
>>> index c860b590142a..c048ab9af053 100644
>>> --- a/arch/arm/boot/dts/ti/omap/omap4-panda-common.dtsi
>>> +++ b/arch/arm/boot/dts/ti/omap/omap4-panda-common.dtsi
>>> @@ -368,9 +368,7 @@ OMAP4_IOPAD(0x130, PIN_INPUT_PULLUP | MUX_MODE0)	/* i2c4_sda */
>>>  	wl12xx_gpio: wl12xx-gpio-pins {
>>>  		pinctrl-single,pins = <
>>>  			OMAP4_IOPAD(0x066, PIN_OUTPUT | MUX_MODE3)		/* gpmc_a19.gpio_43 */  
>>
>> We could add function name in comment? e.g. /* gpmc_a19.gpio_43 - WLAN_EN */
>>
> This is about existing code, there is still a lot of room to cleanup
> other stuff. 
> 
>>> -			OMAP4_IOPAD(0x06c, PIN_OUTPUT | MUX_MODE3)		/* gpmc_a22.gpio_46 */
>>>  			OMAP4_IOPAD(0x070, PIN_OUTPUT_PULLUP | MUX_MODE3)	/* gpmc_a24.gpio_48 */  
>>
>> This one is FM_EN and has nothing to do with WLAN.
>>
> same here.
>>> -			OMAP4_IOPAD(0x072, PIN_OUTPUT_PULLUP | MUX_MODE3)	/* gpmc_a25.gpio_49 */  
>>>  		>;  
>>>  	};
>>>  
>>> @@ -393,6 +391,22 @@ button_pins: button-pins {
>>>  			OMAP4_IOPAD(0x114, PIN_INPUT_PULLUP | MUX_MODE3)	/* gpio_121 */  
>>>  		>;  
>>>  	};
>>> +
>>> +	bt_pins: bt-pins {
>>> +		pinctrl-single,pins = <
>>> +			OMAP4_IOPAD(0x06c, PIN_OUTPUT | MUX_MODE3)	  /* BTEN */
>>> +			OMAP4_IOPAD(0x072, PIN_OUTPUT_PULLUP | MUX_MODE3) /* BTWAKEUP */  
>>
>> Could we please use comment style <pin name>.<pinmux name> - Function
>> 			OMAP4_IOPAD(0x06c, PIN_OUTPUT | MUX_MODE3)		/* gpmc_a22.gpio_46 - BTEN */
>> 			OMAP4_IOPAD(0x072, PIN_OUTPUT_PULLUP | MUX_MODE3)	/* gpmc_a25.gpio_49 - BTWAKEUP */
>>
> I was a bit lazy with checkpatch.pl. Your proposal generates a lot of
> noise there, so I was too lazy to filter that noise, so I disabled that
> noise. I had it first that way.

What noise? line length exceeded warnings? Those are harmless.
I'd prefer not to loose the pinmux/function information in the comment.

-- 
cheers,
-roger


  reply	other threads:[~2025-01-07 12:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-29 23:01 [PATCH 0/2] ARM: dts: omap4: panda: TiWilink improvements Andreas Kemnade
2024-12-29 23:01 ` [PATCH 1/2] ARM: dts: omap4: panda: fix resources needed for Panda Andreas Kemnade
2024-12-29 23:01 ` [PATCH 2/2] ARM: dts: omap4: panda: cleanup bluetooth Andreas Kemnade
2025-01-04 17:29   ` Roger Quadros
2025-01-04 18:41     ` Andreas Kemnade
2025-01-07 12:33       ` Roger Quadros [this message]
2024-12-30 18:17 ` [PATCH 0/2] ARM: dts: omap4: panda: TiWilink improvements Rob Herring (Arm)
  -- strict thread matches above, loose matches on Subject: below --
2024-12-31 10:44 [PATCH 2/2] ARM: dts: omap4: panda: cleanup bluetooth kernel test robot

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=4e2312b8-78d2-4dec-9911-8fd513eeef25@kernel.org \
    --to=rogerq@kernel.org \
    --cc=aaro.koskinen@iki.fi \
    --cc=andreas@kemnade.info \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=tony@atomide.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 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.