From: Christoph Hellwig <hch@infradead.org>
To: Deepak Ukey <deepak.ukey@microchip.com>
Cc: linux-scsi@vger.kernel.org,
Vasanthalakshmi.Tharmarajan@microchip.com,
Viswas.G@microchip.com, jinpu.wang@profitbricks.com,
martin.petersen@oracle.com, yuuzheng@google.com,
auradkar@google.com, vishakhavc@google.com, bjashnani@google.com,
radha@google.com, akshatzen@google.com
Subject: Re: [PATCH V5 2/2] pm80xx : Staggered spin up support.
Date: Mon, 3 Aug 2020 13:45:51 +0100 [thread overview]
Message-ID: <20200803124551.GA26520@infradead.org> (raw)
In-Reply-To: <20200803122923.6826-3-deepak.ukey@microchip.com>
On Mon, Aug 03, 2020 at 05:59:23PM +0530, Deepak Ukey wrote:
> From: Viswas G <Viswas.G@microchip.com>
>
> As a part of drive discovery, driver will initaite the drive spin up.
> If all drives do spin up together, it will result in large power
> consumption. To reduce the power consumption, driver provide an option
> to make a small group of drives (say 3 or 4 drives together) to do the
> spin up. The delay between two spin up group and no of drives to
> spin up (group) can be programmed by the customer in seeprom and
> driver will use it to control the spinup.
Isn't this something we should implement in libsas instead?
prev parent reply other threads:[~2020-08-03 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 12:29 [PATCH V5 0/2] pm80xx : Updates for the driver version 0.1.39 Deepak Ukey
2020-08-03 12:29 ` [PATCH V5 1/2] pm80xx : Support for get phy profile functionality Deepak Ukey
2020-08-03 12:33 ` Jinpu Wang
2020-08-03 15:30 ` kernel test robot
2020-08-03 12:29 ` [PATCH V5 2/2] pm80xx : Staggered spin up support Deepak Ukey
2020-08-03 12:45 ` Christoph Hellwig [this message]
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=20200803124551.GA26520@infradead.org \
--to=hch@infradead.org \
--cc=Vasanthalakshmi.Tharmarajan@microchip.com \
--cc=Viswas.G@microchip.com \
--cc=akshatzen@google.com \
--cc=auradkar@google.com \
--cc=bjashnani@google.com \
--cc=deepak.ukey@microchip.com \
--cc=jinpu.wang@profitbricks.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=radha@google.com \
--cc=vishakhavc@google.com \
--cc=yuuzheng@google.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