mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: sbranden@broadcom.com, rjui@broadcom.com, f.fainelli@gmail.com,
	nsaenzjulienne@suse.de,
	Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: linux-rpi-kernel@lists.infradead.org, linux-spi@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	bcm-kernel-feedback-list@broadcom.com,
	linux-arm-kernel@lists.infradead.org,
	patches@opensource.cirrus.com
Subject: Re: [PATCH] spi: bcm2835: Set controller max_speed_hz
Date: Wed, 13 Jan 2021 17:54:26 +0000	[thread overview]
Message-ID: <161056046630.11960.4692892345837780609.b4-ty@kernel.org> (raw)
In-Reply-To: <20210107164825.21919-1-rf@opensource.cirrus.com>

On Thu, 7 Jan 2021 16:48:25 +0000, Richard Fitzgerald wrote:
> Set the struct spi_controller max_speed_hz. This is based on the
> reported source clock frequency during probe. The maximum bus clock
> is half the source clock (as per the code in bcm2835_spi_transfer_one).
> 
> If the controller max_speed_hz is not set, the spi core will limit all
> transfers to 0 Hz so only the minimum possible bus frequency would be used.

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: bcm2835: Set controller max_speed_hz
      commit: c6892892a95debac8050579b0709214b7b28b514

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark

      parent reply	other threads:[~2021-01-13 17:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07 16:48 Richard Fitzgerald
2021-01-07 16:58 ` Mark Brown
2021-01-13 17:54 ` Mark Brown [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=161056046630.11960.4692892345837780609.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=nsaenzjulienne@suse.de \
    --cc=patches@opensource.cirrus.com \
    --cc=rf@opensource.cirrus.com \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.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

all inboxes | Powered by JetHome®