All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Patrice Chotard <patrice.chotard@foss.st.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Liang He <windhl@126.com>, Wan Jiabing <wanjiabing@vivo.com>,
	Hugues Fruchet <hugues.fruchet@st.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: c8sectpfe: switch to using gpiod API
Date: Fri, 10 Mar 2023 18:52:54 +0200	[thread overview]
Message-ID: <ZAtgZppUrfBBs2Mu@smile.fi.intel.com> (raw)
In-Reply-To: <Y92VLGLQJZ/UDRx1@google.com>

On Fri, Feb 03, 2023 at 03:13:48PM -0800, Dmitry Torokhov wrote:
> This switches the driver from using legacy gpio API and to the newer
> gpiod API. Since ordinary gpiod APIs operate on logical and not
> electrical levels, handling of the reset GPIO is adjusted accordingly.

Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

This is an important patch for the further cleanups in the GPIO subsystem.
Can we have this applied, please?

-- 
With Best Regards,
Andy Shevchenko



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Patrice Chotard <patrice.chotard@foss.st.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Liang He <windhl@126.com>, Wan Jiabing <wanjiabing@vivo.com>,
	Hugues Fruchet <hugues.fruchet@st.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: c8sectpfe: switch to using gpiod API
Date: Fri, 10 Mar 2023 18:52:54 +0200	[thread overview]
Message-ID: <ZAtgZppUrfBBs2Mu@smile.fi.intel.com> (raw)
In-Reply-To: <Y92VLGLQJZ/UDRx1@google.com>

On Fri, Feb 03, 2023 at 03:13:48PM -0800, Dmitry Torokhov wrote:
> This switches the driver from using legacy gpio API and to the newer
> gpiod API. Since ordinary gpiod APIs operate on logical and not
> electrical levels, handling of the reset GPIO is adjusted accordingly.

Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

This is an important patch for the further cleanups in the GPIO subsystem.
Can we have this applied, please?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-03-10 16:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 23:13 [PATCH] media: c8sectpfe: switch to using gpiod API Dmitry Torokhov
2023-02-03 23:13 ` Dmitry Torokhov
2023-03-10 16:52 ` Andy Shevchenko [this message]
2023-03-10 16:52   ` Andy Shevchenko

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=ZAtgZppUrfBBs2Mu@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hugues.fruchet@st.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=patrice.chotard@foss.st.com \
    --cc=wanjiabing@vivo.com \
    --cc=windhl@126.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.