On Fri, 2021-12-10 at 09:05 +0000, Ajay.Kathat@xxxxxxxxxxxxx wrote:
> On 10/12/21 00:42, David Mosberger-Tang wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> >
> > On Thu, 2021-12-09 at 11:15 -0700, David Mosberger-Tang wrote:
> >
> > > > Did you test by enabling the power-save mode with "wpa_supplicant" or
> > > > using "iw" command. For power consumption measurement, please try by
> > > > disabling the PSM mode.
> > > No, I have not played with power-saving mode. There are some disconcerting
> > > messages when turning PSM on:
> > >
> > > [ 1764.070375] wilc1000_spi spi1.0: Failed cmd, cmd (ca), resp (00)
> > > [ 1764.076403] wilc1000_spi spi1.0: Failed cmd, read reg (000013f4)...
> > As far as I can see, chip_wakeup() can trigger this legitimately:
> >
> > do {
> > h->hif_read_reg(wilc, WILC_SPI_WAKEUP_REG, ®);
> > h->hif_write_reg(wilc, WILC_SPI_WAKEUP_REG,
> > reg | WILC_SPI_WAKEUP_BIT);
> > h->hif_write_reg(wilc, WILC_SPI_WAKEUP_REG,
> > reg & ~WILC_SPI_WAKEUP_BIT);
> >
> > do {
> > usleep_range(2000, 2500);
> > wilc_get_chipid(wilc, true);
> > } while (wilc_get_chipid(wilc, true) == 0);
> > } while (wilc_get_chipid(wilc, true) == 0);
> >
> > Actually, the above looks rather gross. wilc_get_chip() reads both WILC_CHIPID
> > and WILC_RF_REVISION_ID and we do this at least three times in a row on each
> > chip_wakeup(). Wow. Is this really necessary?
>
> I believe you are using the old driver code so please check with latest
> code. 'chip_wakeup()' was changed recently so I don't think
> 'wilc_get_chipid()' call is valid anymore inside this API.
>
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/microchip/wilc1000?h=v5.15&id=5bb9de8bcb18c38ea089a287b77944ef8ee71abd
Indeed I was. I switched to 5.15 recently but thought I had backported all
patches, but I was missing a handful. Yes, the new code is much better, thanks!
> > In any case, for now, the below supresses the error messages:
> >
> > diff --git a/drivers/net/wireless/microchip/wilc1000/spi.c b/drivers/net/wireless/microchip/wilc1000/spi.c
> > index b778284247f7..516787aa4a23 100644
> > --- a/drivers/net/wireless/microchip/wilc1000/spi.c
> > +++ b/drivers/net/wireless/microchip/wilc1000/spi.c
> > @@ -498,7 +498,7 @@ static int wilc_spi_single_read(struct wilc *wilc, u8 cmd, u32 adr, void *b,
> > r = (struct wilc_spi_rsp_data *)&rb[cmd_len];
> > if (r->rsp_cmd_type != cmd) {
> > if (!spi_priv->probing_crc)
> > - dev_err(&spi->dev,
> > + dev_dbg(&spi->dev,
> > "Failed cmd, cmd (%02x), resp (%02x)\n",
> > cmd, r->rsp_cmd_type);
> > return -EINVAL;
> > @@ -754,7 +754,8 @@ static int wilc_spi_read_reg(struct wilc *wilc, u32 addr, u32 *data)
> >
> > result = wilc_spi_single_read(wilc, cmd, addr, data, clockless);
> > if (result) {
> > - dev_err(&spi->dev, "Failed cmd, read reg (%08x)...\n", addr);
> > + /* Register reads may fail legitimately, e.g., during chip_wakeup(). */
> > + dev_dbg(&spi->dev, "Failed cmd, read reg (%08x)...\n", addr);
> > return result;
> > }
> >
> >
> > Maybe a parameter should be added to hif_read_reg() to indicate whether failure is an option?
>
> I have not observed the failure log specifically during 'chip_wakeup'
> but if you see them often then we can add the information in comments.
My tree was missing the clockless register fixes as well so perhaps that's what
caused these. It seems to be good now.
This is actually starting to look quite good! Here is the current iperf3
throughput I'm getting:
PSM off:
[ 4] 0.00-120.00 sec 137 MBytes 9.60 Mbits/sec 7 sender
[ 5] 0.00-120.03 sec 281 MBytes 19.6 Mbits/sec receiver
PSM on:
[ 4] 0.00-120.01 sec 140 MBytes 9.82 Mbits/sec 9 sender
[ 5] 0.00-120.69 sec 283 MBytes 19.6 Mbits/sec receiver
I'll submit a patch to skip wakeup/allow_sleep if power-save mode is off.
The only remaining issue I'm seeing is that if I turn on power-save mode right
after starting wpa_supplicant, the driver thinks that PSM is on, but power
consumption indicates that it is not actually on (using about 1.5W of power).
When it's in this state, I have to manually use iw to turn PSM off and then on
again to get actual power-savings (power dropping to about 1.1W).
--david
