public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krishna Yarlagadda <kyarlagadda@nvidia.com>
To: <broonie@kernel.org>, <thierry.reding@gmail.com>,
	<jonathanh@nvidia.com>, <linux-spi@vger.kernel.org>,
	<linux-tegra@vger.kernel.org>, <ashishsingha@nvidia.com>
Cc: <skomatineni@nvidia.com>, <ldewangan@nvidia.com>,
	<robh+dt@kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	"Krishna Yarlagadda" <kyarlagadda@nvidia.com>
Subject: [PATCH 0/3] spi: tegra quad: Add Tegra Grace features
Date: Thu, 17 Mar 2022 06:50:03 +0530	[thread overview]
Message-ID: <20220317012006.15080-1-kyarlagadda@nvidia.com> (raw)

Add multiple chip selects and hardware wait state polling supported
by Tegra Grace.

Krishna Yarlagadda (3):
  spi: tegra210-quad: Multi-cs support
  spi: tegra210-quad: Add wait polling support
  spi: dt-bindings: Add wait state polling flag

 .../bindings/spi/nvidia,tegra210-quad.yaml    |  6 ++
 drivers/spi/spi-tegra210-quad.c               | 64 ++++++++++++++++++-
 2 files changed, 68 insertions(+), 2 deletions(-)

-- 
2.17.1


             reply	other threads:[~2022-03-17  1:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17  1:20 Krishna Yarlagadda [this message]
2022-03-17  1:20 ` [PATCH 1/3] spi: tegra210-quad: Multi-cs support Krishna Yarlagadda
2022-03-17 15:00   ` kernel test robot
2022-03-17  1:20 ` [PATCH 2/3] spi: tegra210-quad: Add wait polling support Krishna Yarlagadda
2022-03-17  8:54   ` Jon Hunter
2022-03-17  9:02     ` Krishna Yarlagadda
2022-03-17  9:44       ` Jon Hunter
2022-03-17 15:26         ` Jon Hunter
2022-03-17 18:00           ` Krishna Yarlagadda
2022-03-17 18:09             ` Mark Brown
2022-03-17  9:31   ` Jon Hunter
2022-03-17  1:20 ` [PATCH 3/3] spi: dt-bindings: Add wait state polling flag Krishna Yarlagadda
2022-03-17  8:42   ` Mikko Perttunen
2022-03-17  9:03     ` Krishna Yarlagadda
2022-03-23 20:13   ` Rob Herring

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=20220317012006.15080-1-kyarlagadda@nvidia.com \
    --to=kyarlagadda@nvidia.com \
    --cc=ashishsingha@nvidia.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=skomatineni@nvidia.com \
    --cc=thierry.reding@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