| Message ID | ACC0D1F6-7857-4FF0-A474-4EC699572E1B@live.com |
|---|---|
| State | Superseded |
| Headers | show |
| Series | [1/2] brcmfmac: Use separate struct to declare firmware names for Apple OTP chips | expand |
> I think my reply to Arend flew over your head. Sorry. I am not that good in English so sometimes do misinterpret things. > > My point was that I'd rather have the Broadcom/Cypress people actually > answer my question so we can figure out how to do this *properly*, > instead of doing "safer-but-dumb" things (like this patch) because we > just don't have the information to do it properly. > > - Hector
On January 2, 2023 4:15:41 PM Hector Martin <marcan@marcan.st> wrote: > On 02/01/2023 23.40, Aditya Garg wrote: >> From: Aditya Garg <gargaditya08@live.com> >> >> Commit 'dce45ded7619' added support for 89459 chip pcie device. It uses the >> BRCM4355 chip which is also found in Apple hardware. However this commit >> causes conflicts in the firmware naming between Apple hardware, which >> supports OTP and other non-Apple hardwares. So, this patch makes these >> Apple chips use their own firmware table so as to avoid possible conflicts >> like these in the future. > > I think my reply to Arend flew over your head. > > My point was that I'd rather have the Broadcom/Cypress people actually > answer my question so we can figure out how to do this *properly*, > instead of doing "safer-but-dumb" things (like this patch) because we > just don't have the information to do it properly. Fair enough. Can you accurately (re)state your question and I will try to answer it. Regards, Arend > - Hector
On 2023/01/03 3:27, Arend Van Spriel wrote: > On January 2, 2023 4:15:41 PM Hector Martin <marcan@marcan.st> wrote: > >> On 02/01/2023 23.40, Aditya Garg wrote: >>> From: Aditya Garg <gargaditya08@live.com> >>> >>> Commit 'dce45ded7619' added support for 89459 chip pcie device. It uses the >>> BRCM4355 chip which is also found in Apple hardware. However this commit >>> causes conflicts in the firmware naming between Apple hardware, which >>> supports OTP and other non-Apple hardwares. So, this patch makes these >>> Apple chips use their own firmware table so as to avoid possible conflicts >>> like these in the future. >> >> I think my reply to Arend flew over your head. >> >> My point was that I'd rather have the Broadcom/Cypress people actually >> answer my question so we can figure out how to do this *properly*, >> instead of doing "safer-but-dumb" things (like this patch) because we >> just don't have the information to do it properly. > > Fair enough. Can you accurately (re)state your question and I will try to > answer it. As per my original email: Is the CYW89459 just a rebrand of the BCM4355, or just a subset? Can we consider them equivalent, and equivalent to the Apple part (BCM4355C1 / revision 12)? More specifically: - What BCM4355 variants exist in the wild, and what are their PCI device IDs and revision IDs? - Is a single firmware nominally intended to be compatible with all of those variants? Does that include the CYW89459 branded parts? - If CYW89459 is a rebrand of BCM4355, is it complete, or are there still chips being sold as BCM4355? Even more specifically, bcmdhd has these device IDs: #define BCM4355_D11AC_ID 0x43dc /* 4355 802.11ac dualband device */ #define BCM4355_D11AC2G_ID 0x43fc /* 4355 802.11ac 2.4G device */ #define BCM4355_D11AC5G_ID 0x43fd /* 4355 802.11ac 5G device */ But the patch I'm replying to uses PCI ID 0x4355, which instead should be: #define BCM43237_D11N_ID 0x4355 /* 43237 802.11n dualband device */ #define BCM43237_D11N5G_ID 0x4356 /* 43237 802.11n 5GHz device */ So what's up with the BCM43237? Is that a 4355 variant? Is this what got rebranded as CYW89459? Is it firmware-compatible with the others? <rant> I'm going to be honest here: I'm quite saddened by the state of brcmfmac and Broadcom's neglect of this driver. Other than the Apple OTP / firmware selection shenanigans, everything else I'm having to implement to support Apple machines are features that Broadcom's downstream bcmdhd driver *already* supports on non-Apple machines, not Apple-specific. Not only that, people are asking for modern WiFi features like newer crypto modes that bcmdhd supports but brcmfmac doesn't. It seems clear that Broadcom isn't interested in maintaining this driver and updating it to support newer chips and features. So I'm basically doing your job for you all. Which is fine, but if I'm going to be in charge of implementing all this stuff for you, *please* help me by at least clarifying the device variant / firmware feature related issues, because getting that wrong will cause regressions or firmware naming scheme breaks down the line, and that sucks for users. </rant> - Hector
On 1/3/2023 4:55 AM, Hector Martin wrote: > On 2023/01/03 3:27, Arend Van Spriel wrote: >> On January 2, 2023 4:15:41 PM Hector Martin <marcan@marcan.st> wrote: >> >>> On 02/01/2023 23.40, Aditya Garg wrote: >>>> From: Aditya Garg <gargaditya08@live.com> >>>> >>>> Commit 'dce45ded7619' added support for 89459 chip pcie device. It uses the >>>> BRCM4355 chip which is also found in Apple hardware. However this commit >>>> causes conflicts in the firmware naming between Apple hardware, which >>>> supports OTP and other non-Apple hardwares. So, this patch makes these >>>> Apple chips use their own firmware table so as to avoid possible conflicts >>>> like these in the future. >>> >>> I think my reply to Arend flew over your head. >>> >>> My point was that I'd rather have the Broadcom/Cypress people actually >>> answer my question so we can figure out how to do this *properly*, >>> instead of doing "safer-but-dumb" things (like this patch) because we >>> just don't have the information to do it properly. >> >> Fair enough. Can you accurately (re)state your question and I will try to >> answer it. > > As per my original email: Is the CYW89459 just a rebrand of the BCM4355, > or just a subset? Can we consider them equivalent, and equivalent to the > Apple part (BCM4355C1 / revision 12)? There is probably no easy answer. Mainly because Cypress is a separate entity. However, they use the same/similar technology and code base. So let me first start with the chip naming. The wifi chip primarily has a number and revision. The chip number is straighforward and can be read from the device. The chip revision comes in two variants: 1) simple increasing number as read from the device, and 2) a <letter><digit> format. The latter start at a0, which you almost never see in the wild unless we do it "first time right". Whenever spinning a new chip we either increase the digit or the letter depending on type/amount of changes. There is not predictable mapping between the revision variants. Depending on the hurdles in a chip project we may move from a0 to b0, or from b0 to b1 or whatever. If CYW89459 chip reads chip number 0x4355 than it is a BCM4355. If it is a different revision it may require different firmware. A different letter will always require different firmware. A different digit may work although the firmware can have code paths for a specific revision. The firmware tables in pcie.c have the revmask. With our crystal ball being out-of-order we tend to enable a firmware for all revisions (0xFFFFFFFF) unless proven otherwise. If otherwise, we come up with a sensible new name and add a new entry to the firmware table changing the revmasks accordingly. > More specifically: > - What BCM4355 variants exist in the wild, and what are their PCI device > IDs and revision IDs? Who knows. The PCI revision ID always equals the chip revision afaik. The PCI device IDs should be as below. > - Is a single firmware nominally intended to be compatible with all of > those variants? Does that include the CYW89459 branded parts? > - If CYW89459 is a rebrand of BCM4355, is it complete, or are there > still chips being sold as BCM4355? > > Even more specifically, bcmdhd has these device IDs: > > #define BCM4355_D11AC_ID 0x43dc /* 4355 802.11ac dualband device */ > #define BCM4355_D11AC2G_ID 0x43fc /* 4355 802.11ac 2.4G device */ > #define BCM4355_D11AC5G_ID 0x43fd /* 4355 802.11ac 5G device */ > > But the patch I'm replying to uses PCI ID 0x4355, which instead should be: > > #define BCM43237_D11N_ID 0x4355 /* 43237 802.11n dualband device */ > #define BCM43237_D11N5G_ID 0x4356 /* 43237 802.11n 5GHz device */ > > So what's up with the BCM43237? Is that a 4355 variant? Is this what got > rebranded as CYW89459? Is it firmware-compatible with the others? Right. If you have come across a BCM4355 with PCI device ID 0x4355 than my best guess would be that their OTP is corrupted and the PCIe core on the chip uses its default as stored in hardware, which equals the chip number. This is really a fallback for a faulty device (or a device which does not have its OTP programmed). > <rant> > > I'm going to be honest here: I'm quite saddened by the state of brcmfmac > and Broadcom's neglect of this driver. Other than the Apple OTP / > firmware selection shenanigans, everything else I'm having to implement > to support Apple machines are features that Broadcom's downstream bcmdhd > driver *already* supports on non-Apple machines, not Apple-specific. Not > only that, people are asking for modern WiFi features like newer crypto > modes that bcmdhd supports but brcmfmac doesn't. It seems clear that > Broadcom isn't interested in maintaining this driver and updating it to > support newer chips and features. So I'm basically doing your job for > you all. Which is fine, but if I'm going to be in charge of implementing > all this stuff for you, *please* help me by at least clarifying the > device variant / firmware feature related issues, because getting that > wrong will cause regressions or firmware naming scheme breaks down the > line, and that sucks for users. > > </rant> Happy New year to you. Thanks for clearly marking the rant. Makes it easier to ignore, but let me get into this. I would not call bcmdhd the downstream driver. It is a separate out-of-tree driver. Indeed resources were pulled from brcm80211 development, but there always have been only 2 or 3 people working on it. Me being the constant working mule and these days only for 20% of my working hours to do the job. So you are not really doing our job as we are not assigned to do so. I guess there is no ROI for Broadcom or so it is perceived and there is no customer pushing for it. That said I am always happy to help and clarify whatever I can. Regards, Arend
On 03/01/2023 22.30, Arend van Spriel wrote: > On 1/3/2023 4:55 AM, Hector Martin wrote: >> On 2023/01/03 3:27, Arend Van Spriel wrote: >>> On January 2, 2023 4:15:41 PM Hector Martin <marcan@marcan.st> wrote: >>> >>>> On 02/01/2023 23.40, Aditya Garg wrote: >>>>> From: Aditya Garg <gargaditya08@live.com> >>>>> >>>>> Commit 'dce45ded7619' added support for 89459 chip pcie device. It uses the >>>>> BRCM4355 chip which is also found in Apple hardware. However this commit >>>>> causes conflicts in the firmware naming between Apple hardware, which >>>>> supports OTP and other non-Apple hardwares. So, this patch makes these >>>>> Apple chips use their own firmware table so as to avoid possible conflicts >>>>> like these in the future. >>>> >>>> I think my reply to Arend flew over your head. >>>> >>>> My point was that I'd rather have the Broadcom/Cypress people actually >>>> answer my question so we can figure out how to do this *properly*, >>>> instead of doing "safer-but-dumb" things (like this patch) because we >>>> just don't have the information to do it properly. >>> >>> Fair enough. Can you accurately (re)state your question and I will try to >>> answer it. >> >> As per my original email: Is the CYW89459 just a rebrand of the BCM4355, >> or just a subset? Can we consider them equivalent, and equivalent to the >> Apple part (BCM4355C1 / revision 12)? > > There is probably no easy answer. Mainly because Cypress is a separate > entity. However, they use the same/similar technology and code base. So > let me first start with the chip naming. The wifi chip primarily has a > number and revision. The chip number is straighforward and can be read > from the device. The chip revision comes in two variants: 1) simple > increasing number as read from the device, and 2) a <letter><digit> > format. The latter start at a0, which you almost never see in the wild > unless we do it "first time right". Whenever spinning a new chip we > either increase the digit or the letter depending on type/amount of > changes. There is not predictable mapping between the revision variants. > Depending on the hurdles in a chip project we may move from a0 to b0, or > from b0 to b1 or whatever. Right, this is standard chip spin numbering, that much I know. > If CYW89459 chip reads chip number 0x4355 than it is a BCM4355. If it is > a different revision it may require different firmware. A different > letter will always require different firmware. A different digit may > work although the firmware can have code paths for a specific revision. So is it always correct to have the same firmware (in a generic situation, not a customized OEM build) for, say, a BCM4355 rev 12, regardless of what the PCI ID programmed into the OTP is (and what the marketing device name is)? If so, then my conclusion is that the original patch I replied to is incorrect, all the defines should've been called BCM4355 (not the Cypress part number), and we probably need two firmware table entries since (judging by the revision check elsewhere in that patch) there are other revisions in the wild than the one Apple uses, and therefore there should at the very least be a firmware name split at C1. It would then be very helpful to know what revisions *do* exist and their correct naming. If different PCI device IDs might need different firmware, then the exiting firmware selection/table mechanism is insufficient. > Happy New year to you. Thanks for clearly marking the rant. Makes it > easier to ignore, but let me get into this. I would not call bcmdhd the > downstream driver. It is a separate out-of-tree driver. Indeed resources > were pulled from brcm80211 development, but there always have been only > 2 or 3 people working on it. Me being the constant working mule and > these days only for 20% of my working hours to do the job. So you are > not really doing our job as we are not assigned to do so. I guess there > is no ROI for Broadcom or so it is perceived and there is no customer > pushing for it. That said I am always happy to help and clarify whatever > I can. Is there any chance you can provide a list of chips/shipping revisions and revision IDs, so we can stop guessing at the mappings in the firmware table? Because this is effectively breaking userspace ABI every time we make a change to an existing chip, as it can change the firmware file name that userspace loads. This already happened with BCM4364, where (at least) B2 and B3 revisions exist in the wild and we need separate firmwares, yet it was added with a full mask, resulting in people copying "the right firmware for them" manually and my patch to split it into properly named firmwares will break those users. - Hector
> On Jan 3, 2023, at 8:30 AM, Arend van Spriel <arend.vanspriel@broadcom.com> wrote: > > On 1/3/2023 4:55 AM, Hector Martin wrote: >> More specifically: >> - What BCM4355 variants exist in the wild, and what are their PCI device >> IDs and revision IDs? > > Who knows. The PCI revision ID always equals the chip revision afaik. The PCI device IDs should be as below. If the day ever came where the FCC inquired about a theoretical spurious radio emissions issue in such a chipset, and asked Broadcom for a list of all affected hardware releases, would the FCC also be told “who knows”? I guess the difference is that the FCC has the statutory authority to yank Broadcom’s certifications to sell their product, whereas Hector is merely improving your driver support for no monetary compensation from you. Maybe the Broadcom drivers should be yanked from Linux if this is what passes for Broadcom release engineering. zzy
On 1/3/2023 2:46 PM, Hector Martin wrote: > On 03/01/2023 22.30, Arend van Spriel wrote: >> On 1/3/2023 4:55 AM, Hector Martin wrote: >>> On 2023/01/03 3:27, Arend Van Spriel wrote: >>>> On January 2, 2023 4:15:41 PM Hector Martin <marcan@marcan.st> wrote: >>>> >>>>> On 02/01/2023 23.40, Aditya Garg wrote: >>>>>> From: Aditya Garg <gargaditya08@live.com> >>>>>> >>>>>> Commit 'dce45ded7619' added support for 89459 chip pcie device. It uses the >>>>>> BRCM4355 chip which is also found in Apple hardware. However this commit >>>>>> causes conflicts in the firmware naming between Apple hardware, which >>>>>> supports OTP and other non-Apple hardwares. So, this patch makes these >>>>>> Apple chips use their own firmware table so as to avoid possible conflicts >>>>>> like these in the future. >>>>> >>>>> I think my reply to Arend flew over your head. >>>>> >>>>> My point was that I'd rather have the Broadcom/Cypress people actually >>>>> answer my question so we can figure out how to do this *properly*, >>>>> instead of doing "safer-but-dumb" things (like this patch) because we >>>>> just don't have the information to do it properly. >>>> >>>> Fair enough. Can you accurately (re)state your question and I will try to >>>> answer it. >>> >>> As per my original email: Is the CYW89459 just a rebrand of the BCM4355, >>> or just a subset? Can we consider them equivalent, and equivalent to the >>> Apple part (BCM4355C1 / revision 12)? >> >> There is probably no easy answer. Mainly because Cypress is a separate >> entity. However, they use the same/similar technology and code base. So >> let me first start with the chip naming. The wifi chip primarily has a >> number and revision. The chip number is straighforward and can be read >> from the device. The chip revision comes in two variants: 1) simple >> increasing number as read from the device, and 2) a <letter><digit> >> format. The latter start at a0, which you almost never see in the wild >> unless we do it "first time right". Whenever spinning a new chip we >> either increase the digit or the letter depending on type/amount of >> changes. There is not predictable mapping between the revision variants. >> Depending on the hurdles in a chip project we may move from a0 to b0, or >> from b0 to b1 or whatever. > > Right, this is standard chip spin numbering, that much I know. > >> If CYW89459 chip reads chip number 0x4355 than it is a BCM4355. If it is >> a different revision it may require different firmware. A different >> letter will always require different firmware. A different digit may >> work although the firmware can have code paths for a specific revision. > > So is it always correct to have the same firmware (in a generic > situation, not a customized OEM build) for, say, a BCM4355 rev 12, > regardless of what the PCI ID programmed into the OTP is (and what the > marketing device name is)? Yes. > If so, then my conclusion is that the original patch I replied to is > incorrect, all the defines should've been called BCM4355 (not the > Cypress part number), and we probably need two firmware table entries > since (judging by the revision check elsewhere in that patch) there are > other revisions in the wild than the one Apple uses, and therefore there > should at the very least be a firmware name split at C1. It would then > be very helpful to know what revisions *do* exist and their correct naming. I can only track down what we have in Broadcom. For the 4355 the revisions B1 (=6), B3 (=8), C0 (=10) and C1 are mentioned as released. Here things get weird, because you mentioned BCM4355 rev12, which would be a C2. So without asking around I can only assume this C2 variant is not different from firmware perspective and can happily run the C1 firmware. > If different PCI device IDs might need different firmware, then the > exiting firmware selection/table mechanism is insufficient. > >> Happy New year to you. Thanks for clearly marking the rant. Makes it >> easier to ignore, but let me get into this. I would not call bcmdhd the >> downstream driver. It is a separate out-of-tree driver. Indeed resources >> were pulled from brcm80211 development, but there always have been only >> 2 or 3 people working on it. Me being the constant working mule and >> these days only for 20% of my working hours to do the job. So you are >> not really doing our job as we are not assigned to do so. I guess there >> is no ROI for Broadcom or so it is perceived and there is no customer >> pushing for it. That said I am always happy to help and clarify whatever >> I can. > > Is there any chance you can provide a list of chips/shipping revisions > and revision IDs, so we can stop guessing at the mappings in the > firmware table? Because this is effectively breaking userspace ABI every > time we make a change to an existing chip, as it can change the firmware > file name that userspace loads. This already happened with BCM4364, > where (at least) B2 and B3 revisions exist in the wild and we need > separate firmwares, yet it was added with a full mask, resulting in > people copying "the right firmware for them" manually and my patch to > split it into properly named firmwares will break those users. Userspace is not loading anything these days. AFAIK the kernel is directly accessing the firmware file. Anyway, I never considered this as being a big issue. If people change their installed os to get things working, they can expect the reverse can happen anytime and deal with it once more. If this is considered a real issue we should only set the revmask for the revision we know to be working. Regards, Arend
diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c index ae57a9a3a..ad7a780cd 100644 --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c @@ -92,10 +92,13 @@ static const struct brcmf_firmware_mapping brcmf_pcie_fwnames[] = { BRCMF_FW_ENTRY(BRCM_CC_43664_CHIP_ID, 0xFFFFFFF0, 4366C), BRCMF_FW_ENTRY(BRCM_CC_43666_CHIP_ID, 0xFFFFFFF0, 4366C), BRCMF_FW_ENTRY(BRCM_CC_4371_CHIP_ID, 0xFFFFFFFF, 4371), - BRCMF_FW_ENTRY(BRCM_CC_4378_CHIP_ID, 0xFFFFFFFF, 4378B1), /* revision ID 3 */ BRCMF_FW_ENTRY(CY_CC_89459_CHIP_ID, 0xFFFFFFFF, 4355), }; +static const struct brcmf_firmware_mapping brcmf_pcie_otp_fwnames[] = { + BRCMF_FW_ENTRY(BRCM_CC_4378_CHIP_ID, 0xFFFFFFFF, 4378B1), /* revision ID 3 */ +}; + #define BRCMF_PCIE_FW_UP_TIMEOUT 5000 /* msec */ #define BRCMF_PCIE_REG_MAP_SIZE (32 * 1024) @@ -2165,10 +2168,16 @@ brcmf_pcie_prepare_fw_request(struct brcmf_pciedev_info *devinfo) { ".clm_blob", devinfo->clm_name }, }; - fwreq = brcmf_fw_alloc_request(devinfo->ci->chip, devinfo->ci->chiprev, - brcmf_pcie_fwnames, - ARRAY_SIZE(brcmf_pcie_fwnames), - fwnames, ARRAY_SIZE(fwnames)); + if (devinfo->otp.valid) + fwreq = brcmf_fw_alloc_request(devinfo->ci->chip, devinfo->ci->chiprev, + brcmf_pcie_otp_fwnames, + ARRAY_SIZE(brcmf_pcie_otp_fwnames), + fwnames, ARRAY_SIZE(fwnames)); + else + fwreq = brcmf_fw_alloc_request(devinfo->ci->chip, devinfo->ci->chiprev, + brcmf_pcie_fwnames, + ARRAY_SIZE(brcmf_pcie_fwnames), + fwnames, ARRAY_SIZE(fwnames)); if (!fwreq) return NULL;