public inbox for linux-integrity@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Lino Sanfilippo <LinoSanfilippo@gmx.de>,
	rjui@broadcom.com, sbranden@broadcom.com,
	bcm-kernel-feedback-list@broadcom.com, nsaenz@kernel.org,
	linux-spi@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, p.rosenberger@kunbus.com,
	linux-integrity@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] spi: bcm2835: do not unregister controller in shutdown handler
Date: Mon, 4 Oct 2021 18:05:26 +0100	[thread overview]
Message-ID: <YVs0Vk9TJqHt8R4K@sirena.org.uk> (raw)
In-Reply-To: <20211004165127.GZ3544071@ziepe.ca>

[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]

On Mon, Oct 04, 2021 at 01:51:27PM -0300, Jason Gunthorpe wrote:
> On Mon, Oct 04, 2021 at 09:36:37AM -0700, Florian Fainelli wrote:

> > No please don't, I should have arguably justified the reasons why
> > better, but the main reason is that one of the platforms on which this
> > driver is used has received extensive power management analysis and
> > changes, and shutting down every bit of hardware, including something as
> > small as a SPI controller, and its clock (and its PLL) helped meet
> > stringent power targets.

> Huh? for device shutdown? What would this matter if the next step is
> reboot or power off?

On some embedded systems, especially ultra low cost ones, the system
power off state might not actually involve removing all the physical
power supplies for the all the chips in the system so any residual
leakages or active functions will continue to consume power.

Ideally the system power on/off will be triggered by a PMIC which is
able to physically remove power to most other parts of the system which
avoids this issue (much like the PSU in a server) but that's not always
the case.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2021-10-04 17:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 19:56 [PATCH] spi: bcm2835: do not unregister controller in shutdown handler Lino Sanfilippo
2021-09-28 20:08 ` Mark Brown
2021-09-29  8:38   ` Aw: " Lino Sanfilippo
2021-10-01 17:54 ` Mark Brown
2021-10-03 15:25   ` Lino Sanfilippo
2021-10-04 12:49     ` Mark Brown
2021-10-04 13:17       ` Jason Gunthorpe
2021-10-04 14:12         ` Mark Brown
2021-10-04 15:44           ` Jason Gunthorpe
2021-10-04 16:31             ` Mark Brown
2021-10-04 16:36               ` Florian Fainelli
2021-10-04 16:51                 ` Jason Gunthorpe
2021-10-04 16:55                   ` Florian Fainelli
2021-10-04 17:13                     ` Jason Gunthorpe
2021-10-04 17:27                       ` Mark Brown
2021-10-04 17:35                         ` Jason Gunthorpe
2021-10-04 17:44                         ` Florian Fainelli
2021-10-04 17:56                           ` Mark Brown
2021-10-04 17:05                   ` Mark Brown [this message]
2021-10-04 16:52                 ` Mark Brown
2021-10-04 16:57                   ` Florian Fainelli
2021-10-04 18:30             ` Lino Sanfilippo
2021-10-04 18:37               ` Jason Gunthorpe

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=YVs0Vk9TJqHt8R4K@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=LinoSanfilippo@gmx.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=nsaenz@kernel.org \
    --cc=p.rosenberger@kunbus.com \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.com \
    --cc=stable@vger.kernel.org \
    /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