mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: Daniel Schultz <d.schultz@phytec.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH 3/3] arm: dts: Added ocotp support for i.MX6UL
Date: Wed, 30 Nov 2016 08:38:17 -0800	[thread overview]
Message-ID: <CAHQ1cqFWQo4E=NsxMxeFTvYWbimHx8+5UF5z=gZjP5SAHk=0dg@mail.gmail.com> (raw)
In-Reply-To: <1480504245-1822-3-git-send-email-d.schultz@phytec.de>

On Wed, Nov 30, 2016 at 3:10 AM, Daniel Schultz <d.schultz@phytec.de> wrote:
> Ocotp is available for the iMX6(q|sx|sl) SoCs. This patch will extend the
> iMX6ul DT from the mainline kernel to support the ocotp driver on the
> iMX6ul SoC.
>
> Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
> ---
>  arch/arm/dts/imx6ul-phytec-phycore-som.dts |  1 +
>  arch/arm/dts/imx6ul.dtsi                   | 20 ++++++++++++++++++++
>  2 files changed, 21 insertions(+)
>  create mode 100644 arch/arm/dts/imx6ul.dtsi
>
> diff --git a/arch/arm/dts/imx6ul-phytec-phycore-som.dts b/arch/arm/dts/imx6ul-phytec-phycore-som.dts
> index be4556a..285ea62 100644
> --- a/arch/arm/dts/imx6ul-phytec-phycore-som.dts
> +++ b/arch/arm/dts/imx6ul-phytec-phycore-som.dts
> @@ -13,6 +13,7 @@
>  /dts-v1/;
>
>  #include <arm/imx6ul.dtsi>
> +#include "imx6ul.dtsi"
>
>  / {
>         model = "Phytec phyCORE-i.MX6 Ultra Lite SOM";
> diff --git a/arch/arm/dts/imx6ul.dtsi b/arch/arm/dts/imx6ul.dtsi
> new file mode 100644
> index 0000000..2e02d27
> --- /dev/null
> +++ b/arch/arm/dts/imx6ul.dtsi
> @@ -0,0 +1,20 @@
> +/*
> + * Copyright (C) 2016 PHYTEC Messtechnik GmbH
> + * Author: Daniel Schultz <d.schultz@phytec.de>
> + *
> + * The code contained herein is licensed under the GNU General Public
> + * License. You may obtain a copy of the GNU General Public License
> + * Version 2 or later at the following locations:
> + *
> + * http://www.opensource.org/licenses/gpl-license.html
> + * http://www.gnu.org/copyleft/gpl.html
> + */
> +
> +&aips2 {
> +       ocotp: ocotp-ctrl@21bc000 {
> +               compatible = "fsl,imx6ul-ocotp";
> +               reg = <0x021bc000 0x4000>;
> +               clocks = <&clks IMX6UL_CLK_OCOTP>;

Just as my two cents, I'd say that all of the above (that is
instantiation of OCOT on AIPS2) should go via Linux kernel and trickle
down via syncing with its .dts tree (<arm/imx6ul.dtsi> in particular).
At least that's what I had to do for OCOTP in Vybrid. Although your
case might be more complicated since there are no bindings for
"fsl,imx6ul-ocotp" upstream, so take this with a grain of salt

Cheers,
Andrey

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2016-11-30 16:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 11:10 [PATCH 1/3] arm: imx6: ocotp: Added support for the i.MX6UL Daniel Schultz
2016-11-30 11:10 ` [PATCH 2/3] arm: imx6: ocotp: Added write check Daniel Schultz
2016-11-30 11:10 ` [PATCH 3/3] arm: dts: Added ocotp support for i.MX6UL Daniel Schultz
2016-11-30 16:38   ` Andrey Smirnov [this message]
2016-12-08  9:32     ` Daniel Schultz

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='CAHQ1cqFWQo4E=NsxMxeFTvYWbimHx8+5UF5z=gZjP5SAHk=0dg@mail.gmail.com' \
    --to=andrew.smirnov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=d.schultz@phytec.de \
    /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