From: Nishanth Menon <nm@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>, Tero Kristo <kristo@kernel.org>
Cc: Nishanth Menon <nm@ti.com>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>
Subject: Re: [RESEND PATCH] arm64: dts: ti: k3-am64-main: Add ADC nodes
Date: Thu, 18 Mar 2021 09:24:58 -0500 [thread overview]
Message-ID: <161607554267.23461.3716611573021877758.b4-ty@ti.com> (raw)
In-Reply-To: <20210318113443.20036-1-vigneshr@ti.com>
On Thu, 18 Mar 2021 17:04:43 +0530, Vignesh Raghavendra wrote:
> AM64 SoC has a single ADC IP with 8 channels. Add DT node for the same.
>
> Default usecase is to control ADC from non Linux core on the system on
> AM642 GP EVM, therefore mark the node as reserved in k3-am642-evm.dts
> file. ADC lines are not pinned out on AM642 SK board, therefore disable
> the node in k3-am642-sk.dts file.
Hi Vignesh Raghavendra,
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/1] arm64: dts: ti: k3-am64-main: Add ADC nodes
commit: fad4e18fe4dccacf68418da01e98c4b8fb590023
Thanks for rebasing and helping sequence. I have taken note that we
will be converting the binding to yaml in near future, so inline with
what we are doing now, accepting the patch.
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant 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.
[1] git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>, Tero Kristo <kristo@kernel.org>
Cc: Nishanth Menon <nm@ti.com>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>
Subject: Re: [RESEND PATCH] arm64: dts: ti: k3-am64-main: Add ADC nodes
Date: Thu, 18 Mar 2021 09:24:58 -0500 [thread overview]
Message-ID: <161607554267.23461.3716611573021877758.b4-ty@ti.com> (raw)
In-Reply-To: <20210318113443.20036-1-vigneshr@ti.com>
On Thu, 18 Mar 2021 17:04:43 +0530, Vignesh Raghavendra wrote:
> AM64 SoC has a single ADC IP with 8 channels. Add DT node for the same.
>
> Default usecase is to control ADC from non Linux core on the system on
> AM642 GP EVM, therefore mark the node as reserved in k3-am642-evm.dts
> file. ADC lines are not pinned out on AM642 SK board, therefore disable
> the node in k3-am642-sk.dts file.
Hi Vignesh Raghavendra,
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/1] arm64: dts: ti: k3-am64-main: Add ADC nodes
commit: fad4e18fe4dccacf68418da01e98c4b8fb590023
Thanks for rebasing and helping sequence. I have taken note that we
will be converting the binding to yaml in near future, so inline with
what we are doing now, accepting the patch.
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant 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.
[1] git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-18 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 11:34 [RESEND PATCH] arm64: dts: ti: k3-am64-main: Add ADC nodes Vignesh Raghavendra
2021-03-18 11:34 ` Vignesh Raghavendra
2021-03-18 14:24 ` Nishanth Menon [this message]
2021-03-18 14:24 ` Nishanth Menon
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=161607554267.23461.3716611573021877758.b4-ty@ti.com \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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.