[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKUFe6ad027MAg-A3XO7i1=c-Q623JqMPCKV_+Hi+ZpUojBn-Q@mail.gmail.com>
Date: Tue, 18 Jul 2017 00:07:35 +0530
From: Abhishek Shah <abhishek.shah@...adcom.com>
To: Jon Mason <jon.mason@...adcom.com>
Cc: Rafał Miłecki <rafal@...ecki.pl>,
Florian Fainelli <f.fainelli@...il.com>,
"David S . Miller" <davem@...emloft.net>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Network Development <netdev@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
BCM Kernel Feedback <bcm-kernel-feedback-list@...adcom.com>
Subject: Re: [PATCH 2/3] net: ethernet: bgmac: Make IDM register space optional
Hi Jon,
> This also will need to be added to
> drivers/net/ethernet/broadcom/bgmac-bcma.c. Otherwise, the driver
> will no longer work for those platforms. Since this was already
> accepted, please push out a fix ASAP.
>
I do not see how the bcma driver [bgmac-bcma.c] will no longer work.
The whole idea behind introducing this BGMAC_FEAT_IDM_MASK bit
was to keep bcma driver's functionality intact.
The BGMAC_FEAT_IDM_MASK bit is explicitly set by the bgmac-platform driver
and is unset inside the same if the idm register base is provided.
For BCMA driver case, I do not touch BGMAC_FEAT_IDM_MASK bit, i.e. it
is *not* set.
And if it is not set, each idm operation done in bgmac.c will take place.
Please explain if I am missing something here.
Regards,
Abhishek
Powered by blists - more mailing lists