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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 0AE1CC433F5 for ; Tue, 21 Dec 2021 16:11:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Content-Type: List-Subscribe:List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id: In-Reply-To:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date: Reply-To:Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date :Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=eHWRVtACSjuzQ2GlizA7quKQe84SkgkrcFa/6F1qvLM=; b=NAYb8GEhgA3GGULoArN5XRcGT1 awy3/mXBBWP0tapGgfTkMQLIgQTi/thKlEF5QpEF273vHwtIDfEasGE+q17xdKzo7cEyRPzsX82L8 ayCiGjnT6NfPkuUASq7qP85SaPPg/6wzuhJ6u0GAv1MRkhBstAdl3nTbLVtO3GbxTe4B0jW4eKz94 lI+vfkigQ0oou3d8nFd7JXrv3zrXnXD3Cb0j71WH7acJHhY0h8OOXWC/DZFXDBWbvmRyFf+NJ2qj9 Kuj3ePZaX2Ibn9Dby1g8n3HwgW82iR8nsrjtIrdx0gjJKQt3aIUiGnbcNiU88yHG7Uvi2i7wNwTD1 O7U6YoQg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mzhhs-007W2Q-88; Tue, 21 Dec 2021 16:09:40 +0000 Received: from mail-qv1-xf2e.google.com ([2607:f8b0:4864:20::f2e]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1mzhhp-007W1w-6l for linux-arm-kernel@lists.infradead.org; Tue, 21 Dec 2021 16:09:38 +0000 Received: by mail-qv1-xf2e.google.com with SMTP id q4so6219371qvh.9 for ; Tue, 21 Dec 2021 08:09:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=konsulko.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=sDHaRbhuC79BvGEiY197i/14OhtcoJmxWUUsJ+hn1tM=; b=AWIEpNjI0GhhacozwgXfNDX8HXru6njjnqzuOakQpFbzg0QGvP9eC1eXYeLtovkZf3 pXG37qJeKRrA2jHAjPcBxHr1auYJfg8mNBhVXC8b17MWr/4irNUkEMqOza5G14kKBf0D tJPSGx5XSrb2y2dsYd4Jt6BML/La7k2bAtll4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=sDHaRbhuC79BvGEiY197i/14OhtcoJmxWUUsJ+hn1tM=; b=OKg91jU28kbLXhxN7O9Ey7wS0W068YgeZlAFl5lWpOF1S3ibu9cKaK0nBUw2wKGMwC ZKPhHsz+5vSsDSaXiMQU8q4BPqBbmySqVoVtny6UIGGSPCFByt767rX17J5c86HDzSF9 3K+1hTBEBbyITINi/rEkZATKQN5BUvujwtemrV7lEMupyGWFTqINqO12CXWojybPVDrg I2XfWsXdsLOStHpe7CUzvXNyy9mSuCsBSFcaneQnGCrA8wqvsw0hudWebQbAabGjb2vP 50UEwwfgu44Ombp227UL6TlyWiTvC7Sj6BEkznvH62kMH1G5YmfKYAcrcZAq1OW2kFbe L/MQ== X-Gm-Message-State: AOAM532LlwLsi4WutgOBjiKJNO65hrJz2oNixy2Hu0zJrh2fafM/nFUo RmFE6T1zcdW8tZW2L+Ht+6gWbA== X-Google-Smtp-Source: ABdhPJz0w0/IwKbdnz/unPro2aAspCcZT1Eu2iawUsmmWEfjRFqBP2h+TqQfprKzOuORjbN2gVfCOA== X-Received: by 2002:a05:6214:400e:: with SMTP id kd14mr2790790qvb.68.1640102976088; Tue, 21 Dec 2021 08:09:36 -0800 (PST) Received: from bill-the-cat (2603-6081-7b01-cbda-04c9-073b-bd3f-c77c.res6.spectrum.com. [2603:6081:7b01:cbda:4c9:73b:bd3f:c77c]) by smtp.gmail.com with ESMTPSA id b11sm16667254qtx.85.2021.12.21.08.09.35 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 21 Dec 2021 08:09:35 -0800 (PST) Date: Tue, 21 Dec 2021 11:09:33 -0500 From: Tom Rini To: Arnd Bergmann Cc: Vignesh Raghavendra , Nishanth Menon , Olof Johansson , SoC , arm-soc , Tero Kristo , Linux ARM , Linux Kernel Mailing List Subject: Re: [GIT PULL 1/2] arm64: TI K3 SoC configs changes for v5.17 Message-ID: <20211221160933.GM2773246@bill-the-cat> References: <20211217172806.10023-1-vigneshr@ti.com> <06e60038-1365-fc35-801e-448c9025fb2a@ti.com> <20211221153250.GA2081238@bill-the-cat> MIME-Version: 1.0 In-Reply-To: X-Clacks-Overhead: GNU Terry Pratchett X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20211221_080937_282934_C1BA0B2D X-CRM114-Status: GOOD ( 28.13 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8623392739794684253==" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org --===============8623392739794684253== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="fzZfjcV6kaBgkq89" Content-Disposition: inline --fzZfjcV6kaBgkq89 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 21, 2021 at 04:55:48PM +0100, Arnd Bergmann wrote: > On Tue, Dec 21, 2021 at 4:32 PM Tom Rini wrote: > > On Mon, Dec 20, 2021 at 11:10:25PM +0530, Vignesh Raghavendra wrote: > > > > > > Currently its not possible to build PCIE_CADENCE_PLAT_HOST/EP drivers= as > > > modules (symbols are bool only). > > > PCIe is not necessary for basic boot either. So, I can drop these > > > configs until these drivers are build able as modules, if you prefer. > > > > Is PCIe required for basic boot for the other platforms in the defconfig > > which do enable it in the defconfig today? It is required for non-basic > > boot (whatever storage one puts in a PCIe slot). If someone is going to > > be fixing the PCIe driver to be able to be modular, that's fine too but > > I ran in to this trying to see what works out of the box in the > > defconfig, on this platform and hit both of these rather large > > omissions. >=20 > If PCI is often used for storage, then that's ok. There are a number of > other platforms where PCIe is only used for wireless networking or > other secondary devices, but they are still built-in because they got > added before it became possible for PCIe host drivers to be loadable > modules. I would like to eventually go through and turn those into > loadable modules, but for the moment it would be good to only add > built-in drivers where this is actually useful. That's good to know. My question tho is, what's actually useful? The EVM is 2 PCIe x8 type slots. I honestly don't know if that means "super useful, arbitrary devices are expected to work" or "not useful, arbitrary devices are not expected to work". Is the functional definition of what's in the defconfig vs left up to users, distributions, etc, to find and enabled defined, or at least well known / explained somewhere? Where I'm coming from on this is that these platforms practically are, and can be SystemReady IR certified. So what's needed here to ensure there's a good experience distros to enable what needs enabling for full functionality? What we hit was "lets throw some stuff at this board to test it out and.. wait, PCIe isn't enabled at all? USB host isn't enabled at all?" And all that said, if someone is going to be fixing the PCIe drivers to be enabled as modules soon, and just getting it handled that way in the next appropriately timed merge window, OK, fine, good enough. --=20 Tom --fzZfjcV6kaBgkq89 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGzBAABCgAdFiEEGjx/cOCPqxcHgJu/FHw5/5Y0tywFAmHB/DcACgkQFHw5/5Y0 tyyG8gv+PfvguS1egaG9IzL+unAozNxHjgHPHeglLDukR0djwaNh8fM2uvo5Ll0+ aPkw20zu0aFXIhs2vtICLFD0SEhwKzrKN33eKUFboD8rFdgIvw7CMhIAsZgaIuu0 DZVy2XE4k40AO/iNGcTjegUa+zMUHDJ8xNQFb/q9iV5muynaeD5AKvSqa/j/z8xE SJT8RCsbpm0ZW156jqTOObOmCr/9lN9/hrZmENDgnWp1O35LJEkxaPhiuPR1utix td1Kdflw4+z0EqoBJcnzOzD0/XInZFCQ0b5sSl94XWVvuBR6dmhVrPasySQOB+ci MyQeWtOY8P4VhTE7OlIb25UiyzlFpKFZelvF0MFeNjx7Sz5S8bPHjgBr2ry17r7A 8pNxc8pUDwgofwSZOxNBJQeHma+xLW4UiQvR7LMbRB9g6HIv7wEz9m/EoQLjurfL oSLB9y/1Tw+cfi/df11aShUgKsko71gCLCFJFsHOYfgUVzilaHORo69CfFcqCmC5 3E+Umpnh =rBqo -----END PGP SIGNATURE----- --fzZfjcV6kaBgkq89-- --===============8623392739794684253== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel --===============8623392739794684253==--