On Fri, 2020-10-30 at 13:02 +0200, Andy Shevchenko wrote: > On Fri, Oct 30, 2020 at 04:58:33PM +0900, Tsuchiya Yuto wrote: > > On Wed, 2020-10-28 at 15:04 -0700, Brian Norris wrote: > > ... > > > On the other hand, I agree that I don't want to break the existing users. > > As you mentioned in the reply to the first patch, I can set the default > > value of this parameter depending on the chip id (88W8897) or DMI matching. > > Since it's a PCIe device you already have ID table where you may add a > driver_data with what ever quirks are needed. Sorry that my comment was misleading. I meant using the quirk framework (that is based on DMI matching) I sent in another series. This applies to the other replies from me. However, thanks to your comment, I remembered that currently, the quirk framework can be used only within pcie.c file. For example, the quirk initialization is currently done in pcie.c file. The mwifiex driver is divided into interface-specific modules (PCIe, SDIO, USB) (e.g., mwifiex_pcie module for PCIe interface) + common module (mwifiex module). So, I need to extend the quirk framework so that it can be used by the mwifiex module globally. I'll make a v2 version of this series with using the updated quirk framework so that it won't change behaviors for existing users.
