All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Prathamesh Shete <pshete@nvidia.com>,
	linus.walleij@linaro.org, thierry.reding@gmail.com,
	jonathanh@nvidia.com, linux-gpio@vger.kernel.org,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: smangipudi@nvidia.com
Subject: Re: [PATCH 1/2] pinctrl: tegra: include lpdr pin properties
Date: Wed, 20 Oct 2021 02:00:07 +0300	[thread overview]
Message-ID: <742eef64-c607-451b-3a28-171c628a44d4@gmail.com> (raw)
In-Reply-To: <20211018121815.3017-1-pshete@nvidia.com>

18.10.2021 15:18, Prathamesh Shete пишет:
> From: Suresh Mangipudi <smangipudi@nvidia.com>
> 
> Update lpdr pin-property for supported pins.
> 
> lpdr property help disable most basic driver fingers
> leaving only minimal base driver finger.
> 
> Signed-off-by: Suresh Mangipudi <smangipudi@nvidia.com>
> Signed-off-by: Prathamesh Shete <pshete@nvidia.com>
> ---
>  drivers/pinctrl/tegra/pinctrl-tegra.h    |   2 +
>  drivers/pinctrl/tegra/pinctrl-tegra210.c | 330 ++++++++++++-----------
>  2 files changed, 168 insertions(+), 164 deletions(-)

The code of this driver was generated by [1]. Have you considered
updating the generator?

[1] https://github.com/NVIDIA/tegra-pinmux-scripts

      parent reply	other threads:[~2021-10-19 23:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 12:18 [PATCH 1/2] pinctrl: tegra: include lpdr pin properties Prathamesh Shete
2021-10-18 12:18 ` [PATCH 2/2] pinctrl: tegra: Add pinmux support for Tegra194 Prathamesh Shete
2021-10-24 21:25   ` Linus Walleij
2021-11-05 17:49   ` kernel test robot
2021-11-05 17:49     ` kernel test robot
2022-04-29  6:20     ` Krzysztof Kozlowski
2022-04-29  6:20       ` Krzysztof Kozlowski
2021-10-19 23:00 ` Dmitry Osipenko [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=742eef64-c607-451b-3a28-171c628a44d4@gmail.com \
    --to=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=pshete@nvidia.com \
    --cc=smangipudi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.