linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ynezz@true.cz (Petr Štetiar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: dts: imx6: Add support for Toradex Apalis SoM
Date: Sat, 28 Nov 2015 20:47:19 +0100	[thread overview]
Message-ID: <20151128194719.GO19674@ibawizard.net> (raw)
In-Reply-To: <ecfde8366160cb17f7b1e571f81488de@agner.ch>

Stefan Agner <stefan@agner.ch> [2015-11-27 11:38:44]:

> >> + * Copyright 2014-2015 Toradex AG
> >> + * Copyright 2012 Freescale Semiconductor, Inc.
> >> + * Copyright 2011 Linaro Ltd.
> >> + *
> >> + * 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
> 
> New device trees typically come with a dual license, X11/GPL. It makes
> sense that we use that too, Toradex agrees...

IANAL, but shouldn't we get some form of relicensing agreement from FSL and
Linaro also?

> >> +	clocks {
> >> +		clk24m: clk24m {
> >> +			compatible = "fixed-clock";
> >> +			#clock-cells = <0>;
> >> +			clock-frequency = <24000000>;
> >> +		};
> >> +	};
> 
> There is a 24Mhz osc defined in imx6qdl.dtsi, but I think that is the
> internal osc? I am not entierly familar with the i.MX6 clocks...
> 
> However, this seems not to be used anywhere and other boards also do not
> define that clock, hence I would drop it.

Ok, I'll try to drop it and will see if everything still works.

> > Were v1.0 modules sold to customers? If not the value of having those
> > supported by mainline is really limited.
> 
> I am inclined to say lets not support them. They anyway lead to
> headaches since you need to use a different U-Boot binary too...
> 
> Petr, do you happen to have one of them?

I've simply dropped support for v1.0 modules in patch v2. I've v1.1 module.

> Can we set fsl,dte-mode to false?

Ok, I'll remove that property.

-- ynezz

  reply	other threads:[~2015-11-28 19:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19 12:24 [PATCH 0/2] ARM: dts: imx6: Add support for Toradex Apalis SoM/Ixora Petr Štetiar
2015-11-19 12:24 ` [PATCH 1/2] ARM: dts: imx6: Add support for Toradex Apalis SoM Petr Štetiar
2015-11-19 14:12   ` Lucas Stach
2015-11-19 16:59     ` Joshua Clayton
2015-11-19 17:03       ` Fabio Estevam
2015-11-20 10:40       ` Petr Štetiar
2015-11-20 17:09         ` Joshua Clayton
2015-11-26 10:17     ` Petr Štetiar
2015-11-27 20:02       ` Stefan Agner
2015-11-28 19:38         ` Petr Štetiar
2015-11-27 19:38     ` Stefan Agner
2015-11-28 19:47       ` Petr Štetiar [this message]
2015-11-30 10:16       ` Lucas Stach
2015-11-19 12:25 ` [PATCH 2/2] ARM: dts: imx6: Add support for Toradex Apalis Ixora board Petr Štetiar

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=20151128194719.GO19674@ibawizard.net \
    --to=ynezz@true.cz \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).