[From nobody Thu Jun 25 05:55:01 2020 Received: from mail-ot1-x335.google.com ([2607:f8b0:4864:20::335]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1gnBLE-00036M-B0 for openwrt-devel@lists.openwrt.org; Fri, 25 Jan 2019 23:56:58 +0000 Received: by mail-ot1-x335.google.com with SMTP id n8so10146837otl.6 for <openwrt-devel@lists.openwrt.org>; Fri, 25 Jan 2019 15:56:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VRaKuCPl/8jeJRgUpaiGDx5q2XfX+AX8sQL4vSZ4awM=; b=vHdeJ+kVZh4u1nyFShObAJ9Ahd3C3EOO0kK5qmYCNblvp3DXvlqQXFT2DI/BTgofbX iNGA2uPZZcTMlqQzGoI7atP0BZfbV9EZhM1DFm5h/r6NJuPSEnkRRUIOf5ftU5ZTlYOd T0aNI4FK302T8Kyv5plWGzHta5ZLeDd6Qs9JGAkL8qCF960FwDVnu1l0En5M7YN5Yyhp edSPGZid6oyhWtYpMrCjYoTLcebgmfSaQVKLs4Er43gqaMoEHQHpKWrorpAweFm80e6d dEwAex177rZziWCjtTA6NNfAaP5EBZR5zWBS6iRROPBWPekmA6U95ZM7rLI+kOUchFLt debA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VRaKuCPl/8jeJRgUpaiGDx5q2XfX+AX8sQL4vSZ4awM=; b=Mud0UavpSMkVtH/mKoGXbtIXX+DUMZ8X8+s3aouuAqMfwWSwsPCnbw6DlqgPEK5qdf dISh4E/OU+bMU/PaRn/YqsKEBZnu9WYkjmZI4xfCT1Gbpz1Qj5doW6tLx0LeVO6abBI7 VByXJFrmrnbx+IiaZ+o6TfRo5mfRQejiIlNzagXRaXyce4EbomuwuRyROYNPraywZ7Po SvRG7FCubj4RFrVWBE6WGf6RuXkvZyUm5+Y8oBZY1nQpGIoC0vNbeyrp+3mXtC+gajnR I20Bh6cn20dG/eJXaamUmmezoMMLn4M71R4MP6SLXDRyhEzXlyiDDwpewxb8tbLoYgfz xmcw== X-Gm-Message-State: AJcUukdkh4fSNl/TggfyR+5LVS9XSN1Z8EMs+0rqqqw85Ovq/lJMcLPi +xfc2+oc/H5mBGeqNnk99hrRjaEy3PhcJ77FAVw= X-Google-Smtp-Source: ALg8bN6L62WXSCbwvTZkeCTCzuyooicc8htxVAbnSkxJ9m8ZmIws8n1FazgVsQPYwr01Pt04h59v2mOx8u4qG/R3b3M= X-Received: by 2002:a9d:715d:: with SMTP id y29mr9573252otj.148.1548460612515; Fri, 25 Jan 2019 15:56:52 -0800 (PST) MIME-Version: 1.0 References: <80f2f3e3-3bd8-5200-1acc-6439b82e7b0f@wagsky.com> In-Reply-To: <80f2f3e3-3bd8-5200-1acc-6439b82e7b0f@wagsky.com> From: Martin Blumenstingl <martin.blumenstingl@googlemail.com> Date: Sat, 26 Jan 2019 00:56:41 +0100 Message-ID: <CAFBinCBhoMHpccPhXhsN_Q9BA2vRFVUgSJYL03phXEyxkPf_yg@mail.gmail.com> Subject: Re: [OpenWrt-Devel] ath79 (qca95xx): Status of SPI-Attached NAND Drivers? To: Jeff Kletsky <lede@allycomm.com> Cc: openwrt-devel@lists.openwrt.org Content-Type: text/plain; charset="UTF-8" X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190125_155656_409847_64237CF2 X-CRM114-Status: GOOD ( 11.26 ) X-Spam-Score: -0.2 (/) X-Spam-Report: SpamAssassin version 3.4.2 on bombadil.infradead.org summary: Content analysis details: (-0.2 points) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [2607:f8b0:4864:20:0:0:0:335 listed in] [list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (martin.blumenstingl[at]googlemail.com) 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID_EF Message has a valid DKIM or DK signature from envelope-from domain -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain Hi, (disclaimer: my knowledge about the ath79 SoC is pretty limited) On Fri, Jan 25, 2019 at 10:09 PM Jeff Kletsky <lede@allycomm.com> wrote: [...] > * What is the level of support for QCA9531 and QCA9563 SoCs for NAND? for SPI NAND chips the SoC has to implement an SPI controller the NAND controller is inside the SPI NAND chip itself some SoCs (I believe also some of the ath79 SoCs) integrate a parallel NAND controller. this has nothing to do with the SPI NAND devices though this doesn't answer your question, but the question (and thus the answer) depends on the hardware you have: 1) SPI NAND: is the SPI controller supported? and: is the SPI NAND chip supported? 2) parallel NAND: is the SoC's NAND controller supported? and: is the NAND chip supported? based on your other question I believe you want to know the status of case 1) [...] > * Linux Kernel commit eaa76499711535fd64d747cc4ef0d78ab0fd41c > > Merge tag 'mtd/for-4.21' of git://git.infradead.org/linux-mtd > > SPI-NAND drivers changes: > - Remove the depreacated mt29f_spinand driver from staging. > > > (At least that's a while off, but reinforces the unwillingness of > upstream acceptance of keeping the mt29f_spinand driver alive.) the mt29f_spinand driver was removed in favor of the MTD SPI NAND driver, see [0] (the mt29f_spinand only supported the Micron SPI NAND chips. the new MTD SPI NAND driver implements vendor agnostic logic and hooks where NAND manufacturer specific logic can be integrated) 4.19 was the first kernel with the MTD SPI NAND driver (that gives you context to mkresin's comment) Regards Martin [0] https://github.com/torvalds/linux/tree/master/drivers/mtd/nand/spi ]