[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220112121411.qq2egpoujtsvswla@pali>
Date: Wed, 12 Jan 2022 13:14:11 +0100
From: Pali Rohár <pali@...nel.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Jérôme Pouiller <jerome.pouiller@...abs.com>,
devel@...verdev.osuosl.org, devicetree@...r.kernel.org,
Ulf Hansson <ulf.hansson@...aro.org>, netdev@...r.kernel.org,
linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org,
Rob Herring <robh+dt@...nel.org>, linux-mmc@...r.kernel.org,
"David S . Miller" <davem@...emloft.net>,
Kalle Valo <kvalo@...eaurora.org>
Subject: Re: [PATCH v9 08/24] wfx: add bus_sdio.c
On Wednesday 12 January 2022 13:06:17 Greg Kroah-Hartman wrote:
> On Wed, Jan 12, 2022 at 12:43:32PM +0100, Pali Rohár wrote:
> > Btw, is there any project which maintains SDIO ids, like there is
> > pci-ids.ucw.cz for PCI or www.linux-usb.org/usb-ids.html for USB?
>
> Both of those projects have nothing to do with the kernel drivers or
> values at all, they are only for userspace tools to use.
>
> So even if there was such a thing for SDIO ids, I doubt it would help
> here.
Why do you doubt? For sure if would help! Just checking comments if some
user reported different card with this id would tell us how broken it is
and how sane it is to define macro for particular id.
Powered by blists - more mailing lists