[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5AAF838D.2030105@broadcom.com>
Date: Mon, 19 Mar 2018 10:31:57 +0100
From: Arend van Spriel <arend.vanspriel@...adcom.com>
To: Alexey Roslyakov <alexey.roslyakov@...il.com>, andrew@...n.ch,
kvalo@...eaurora.org, robh+dt@...nel.org, mark.rutland@....com,
franky.lin@...adcom.com, hante.meuleman@...adcom.com,
chi-hsien.lin@...ress.com, wright.feng@...ress.com,
netdev@...r.kernel.org
Cc: linux-wireless@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, brcm80211-dev-list.pdl@...adcom.com,
brcm80211-dev-list@...ress.com
Subject: Re: [PATCH net-next v2 2/2] dt: bindings: add new dt entries for
brcmfmac
On 3/19/2018 2:40 AM, Alexey Roslyakov wrote:
> In case if the host has higher align requirements for SG items, allow
> setting device-specific aligns for scatterlist items.
>
> Signed-off-by: Alexey Roslyakov <alexey.roslyakov@...il.com>
> ---
> Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt b/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt
> index 86602f264dce..187b8c1b52a7 100644
> --- a/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt
> +++ b/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt
> @@ -17,6 +17,11 @@ Optional properties:
> When not specified the device will use in-band SDIO interrupts.
> - interrupt-names : name of the out-of-band interrupt, which must be set
> to "host-wake".
> + - brcm,broken-sg-support : boolean flag to indicate that the SDIO host
> + controller has higher align requirement than 32 bytes for each
> + scatterlist item.
> + - brcm,sd-head-align : alignment requirement for start of data buffer.
> + - brcm,sd-sgentry-align : length alignment requirement for each sg entry.
Hi Alexey,
Thanks for the patch. However, the problem with these is that they are
characterizing the host controller and not the wireless device. So from
device tree perspective , which is to describe the hardware, these
properties should be SDIO host controller properties. Also I am not sure
if the broken-sg-support is still needed. We added that for omap_hsmmc,
but that has since changed to scatter-gather emulation so it might not
be needed anymore.
Regards,
Arend
Powered by blists - more mailing lists