[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <78b0ca0b-222c-f0bc-9501-98a6bb73e48e@gmail.com>
Date: Mon, 9 Nov 2020 09:25:02 -0800
From: Florian Fainelli <f.fainelli@...il.com>
To: Rafał Miłecki <zajec5@...il.com>,
Vivek Unune <npcomplete13@...il.com>
Cc: Hauke Mehrtens <hauke@...ke-m.de>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@...adcom.com>,
Rob Herring <robh+dt@...nel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/2] ARM: dts: BCM5301X: pinctrl - use correct driver
and define mdio pins
On 11/9/20 9:21 AM, Rafał Miłecki wrote:
> On Wed, 4 Nov 2020 at 21:30, Vivek Unune <npcomplete13@...il.com> wrote:
>> BCM47094 version of pinmux uses different driver and supports mdio
>> pinmux pins. Hence, use the correct driver and define the pins.
>>
>> Signed-off-by: Vivek Unune <npcomplete13@...il.com>
>
> Subject and message are a bit confusing as it's actually a matter of
> chipset specific binding and not a driver.
>
> Change looks OK, thanks for handling that!
>
> Acked-by: Rafał Miłecki <rafal@...ecki.pl>
>
Agreed, applied and fixed up the subject and commit message this way:
ARM: dts: BCM5301X: Use corretc pinctrl compatible for 4709x
BCM47094 version of pinmux uses different compatible and supports MDIO
pinmux pins. Hence, use the correct compatible string and defines the
MDIO pins group.
Thanks!
--
Florian
Powered by blists - more mailing lists