All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen-Yu Tsai <wens@csie.org>
To: Paul Kocialkowski <contact@paulk.fr>
Cc: devicetree <devicetree@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Maxime Ripard <mripard@kernel.org>,
	Jernej Skrabec <jernej.skrabec@siol.net>
Subject: Re: [PATCH] ARM: dts: sun8i-v3s: Add CSI0 MCLK pin definition
Date: Mon, 18 Jan 2021 14:25:42 +0800	[thread overview]
Message-ID: <CAGb2v67HY=EFX6-5NmXz0+02FOZkAa1r+AUy9QGeTEZBOcdJMw@mail.gmail.com> (raw)
In-Reply-To: <CAGb2v64xtm5wBuL6bkAYYFK2irjxs58df_xeHws6vaG_QDux+g@mail.gmail.com>

On Wed, Dec 30, 2020 at 11:29 AM Chen-Yu Tsai <wens@csie.org> wrote:
>
> On Tue, Dec 22, 2020 at 4:17 PM Jernej Škrabec <jernej.skrabec@siol.net> wrote:
> >
> > Hi!
> >
> > Dne petek, 18. december 2020 ob 20:50:33 CET je Paul Kocialkowski napisal(a):
> > > This adds a device-tree definition for the CSI0 MCLK pin,
> > > which can be used for feeding MIPI CSI-2 sensors.
> > >
> > > Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
> >
> > Is this used anywhere? Current policy is to add pin definitions only if any
> > user exists.
>
> IIRC we sort of loosened that requirement with the use of /omit-if-no-ref/.
> The A20 dtsi file has a whole bunch of pins defined that are not directly
> used but are available for users to reference, especially in overlays.
> The "-@" parameter for the device tree compiler, used to build overlay
> compatible DTBs, makes the compiler ignore /omit-if-no-ref/ and include
> all the nodes.

I've queued up this patch for 5.12.

ChenYu

WARNING: multiple messages have this Message-ID (diff)
From: Chen-Yu Tsai <wens@csie.org>
To: Paul Kocialkowski <contact@paulk.fr>
Cc: Maxime Ripard <mripard@kernel.org>,
	devicetree <devicetree@vger.kernel.org>,
	Jernej Skrabec <jernej.skrabec@siol.net>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: dts: sun8i-v3s: Add CSI0 MCLK pin definition
Date: Mon, 18 Jan 2021 14:25:42 +0800	[thread overview]
Message-ID: <CAGb2v67HY=EFX6-5NmXz0+02FOZkAa1r+AUy9QGeTEZBOcdJMw@mail.gmail.com> (raw)
In-Reply-To: <CAGb2v64xtm5wBuL6bkAYYFK2irjxs58df_xeHws6vaG_QDux+g@mail.gmail.com>

On Wed, Dec 30, 2020 at 11:29 AM Chen-Yu Tsai <wens@csie.org> wrote:
>
> On Tue, Dec 22, 2020 at 4:17 PM Jernej Škrabec <jernej.skrabec@siol.net> wrote:
> >
> > Hi!
> >
> > Dne petek, 18. december 2020 ob 20:50:33 CET je Paul Kocialkowski napisal(a):
> > > This adds a device-tree definition for the CSI0 MCLK pin,
> > > which can be used for feeding MIPI CSI-2 sensors.
> > >
> > > Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
> >
> > Is this used anywhere? Current policy is to add pin definitions only if any
> > user exists.
>
> IIRC we sort of loosened that requirement with the use of /omit-if-no-ref/.
> The A20 dtsi file has a whole bunch of pins defined that are not directly
> used but are available for users to reference, especially in overlays.
> The "-@" parameter for the device tree compiler, used to build overlay
> compatible DTBs, makes the compiler ignore /omit-if-no-ref/ and include
> all the nodes.

I've queued up this patch for 5.12.

ChenYu

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

  reply	other threads:[~2021-01-18  6:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-18 19:50 [PATCH] ARM: dts: sun8i-v3s: Add CSI0 MCLK pin definition Paul Kocialkowski
2020-12-18 19:50 ` Paul Kocialkowski
2020-12-22  8:17 ` Jernej Škrabec
2020-12-22  8:17   ` Jernej Škrabec
2020-12-24  9:21   ` Paul Kocialkowski
2020-12-24  9:21     ` Paul Kocialkowski
2020-12-30  3:29   ` Chen-Yu Tsai
2020-12-30  3:29     ` Chen-Yu Tsai
2021-01-18  6:25     ` Chen-Yu Tsai [this message]
2021-01-18  6:25       ` Chen-Yu Tsai

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='CAGb2v67HY=EFX6-5NmXz0+02FOZkAa1r+AUy9QGeTEZBOcdJMw@mail.gmail.com' \
    --to=wens@csie.org \
    --cc=contact@paulk.fr \
    --cc=devicetree@vger.kernel.org \
    --cc=jernej.skrabec@siol.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mripard@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 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.