On 03/17/2014 01:37 PM, Rob Herring wrote:
On Mon, Mar 17, 2014 at 9:30 AM, Nishanth Menon n...@ti.com wrote:
On 03/14/2014 04:00 PM, Rob Herring wrote:
On Fri, Mar 14, 2014 at 2:25 PM, Dave Gerlach d-gerl...@ti.com wrote:
Driver to read from a register and depending on either set bits
,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
.
There is as well a option (d) where we wait for FDT overlay to mature,
write up a resource manager and support all level capes.
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
= 0x0030 0x0070;
+ };
+ partition@9 {
+ label = NAND.file-system;
+ reg = 0x00A0 0x1F60;
+ };
+ };
+};
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux
0x1F60;
+ };
+ };
+};
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
has.I dont see asking folks to
uncomment entries to use the cape is a nicer alternative to having
more dts entries.
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
On 03/12/2014 02:28 PM, Tony Lindgren wrote:
* Robert Nelson robertcnel...@gmail.com [140312 12:11]:
On Wed, Mar 12, 2014 at 1:57 PM, Nishanth Menon n...@ti.com wrote:
On Wed, Mar 12, 2014 at 1:26 PM, Gupta, Pekon pe...@ti.com wrote:
Hi,
From: Menon, Nishanth
On 03/12/2014 05:49 AM, Pekon
'
Fixes: c962184 (ARM: OMAP4: PM: add errata support)
Reported-by: Tony Lindgren t...@atomide.com
Signed-off-by: Nishanth Menon n...@ti.com
---
Patch based on: v3.14-rc6
Reported originally with a randconfig defconfig:
http://slexy.org/view/s21U7eF4k1
arch/arm/mach-omap2/pm.h |2 +-
1 file
;
+ };
+ };
+};
--
1.7.9.5
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 03/12/2014 04:59 PM, Santosh Shilimkar wrote:
On Thursday 13 March 2014 05:43 AM, Nishanth Menon wrote:
Just like IS_PM34XX_ERRATUM, IS_PM44XX_ERRATUM is valid only if
CONFIG_PM is enabled, else, disabling CONFIG_PM results in build
failure complaining about the following:
arch/arm/mach
On 03/10/2014 12:22 PM, Mark Brown wrote:
On Mon, Mar 10, 2014 at 12:11:44PM -0500, Nishanth Menon wrote:
On 03/02/2014 09:54 PM, Mark Brown wrote:
On Mon, Feb 24, 2014 at 08:38:07AM -0600, Nishanth Menon wrote:
Intent here is to allow drivers such as cpufreq-cpu0 to be reused on
platforms
On 03/10/2014 01:01 PM, Mark Brown wrote:
On Mon, Mar 10, 2014 at 12:41:05PM -0500, Nishanth Menon wrote:
The only other options are:
a) Abstract it at a higher level at user drivers, since they are
aware of the sequencing needs - but this partially defeats the
purpose, unless ofcourse, we
On 02/28/2014 01:39 AM, Peter Ujfalusi wrote:
On 02/27/2014 05:00 PM, Nishanth Menon wrote:
The other option might be to blindly configure 6040 to max speed -
but then you do have an issue with that single register write
operation to configure the speed?
Yes, exactly. It is unfortunate
On 02/28/2014 08:26 AM, Peter Ujfalusi wrote:
On 02/28/2014 03:30 PM, Nishanth Menon wrote:
TWL6030 can do 3.3MHz by default and there are no speed registers to
configure.
According to the datasheet the speed of twl6030 is limited to 2.4MHz. I have
not seen registers or pins to select
On 02/14/2014 10:31 AM, Tony Lindgren wrote:
* Nishanth Menon n...@ti.com [140213 21:48]:
When device is booted using devicetree, platforms impacted by Erratum
2.1.1.128 is not detected easily in the mmc driver. This erratum
indicates that the module cannot do multi-block transfers. Platforms
look good other than the checkpatch violation noticed in
report, so other than that,
Tested-by: Nishanth Menon n...@ti.com
omap2plus_defconfig
1: am335x-evm: Boot PASS: http://slexy.org/raw/s2jdV3XMCC
2: am335x-sk: Boot PASS: http://slexy.org/raw/s210nZI8Hx
3: am3517-evm: Boot PASS: http
);
+ return;
+ }
+cleanup:
+ kfree(clk_hw);
+ kfree(init);
kfree(ad)?
smatch reported (as part of the kernel_patch_verify_report:
+drivers/clk/ti/apll.c:400 of_omap2_apll_setup() warn: possible memory
leak of 'ad'
--
Regards,
Nishanth Menon
--
To unsubscribe from this list
.
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
speed within TWL6040 -
considering that 6040 can infact do max high speed as well?
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
On 02/26/2014 11:00 PM, Mike Turquette wrote:
Quoting Nishanth Menon (2014-02-26 18:34:55)
+/**
+ * pm_runtime_get_rate() - Returns the device operational frequency
+ * @dev: Device to handle
+ * @rate: Returns rate in Hz.
+ *
+ * Returns appropriate error value in case of error
On 02/27/2014 08:33 AM, Peter Ujfalusi wrote:
On 02/27/2014 04:24 PM, Nishanth Menon wrote:
we should ideally have been using highspeed for i2c bus.
is'nt it better if i2c_check_functionality (and adding required flags
for func) be used to check the adapter speed and decide
this yet, should we
consider adding ti,system-power-controller(as against removing
ti,use_poweroff - so that older down stream dtbs still work) and using
it in the new code?
just proposing here.
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap
+devicetree list.
On 02/27/2014 02:48 PM, Florian Vaussard wrote:
On 02/27/2014 09:38 PM, Nishanth Menon wrote:
On 02/27/2014 02:30 PM, Florian Vaussard wrote:
Currently, the TWL4030 PMIC does not completely poweroff the processor.
Commit b0fc1da4d0359d3cce8f12e0f014aed0704ae202 introduced
On 14:56-20140225, Nishanth Menon wrote:
On 02/24/2014 11:51 PM, Mike Turquette wrote:
Quoting Nishanth Menon (2014-02-18 12:32:18)
[...]
I'm not sure about trying to capture the voltdm as a core concept. It
feels a bit unwieldy to me.
Considering it is a simple collation of regulators
Hi Mike,
On 02/24/2014 11:51 PM, Mike Turquette wrote:
Quoting Nishanth Menon (2014-02-18 12:32:18)
From: Mike Turquette mturque...@linaro.org
This patch provides helper functions for drivers that wish to scale
voltage through the clock rate-change notifiers. The approach taken
On 02/23/2014 07:58 PM, Mark Brown wrote:
On Tue, Feb 18, 2014 at 02:32:20PM -0600, Nishanth Menon wrote:
The current regulator model provides the basic building blocks for the
transitions, however SoC drivers specific to each of these devices, be
it cpufreq/devfreq have to replicate
DSS: http://marc.info/?l=linux-omapm=139272358619064w=2
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 02/19/2014 08:58 PM, Paul Walmsley wrote:
On Wed, 19 Feb 2014, Nishanth Menon wrote:
Paul,
On 02/19/2014 03:22 PM, Paul Walmsley wrote:
[...]
-
Illia Smyrnov (1):
ARM: OMAP4: hwmod: Fix SOFTRESET logic for OMAP4
On 01/29/2014 05:46 PM, Nishanth Menon wrote:
From: Andrii.Tseglytskyi andrii.tseglyts...@ti.com
Add ABB device nodes for OMAP5 family of devices. Data is based on
OMAP543x Technical Reference Manual revision U (April 2013).
NOTE: clock node has been disabled in this patch due to the lack
Valkeinen (1):
ARM: OMAP2+: clock: fix clkoutx2 with CLK_SET_RATE_PARENT
Vaibhav Bedia (1):
ARM: OMAP5: PRM: Fix reboot handling
https://patchwork.kernel.org/patch/3585321/ missing?
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap
(Class0) can also be introduced based on this basic
framework.
This now allows reuse by voltage domain devices which may share the same
voltage domain by allowing the regulator framework to maintain per
consumer usage information.
Signed-off-by: Nishanth Menon n...@ti.com
---
drivers/power/voltdm
.
[n...@ti.com: updates to keep the OPP logic still in cpufreq-cpu0 -
optimization to generalize that for cpufreq is to be done in a later
series]
Signed-off-by: Nishanth Menon n...@ti.com
Signed-off-by: Mike Turquette mturque...@linaro.org
---
drivers/cpufreq/Kconfig|1 +
drivers/cpufreq
-by: Nishanth Menon n...@ti.com
---
drivers/power/voltdm/Kconfig |5 +
drivers/power/voltdm/Makefile |3 +
drivers/power/voltdm/core.c | 347 +++--
drivers/power/voltdm/voltage_domain_private.h | 86 ++
4 files
Add documentation for voltage domain binding format. Specific
voltage domains will have bindings corresponding to them.
Signed-off-by: Nishanth Menon n...@ti.com
---
.../bindings/power/voltdm/voltage_domain.txt | 65
1 file changed, 65 insertions(+)
create mode
voltagedomain solution independent of cpufreq]
Signed-off-by: Nishanth Menon n...@ti.com
Signed-off-by: Mike Turquette mturque...@linaro.org
---
drivers/power/Kconfig |1 +
drivers/power/Makefile|1 +
drivers/power/voltdm/Kconfig |7 ++
drivers/power/voltdm/Makefile
Turquette (2):
PM / Voltagedomain: Add generic clk notifier handler for regulator
based dynamic voltage scaling
cpufreq: cpufreq-cpu0: use clk rate-change notifiers
Nishanth Menon (4):
PM / Voltagedomain: introduce voltage domain driver support
devicetree: bindings: add documentation
Add documentation for device tree description for basic voltage domain
for Texas Instruments OMAP compatible SoC family of processors which
controls both bias and supply voltage planes.
Signed-off-by: Nishanth Menon n...@ti.com
---
.../bindings/power/voltdm/voltdm_omap.txt | 24
On 02/14/2014 01:58 AM, Florian Vaussard wrote:
Hi,
On 02/13/2014 03:43 PM, Nishanth Menon wrote:
On 02/13/2014 04:25 AM, Florian Vaussard wrote:
Update the compatible string for Overo/Tobi to reflect the latest
changes.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
.
This will break older models. This will be addressed later.
Signed-off-by: Tony Lindgren t...@atomide.com
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Tested-by: Kevin Hilman khil...@linaro.org
Acked-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/omap3-overo.dtsi | 3
Vaussard florian.vauss...@epfl.ch
Tested-by: Kevin Hilman khil...@linaro.org
Acked-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/Makefile | 3 ++-
arch/arm/boot/dts/omap3-overo-storm-tobi.dts | 22
++
...omap3-tobi.dts = omap3-overo-tobi
On 02/13/2014 04:25 AM, Florian Vaussard wrote:
Gumstix is the correct vendor for all Overo related products.
Reported-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Acked-by: Nishanth Menon n...@ti.com
---
arch/arm
, so, I wonder as the
number of boards supported keep increasing, is'nt it better we drop
the board information from omap.txt?
- OMAP4 SDP : Software Development Board
compatible = ti,omap4-sdp, ti,omap4430
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line
() warn:
maybe use instead of
sparse reports:
drivers/mmc/host/omap_hsmmc.c: warning: dubious: !x y
Fix the same.
Signed-off-by: Nishanth Menon n...@ti.com
---
drivers/mmc/host/omap_hsmmc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mmc/host/omap_hsmmc.c b
compatible property ti,omap3-pre-es3-hsmmc to allow
driver to determine if driver needs to implement quirks associated
with the specific module version (primarily because the IP revision
information is not sufficient for the same).
Signed-off-by: Nishanth Menon n...@ti.com
---
Changes since v1
.
Signed-off-by: Nishanth Menon n...@ti.com
---
Changes since V1:
- fixed commit message as suggested by Balaji.
- update to use new compatible match for the erratum.
V1: https://patchwork.kernel.org/patch/3514881/
arch/arm/boot/dts/omap3-ldp.dts | 23 +++
1
Boards = 9, No Boot boards = 0
LDP platform prior to the series reports: http://slexy.org/raw/s20qVg17T0
Series is based on v3.14-rc2
Nishanth Menon (2):
mmc: omap_hsmmc: Add support for quirky omap3 hsmmc controller
ARM: dts: omap3-ldp: fix mmc configuration
.../devicetree/bindings/mmc/ti
On 02/13/2014 05:05 PM, Tony Lindgren wrote:
* Nishanth Menon n...@ti.com [140205 06:15]:
On Wed 05 Feb 2014 08:10:34 AM CST, Balaji T K wrote:
Rather than ti,errata.. specific property, something like
caps no/disable multiblock read is more readable in my opinion, Otherwise
Is'nt
On 02/10/2014 07:07 PM, Kevin Hilman wrote:
Nishanth Menon n...@ti.com writes:
On 02/10/2014 12:28 PM, Kevin Hilman wrote:
Roger Quadros rog...@ti.com writes:
+devicetree
On 02/10/2014 05:59 PM, Nishanth Menon wrote:
Hi,
A quick note to report that I saw regression in today's next tag
Reported-by: Nishanth Menon n...@ti.com
Signed-off-by: Roger Quadros rog...@ti.com
Please ignore this patch as Hans has agreed to do a more proper fix in
http://article.gmane.org/gmane.comp.hardware.netbook.arm.sunxi/7015
umm.. even then, drivers/usb/host/ehci-ppc-of.c claims compatibility
On 02/11/2014 08:35 AM, Hans de Goede wrote:
On 02/11/2014 03:17 PM, Nishanth Menon wrote:
On 02/11/2014 07:53 AM, Roger Quadros wrote:
On 02/10/2014 08:10 PM, Roger Quadros wrote:
The OMAP EHCI controller is not compatible with the EHCI
platform HCD driver so don't claim that we
-by: Nishanth Menon n...@ti.com
---
just build tested. but given examples such as
http://thread.gmane.org/gmane.linux.ports.arm.omap/110006
I guess, some form of failure is expected.
based on v3.14-rc2
arch/arm/boot/dts/omap3-n9.dts |2 +-
arch/arm/boot/dts/omap3-n900.dts |2 +-
arch/arm
Aaro,
On 02/11/2014 12:51 PM, Aaro Koskinen wrote:
Hi,
On Tue, Feb 11, 2014 at 09:29:01AM -0600, Nishanth Menon wrote:
Nokia N900 uses OMAP3430 and N9/N950 uses OMAP3630. Mark SoC compatibilty
as per Documentation/devicetree/bindings/arm/omap/omap.txt else
N9/N950 will be probed
On 02/09/2014 06:12 AM, Aaro Koskinen wrote:
N9/N950 does not boot anymore with 3.14-rc1, because SoC compatible
property is missing. Fix that.
Signed-off-by: Aaro Koskinen aaro.koski...@iki.fi
Reviewed-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/omap3-n9.dts | 2 +-
arch/arm
On 02/09/2014 06:12 AM, Aaro Koskinen wrote:
Add missing compatible property to avoid problems in the future.
Signed-off-by: Aaro Koskinen aaro.koski...@iki.fi
Reviewed-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/omap3-n900.dts | 4 ++--
1 file changed, 2 insertions(+), 2
,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
/s2kztuFoSu
TOTAL = 15 boards, Booted Boards = 13, No Boot boards = 2
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 02/10/2014 10:11 AM, Roger Quadros wrote:
On 02/10/2014 05:59 PM, Nishanth Menon wrote:
Hi,
A quick note to report that I saw regression in today's next tag (logs
indicate around EHCI) boot on various TI platforms:
Note: crane and sdp2430 are not expected to pass with
multi_v7_defconfig
boot. Note that omap2plus_defconfig boots fine on all these boards,
this failure is only for multi_v7_defconfig.
Not sure if anyone else has seen this yet.
yep - reported and being looked here:
http://marc.info/?t=13920480394r=1w=2
--
Regards,
Nishanth Menon
--
To unsubscribe from
are different - I was attempting to boot sdp2430
with nfs boot which seems to work fine for me, I believe you are
attempting mmc boot here.
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More
from the DT node of all failing
platforms.
If the driver is not compatible with usb-ehci, not sure why do we
even state that in dts node?
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
On 02/10/2014 12:28 PM, Kevin Hilman wrote:
Roger Quadros rog...@ti.com writes:
+devicetree
On 02/10/2014 05:59 PM, Nishanth Menon wrote:
Hi,
A quick note to report that I saw regression in today's next tag (logs
indicate around EHCI) boot on various TI platforms:
Note: crane
also probably want to make better explanation about this issue and
why we think this is the correct fix for it - for example, question
Kevin asked in [1]
This fixes boot on OMAP platforms with CONFIG_USB_EHCI_HCD_PLATFORM=y
e.g. multi_v7_defconfig
Reported-by: Nishanth Menon n...@ti.com
idea at this point in time - Further, we do have equivalent
requirements in other TI SoCs as well -
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
with v3.14-rc1
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
;
+};
+
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
or 3530 separately out in linux as of
today as they are nothing but a packaging difference for larger board
community - there should be no internal differences - the only
functional variation has been am3517 - which got it's own compatible
property.
--
Regards,
Nishanth Menon
--
To unsubscribe from
Select CONFIG_SOC_DRA7XX so that we can boot dra7-evm.
DRA7 family are A15 based processors that supports LPAE and an
evolutionary update to the OMAP5 generation of processors.
Signed-off-by: Nishanth Menon n...@ti.com
---
based on v3.13-rc1 kernel tag - tested on v3.14-rc1 and next-20140206
omap3_noncore_dpll_set_rate forces a reparent to the same clk_ref
for every call that takes place. This is an can be done only if a change
is detected.
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/mach-omap2/dpll3xxx.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
{
pinctrl-single,pins =
0x54 (PIN_OUTPUT_PULLDOWN | MUX_MODE7) /*
gpmc_a5.gpio1_21 */
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
On Wed 05 Feb 2014 08:10:34 AM CST, Balaji T K wrote:
On Tuesday 04 February 2014 08:48 PM, Nishanth Menon wrote:
On 02/04/2014 06:44 AM, Balaji T K wrote:
On Tuesday 21 January 2014 04:59 AM, Nishanth Menon wrote:
When device is booted using devicetree, platforms impacted by
Erratum
-dev, can't enable clock\n);
Though unrelated to specifically this, elm_resume has a get_sync
without error check..
Further, you might want to cc the mailing lists generated by
./scripts/get_maintainer.pl
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux
On 02/05/2014 08:38 AM, Matt Porter wrote:
On Wed, Feb 05, 2014 at 08:09:16AM -0600, Nishanth Menon wrote:
On 02/05/2014 07:48 AM, Jack Mitchell wrote:
[...]
+ * --- a/arch/arm/boot/dts/am335x-boneblack.dts
+ * +++ b/arch/arm/boot/dts/am335x-boneblack.dts
+ * @@ -73,6 +74,6
for a moment thought it was on newer kernels :).
Looping in Dan who is currently looking at reset driver replacement
for existing hwmod based reset solution.
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord
On 02/04/2014 06:44 AM, Balaji T K wrote:
On Tuesday 21 January 2014 04:59 AM, Nishanth Menon wrote:
When device is booted using devicetree, platforms impacted by
Erratum 2.1.1.128 is not detected easily in the mmc driver. This erratum
indicates that the module cannot do multi-block transfers
On 02/04/2014 06:46 AM, Balaji T K wrote:
On Tuesday 21 January 2014 05:04 AM, Nishanth Menon wrote:
MMC1 is the only MMC interface available on the platform. Further,
since the platform is based on older revision of SoC which is not
capable of doing multi-block writes, mark it so and add
: OMAP5432uEVM: Boot PASS: http://slexy.org/raw/s2QkMn2zTL
TOTAL = 15 boards, Booted Boards = 13, No Boot boards = 2
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
Hi Tony,
On 01/15/2014 02:00 PM, Nishanth Menon wrote:
OMAP5, DRA7, AM43xx all have OPPs. So select the same to allow SoC
only configuration boot to work with OPP.
Reported-by: Nikhil Devshatwar nikhil...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
For DRA7, depends on: https
On 01/20/2014 10:43 AM, Nishanth Menon wrote:
Benoit,
On 12/18/2013 11:16 AM, Benoit Cousson wrote:
On 18/12/2013 18:02, Nishanth Menon wrote:
On 12/18/2013 10:57 AM, Benoit Cousson wrote:
On 17/12/2013 20:45, Nishanth Menon wrote:
On 12/09/2013 03:55 PM, Nishanth Menon wrote:
Craneboard
, Touchscreen and WLAN driver changes haven't
made it into 3.14, so the patchset I mailed is complete.
-- Sebastian
It is usually suggested for dts patches to be cced with devicetree and
linux-arm-kernel lists as well..
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line
OMAP34xx, AM3517 and OMAP36xx platforms use dpll1 clock.
OMAP443x, OMAP446x, OMAP447x, OMAP5, DRA7, AM43xx platforms use
dpll_mpu clock.
Latency used is the generic latency defined in omap-cpufreq
driver.
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi |4
from
version 1 again considering that I have finally based on master.
If folks feel that the clock nodes must be split out into various platforms, I
can regenerate the series again.
Nishanth Menon (2):
clk: ti: am335x: remove unecessary cpu0 clk node
ARM: dts: OMAP3+: add clock nodes for CPU
cpu0 clock node has no functionality, since cpufreq-cpu0 is already
capable of picking up the clock from dts.
Signed-off-by: Nishanth Menon n...@ti.com
---
drivers/clk/ti/clk-33xx.c |1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/clk/ti/clk-33xx.c b/drivers/clk/ti/clk-33xx.c
index
debugfs output - example:
http://slexy.org/view/s21iQyDTct
I mean, it is awesome having to debugfs data, but with nascent
systems, it is always good to compare to what the hardware is really
configured to - and CTT is the easy way to deal with it.
--
Regards,
Nishanth Menon
--
To unsubscribe from
On 01/29/2014 01:29 PM, Robert Nelson wrote:
On Wed, Jan 29, 2014 at 12:19 PM, Nishanth Menon n...@ti.com wrote:
OMAP34xx, AM3517 and OMAP36xx platforms use dpll1 clock.
OMAP443x, OMAP446x, OMAP447x, OMAP5, DRA7, AM43xx platforms use
dpll_mpu clock.
Latency used is the generic latency
]
Signed-off-by: Nishanth Menon n...@ti.com
Signed-off-by: Andrii.Tseglytskyi andrii.tseglyts...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 63 ++
1 file changed, 63 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index
Add ABB device nodes for DRA7 family of devices. Data is based on
DRA7 Technical Reference Manual revision I (Sept 2013)
Signed-off-by: Nishanth Menon n...@ti.com
---
Depends on https://patchwork.kernel.org/patch/3530111/
arch/arm/boot/dts/dra7.dtsi | 132
From: Andrii.Tseglytskyi andrii.tseglyts...@ti.com
Add ABB device node for OMAP36xx family of devices. Data is based on
OMAP36XX Technical Reference Manual revision AB (Dec 2012).
[n...@ti.com: co-developer]
Signed-off-by: Nishanth Menon n...@ti.com
Signed-off-by: Andrii.Tseglytskyi
: Add device nodes for ABB
Nishanth Menon (1):
ARM: dts: DRA7: Add device nodes for ABB
arch/arm/boot/dts/dra7.dtsi | 132 +++
arch/arm/boot/dts/omap36xx.dtsi | 20 ++
arch/arm/boot/dts/omap4.dtsi| 26
arch/arm/boot/dts/omap443x.dtsi
2013).
ABB device nodes for OMAP4460 device Data is based on OMAP4460
Technical Reference Manual revision Z (April 2013)
[n...@ti.com: co-developer]
Signed-off-by: Nishanth Menon n...@ti.com
Signed-off-by: Andrii.Tseglytskyi andrii.tseglyts...@ti.com
---
arch/arm/boot/dts/omap4.dtsi| 26
or omap36xx.dtsi in corresponding tobi board dts.
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
to the maintainer, see CHECKPATCH in MAINTAINERS.
you might want to run something like aiaiai[1] or
kernel_patch_verify[2] or patman... etc.. to help you clean up for
minimum needs.
[1] https://lwn.net/Articles/488992/
[2] https://github.com/nmenon/kernel_patch_verify
--
Regards,
Nishanth Menon
= lan9221_pins;
+ phy-mode = mii;
+ };
+};
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 01/20/2014 05:39 PM, Felipe Balbi wrote:
On Mon, Jan 20, 2014 at 05:29:02PM -0600, Nishanth Menon wrote:
When device is booted using devicetree, platforms impacted by
Erratum 2.1.1.128 is not detected easily in the mmc driver. This erratum
indicates that the module cannot do multi-block
On Tue, Jan 21, 2014 at 12:05 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Tue, Jan 21, 2014 at 11:38:00AM -0600, Nishanth Menon wrote:
On 01/20/2014 05:39 PM, Felipe Balbi wrote:
On Mon, Jan 20, 2014 at 05:29:02PM -0600, Nishanth Menon wrote:
When device is booted using devicetree
,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
*/
omap3_dbb056_display_init_of();
}
#endif /* CONFIG_ARCH_OMAP3 */
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
work/dss-dt-review-3
http://slexy.org/view/s20JhteOFR is my quick build test report - few
checkpatch and build bisect issues would probably need fixing.
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord
Benoit,
On 12/18/2013 11:16 AM, Benoit Cousson wrote:
On 18/12/2013 18:02, Nishanth Menon wrote:
On 12/18/2013 10:57 AM, Benoit Cousson wrote:
On 17/12/2013 20:45, Nishanth Menon wrote:
On 12/09/2013 03:55 PM, Nishanth Menon wrote:
Craneboard is a hardware development platform based
On 01/17/2014 07:20 PM, Nishanth Menon wrote:
[...]
I am running a defconfig set check on next-20140117 and will do one
with next-20140118 once that is ready for comparison results
baseline next-20140120
modified as follows:
multi_v7_defconfig - added CONFIG_SOC_DRA7XX
omap2plus_defconfig
Move all OMAP4 PM errata initializations to centralized location in
omap4_pm_init_early. This allows for users to utilize the erratas
in various submodules as needed.
Reported-by: Tony Lindgren t...@atomide.com
Signed-off-by: Nishanth Menon n...@ti.com
---
Reported by Tony here: https
701 - 800 of 2389 matches
Mail list logo
