From: Colin Ian King <colin.king@canonical.com>
To: "Larry Finger" <Larry.Finger@lwfinger.net>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
linux-wireless@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bcma: fix incorrect update of BCMA_CORE_PCI_MDIO_DATA
Date: Thu, 22 Aug 2019 17:11:19 +0100 [thread overview]
Message-ID: <31258833-174f-080b-489e-85d3556bd1de@canonical.com> (raw)
In-Reply-To: <d3c16158-ef89-f5ee-2f67-4357c70e8fe9@lwfinger.net>
On 22/08/2019 17:03, Larry Finger wrote:
> On 8/22/19 8:35 AM, Colin King wrote:
>> From: Colin Ian King <colin.king@canonical.com>
>>
>> An earlier commit re-worked the setting of the bitmask and is now
>> assigning v with some bit flags rather than bitwise or-ing them
>> into v, consequently the earlier bit-settings of v are being lost.
>> Fix this by replacing an assignment with the bitwise or instead.
>>
>> Addresses-Coverity: ("Unused value")
>> Fixes: 2be25cac8402 ("bcma: add constants for PCI and use them")
>> Signed-off-by: Colin Ian King <colin.king@canonical.com>
>> ---
>> drivers/bcma/driver_pci.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/bcma/driver_pci.c b/drivers/bcma/driver_pci.c
>> index f499a469e66d..d219ee947c07 100644
>> --- a/drivers/bcma/driver_pci.c
>> +++ b/drivers/bcma/driver_pci.c
>> @@ -78,7 +78,7 @@ static u16 bcma_pcie_mdio_read(struct bcma_drv_pci
>> *pc, u16 device, u8 address)
>> v |= (address << BCMA_CORE_PCI_MDIODATA_REGADDR_SHF_OLD);
>> }
>> - v = BCMA_CORE_PCI_MDIODATA_START;
>> + v |= BCMA_CORE_PCI_MDIODATA_START;
>> v |= BCMA_CORE_PCI_MDIODATA_READ;
>> v |= BCMA_CORE_PCI_MDIODATA_TA;
>
> I'm not sure the "Fixes" attribute is correct.
>
> The changes for this section in commit 2be25cac8402 are
>
> - v = (1 << 30); /* Start of Transaction */
> - v |= (1 << 28); /* Write Transaction */
> - v |= (1 << 17); /* Turnaround */
> - v |= (0x1F << 18);
> + v = BCMA_CORE_PCI_MDIODATA_START;
> + v |= BCMA_CORE_PCI_MDIODATA_WRITE;
> + v |= (BCMA_CORE_PCI_MDIODATA_DEV_ADDR <<
> + BCMA_CORE_PCI_MDIODATA_DEVADDR_SHF);
> + v |= (BCMA_CORE_PCI_MDIODATA_BLK_ADDR <<
> + BCMA_CORE_PCI_MDIODATA_REGADDR_SHF);
> + v |= BCMA_CORE_PCI_MDIODATA_TA;
>
> Because the code has done quite a bit of work on v just above this
> section, I agree that this is likely an error, but that error happened
> in an earlier commit. Thus 2be25cac8402 did not introduce the error,
> merely copied it.
Ugh, this goes back further. I didn't spot that. I'm less confident of
what the correct settings should be now.
>
> Has this change been tested?
Afraid not, I don't have the H/W.
>
> Larry
next prev parent reply other threads:[~2019-08-22 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 13:35 [PATCH] bcma: fix incorrect update of BCMA_CORE_PCI_MDIO_DATA Colin King
2019-08-22 16:03 ` Larry Finger
2019-08-22 16:11 ` Colin Ian King [this message]
2019-08-22 16:38 ` Larry Finger
2019-08-27 7:58 ` Colin Ian King
2019-08-25 19:59 ` Rafał Miłecki
2019-08-22 16:55 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=31258833-174f-080b-489e-85d3556bd1de@canonical.com \
--to=colin.king@canonical.com \
--cc=Larry.Finger@lwfinger.net \
--cc=hauke@hauke-m.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).