From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4FF51C2D0C8 for ; Sun, 22 Dec 2019 04:35:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 10DAB206B7 for ; Sun, 22 Dec 2019 04:35:51 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="Cv0SnhHu" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726729AbfLVEft (ORCPT ); Sat, 21 Dec 2019 23:35:49 -0500 Received: from mail-lj1-f196.google.com ([209.85.208.196]:38168 "EHLO mail-lj1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726339AbfLVEft (ORCPT ); Sat, 21 Dec 2019 23:35:49 -0500 Received: by mail-lj1-f196.google.com with SMTP id k8so14357197ljh.5; Sat, 21 Dec 2019 20:35:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=COqV+F9ei+E2oY/KUB0AC+nOpaJlD5cnAnx3su+cln8=; b=Cv0SnhHugHFXM1wehyT8ZP9WXuaIPyVcBG6QAPwrblORdbVMiTAq5PHe4q50nyM/yb 7uEgLheCNNJx5Q34a5dRlsr3bz70WQoFgnfd0vNUZc/DPyzWEnmrb/N7VVxEpHzA6gte O8jawT7C5MPN4poBDjy1xgqL74lKqd7+xQmN5rVfGQIr7BuYYHWMPG/V9aqYIthcXXSg cazi3FoZXNrpwOAhTN/CBxTcxmMwWW7jMBTMGZcf16SPjrPx+z7QlU9i6arOrqjdSYZ/ N42CdQnpuBqd4eOwRVh7LrPJAQ2OX3lVzj95Ewy1hLSsPULxOhX8qH2uuHbXR11a+KCJ /oyw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=COqV+F9ei+E2oY/KUB0AC+nOpaJlD5cnAnx3su+cln8=; b=ZVjCXS11NRf2SAS7Mkw6Mh3wDSNCNAVzBuoE8WOg+Fs1GNvbTM+ugWXSH7SKcCBbXb dDCzZPICULzcrtu6tmazoFBck4ahWVgGqEuYQo1NOq0hVNb16A6z28KsD8Pl7arlMF7m ilDZH+wnF/4ohk9yq0fdDxgO9+84o6eXfoUiE6lfRlFblzHJFwuB+5cAwA3p1NQ/Eypc YyMkOtCtLhluRR+G9xOB60OgemzUZwo/PgflbuY9CAhtggLLkp+MDJbMPj/hIQ4t7fJ9 NxQsssUK6wWi1ECqtw9mm2tT6vCmLCK4qUukIvtZek/9VNOuCCrvEMogt5o9Phd4ED7c QtxQ== X-Gm-Message-State: APjAAAWPKW7Ugkr0TxWXA3KYNtwNm5PQRuyeV5mK+BankAckDlAR7fVG qtbm7/NO4VPLJnMcnrnukiU= X-Google-Smtp-Source: APXvYqwwHNpyqONsjbrnnDi7Do8gsYy7HpNpEiploEtWoEqRQpQQl2rppymPVsg7yDY255l1Q74Klw== X-Received: by 2002:a2e:88c5:: with SMTP id a5mr14669392ljk.201.1576989347408; Sat, 21 Dec 2019 20:35:47 -0800 (PST) Received: from [172.20.1.19] ([5.42.224.242]) by smtp.gmail.com with ESMTPSA id g15sm1827895ljl.10.2019.12.21.20.35.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 21 Dec 2019 20:35:46 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: [PATCH v2 0/9] brcmfmac: add support for BCM4359 SDIO chipset From: Christian Hewitt In-Reply-To: Date: Sun, 22 Dec 2019 07:35:43 +0300 Cc: Kalle Valo , Heiko Stuebner , linux-wireless@vger.kernel.org, brcm80211-dev-list.pdl@broadcom.com, brcm80211-dev-list@cypress.com, netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org, Neil Armstrong Content-Transfer-Encoding: quoted-printable Message-Id: <47DB71CE-ACC4-431D-9E66-D28A8C18C0A4@gmail.com> References: <20191211235253.2539-1-smoch@web.de> To: Soeren Moch X-Mailer: Apple Mail (2.3445.104.11) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org > On 19 Dec 2019, at 2:04 am, Soeren Moch wrote: >=20 > I guess you need similar enhancements of the board device tree as in > patch 8 of this series for your VIM3 board. Wider testing now points to a known SDIO issue (SoC bug) with Amlogic = G12A/B hardware. The merged workaround for the bug was only tested with = bcmdhd and brcmfmac may require tweaking as the same issue exhibits on = an Amlogic G12B device with BCM4356 chip. Testing the series with = Amlogic GXM (older) and SM1 (newer) hardware to exclude the SoC bug = shows everything working as expected. Christian=