The RFBI node for OMAP DSS was left out when adding the rest of the DSS
nodes, because it was not clear how to set up the clocks for the RFBI.
However, it seems that if there is a HWMOD for a device, we also need a
DT node for it. Otherwise, at boot, we get:
WARNING: CPU: 0 PID: 1 at
On 09/03/2014 10:28 PM, Mike Turquette wrote:
Quoting Tero Kristo (2014-08-04 05:36:19)
On 08/04/2014 02:37 PM, Peter Ujfalusi wrote:
On 08/01/2014 04:15 PM, Tero Kristo wrote:
Hi,
This patch adds possibility to register external clocks (outside the main
SoC) on TI boards through device
Hi Suman,
Thank you for the patch.
On Wednesday 03 September 2014 18:58:31 Suman Anna wrote:
Any device requiring to be attached to an iommu_domain must have
valid archdata containing the necessary iommu information, which
is SoC-specific. Add a check in the omap_iommu_attach_dev to make
Hi Suman,
Thank you for the patch.
On Wednesday 03 September 2014 18:58:32 Suman Anna wrote:
A device is tied to an iommu through its archdata field. The archdata
is allocated on the fly for DT-based devices automatically through the
.add_device iommu ops. The current logic incorrectly
On 09/03/2014 08:39 PM, Tony Lindgren wrote:
good.txt and bad.txt are from the late_initcall.
$ diff -u good.txt bad.txt
--- good.txt2014-09-03 10:29:58.920317368 +0200
+++ bad.txt 2014-09-03 10:28:57.064313222 +0200
Hmm can you check that you have good.txt and bad.txt the
right
+ Sekhar.
Hi Pekon,
On 09/03/2014 08:29 PM, pekon wrote:
Hi Roger,
On Wednesday 03 September 2014 02:02 PM, Roger Quadros wrote:
Hi Pekon,
On 09/02/2014 10:02 PM, pekon wrote:
Hi Roger,
On Tuesday 02 September 2014 07:27 PM, Roger Quadros wrote:
NAND uses wait pin only to indicate
LDO8 regulator is used for act led and serial cosole power supply.
Its DT status is declared as disabled, however the serial console was
functional until Commit 318dbb02b (regulator: palmas: Fix SMPS
enable/disable/is_enabled) wich properly turns off LDO8 on boot.
Fix serial cosole power supply
CM-T54 CoM can be used with various custom baseboards, other
than SB-T54 (supplied with SBC-T54 single board computer).
Update model property of SBC-T54 DT to clarify this.
Signed-off-by: Dmitry Lifshitz lifsh...@compulab.co.il
---
arch/arm/boot/dts/omap5-sbc-t54.dts |4 ++--
1 files
Essential fix of CM-T54 serial console power supply and
minor update of SBC-T54 DT model property.
Dmitry Lifshitz (2):
ARM: dts: cm-t54: fix serial console power supply.
ARM: dts: sbc-t54: fix model property
arch/arm/boot/dts/omap5-cm-t54.dts |5 ++---
Hi,
The following series was inspired in part by
http://marc.info/?l=linux-omapm=140974309205295w=2
causing me to try and do an audit of pinctrl configurations on the platform.
Further, failures on latest board updates in the automated farm also
caused identification of a fix which was yet to
From: Lokesh Vutla lokeshvu...@ti.com
DRA7 evm REV G and later boards uses a vtt regulator for DDR3
termination and this is controlled by gpio7_11. This gpio is
configured in boot loader. gpio7_11, which is only available only on
Pad A22, in previous boards, is connected only to an unused pad on
While auditing the various pin ctrl configurations using the following
command:
grep PIN_ arch/arm/boot/dts/dra7-evm.dts|(while read line;
do
v=`echo $line | sed -e s/\s\s*/|/g | cut -d '|' -f1 |
cut -d 'x' -f2|tr [a-z] [A-Z]`;
HEX=`echo
On 08:23-20140904, Nishanth Menon wrote:
While auditing the various pin ctrl configurations using the following
command:
grep PIN_ arch/arm/boot/dts/dra7-evm.dts|(while read line;
do
v=`echo $line | sed -e s/\s\s*/|/g | cut -d '|' -f1 |
cut -d 'x' -f2|tr [a-z] [A-Z
$subject: ARM: dts: OMAP5: Add DSS RFBI node
On 09/04/2014 01:28 AM, Tomi Valkeinen wrote:
The RFBI node for OMAP DSS was left out when adding the rest of the DSS
nodes, because it was not clear how to set up the clocks for the RFBI.
However, it seems that if there is a HWMOD for a device,
On 09/03/2014 07:48 PM, Tony Lindgren wrote:
I will check this upper part of this email soon…
OK. At least it's starting to now sound that the bugs are pretty much
the same with 8250 and serial-omap :)
Do you see a reason for not posting the entire series again since now I
am bug compatible
Hi Tony,
On Thursday 28 August 2014 04:58 AM, Tony Lindgren wrote:
We don't need twl4030_phy_power() any longer now that we have
the runtime PM calls. Let's get rid of it as it's confusing.
No functional changes, just move the code and use res instead
of ret as we are not returning that
From: Jeff Lance j-lan...@ti.com
The TSC driver is beeing updated, the parameter is not used anymore. The
AIN lines can not be muxed. All boards use the same value.
This patch updates the Documentation and dts files.
Cc: Benoît Cousson bcous...@baylibre.com
Cc: Tony Lindgren t...@atomide.com
Cc:
From: Jeff Lance j-lan...@ti.com
The step config setting for a 5 wire touchscreen is incorrectly sets the
Y coordinates.
It was broken while we moved to DT. If you look close, the change was:
|- STEPCONFIG_XNP | STEPCONFIG_YPN;
|+ ts_dev-bit_xn | ts_dev-bit_yp;
while bit_xn = STEPCONFIG_XNN and
From: Jeff Lance j-lan...@ti.com
With the touschscreen in am335x, you do not have the option to mux the
analog input lines. You must connect the analog input to the corresponding
touchscreen terminal.
This patch removes the code that is parsing the ti,wire-config and uses
the default parameters
* Sebastian Andrzej Siewior bige...@linutronix.de [140904 06:46]:
On 09/03/2014 07:48 PM, Tony Lindgren wrote:
I will check this upper part of this email soon…
OK. At least it's starting to now sound that the bugs are pretty much
the same with 8250 and serial-omap :)
Do you see a
On 09/04/2014 04:52 PM, Tony Lindgren wrote:
Yeah makes sense to me. Thanks for ensuring the bug
compability :)
Thanks. What about the ttyOx vs ttySx. Do you want me to add kernel
line fixup somewhere arch/arm or we ignore this for now? Greg didn't
say anything…
Regards,
Tony
On Thu, 4 Sep 2014, Dmitry Lifshitz wrote:
LDO8 regulator is used for act led and serial cosole power supply.
Its DT status is declared as disabled, however the serial console was
functional until Commit 318dbb02b (regulator: palmas: Fix SMPS
enable/disable/is_enabled) wich properly turns
* Sebastian Andrzej Siewior bige...@linutronix.de [140904 07:56]:
On 09/04/2014 04:52 PM, Tony Lindgren wrote:
Yeah makes sense to me. Thanks for ensuring the bug
compability :)
Thanks. What about the ttyOx vs ttySx. Do you want me to add kernel
line fixup somewhere arch/arm or we ignore
* Sebastian Andrzej Siewior bige...@linutronix.de [140904 01:46]:
On 09/03/2014 08:39 PM, Tony Lindgren wrote:
good.txt and bad.txt are from the late_initcall.
$ diff -u good.txt bad.txt
--- good.txt2014-09-03 10:29:58.920317368 +0200
+++ bad.txt 2014-09-03 10:28:57.064313222
From: Jeff Lance j-lan...@ti.com
The logic in AFE_Pen_Ctrl bitmask in the CTRL register is different for five
wire versus four or eight wire touschscreens. This patch should fix this for
five-wire touch screens. There should be no change needed here for four and
eight wire tousch screens.
* Kishon Vijay Abraham I kis...@ti.com [140904 06:51]:
Hi Tony,
On Thursday 28 August 2014 04:58 AM, Tony Lindgren wrote:
We don't need twl4030_phy_power() any longer now that we have
the runtime PM calls. Let's get rid of it as it's confusing.
No functional changes, just move the code
Hi Tony,
On Thursday 04 September 2014 03:12 AM, Tony Lindgren wrote:
* Tony Lindgren t...@atomide.com [140903 14:41]:
* Roger Quadros rog...@ti.com [140902 06:57]:
Hi Tony,
These are some of the issues I found while testing v3.17-rc3.
- Wrong ECC scheme used for am43x GP and EPOS evm. We
On Thursday 04 September 2014 03:16 PM, Roger Quadros wrote:
[...]
This patch is for the 3.17 bug fix cycle. Implementing NAND device ready
mechanism
is a new feature (for DT case) and I will work on it for future versions.
Also I'm not de-scoping wait-pin (or more correctly device ready)
Hi Laurent,
On Wednesday 03 September 2014 18:58:31 Suman Anna wrote:
Any device requiring to be attached to an iommu_domain must have
valid archdata containing the necessary iommu information, which
is SoC-specific. Add a check in the omap_iommu_attach_dev to make
sure that the device has
* pekon pe...@pek-sem.com [140904 12:01]:
Hi Tony,
On Thursday 04 September 2014 03:12 AM, Tony Lindgren wrote:
* Tony Lindgren t...@atomide.com [140903 14:41]:
* Roger Quadros rog...@ti.com [140902 06:57]:
Hi Tony,
These are some of the issues I found while testing v3.17-rc3.
- Wrong
* Nishanth Menon n...@ti.com [140904 06:24]:
Hi,
The following series was inspired in part by
http://marc.info/?l=linux-omapm=140974309205295w=2
causing me to try and do an audit of pinctrl configurations on the platform.
Further, failures on latest board updates in the automated farm
Hi Laurent,
On Wednesday 03 September 2014 18:58:32 Suman Anna wrote:
A device is tied to an iommu through its archdata field. The archdata
is allocated on the fly for DT-based devices automatically through the
.add_device iommu ops. The current logic incorrectly assigned the name
of the
Hello.
This patchset is against the usb-next' branch of Greg KH's 'usb.git' repo.
Here I add support for the generic PHY to the 'struct usb_hcd' (having to
rename the existing 'phy' field to 'usb_phy' beforehand). This was mainly
intended to be used with the PCI OHCI/EHCI drivers and also xHCI
From: Antoine Tenart antoine.ten...@free-electrons.com
The USB PHY member of the HCD structure is renamed to 'usb_phy' and
modifications are done in all drivers accessing it.
This is in preparation to adding the generic PHY support.
Signed-off-by: Antoine Tenart antoine.ten...@free-electrons.com
Hi,
This is an updated series addressing Laurent's review comments on
Patch1. Patch2 is unchanged from the previous series.
Patches are based on 3.17-rc3.
v1:
http://marc.info/?l=linux-omapm=140978874026176w=2
Suman Anna (2):
iommu/omap: Check for valid archdata in attach_dev
iommu/omap:
A device is tied to an iommu through its archdata field. The archdata
is allocated on the fly for DT-based devices automatically through the
.add_device iommu ops. The current logic incorrectly assigned the name
of the IOMMU user device, instead of the name of the IOMMU device as
required by the
Any device requiring to be attached to an iommu_domain must have
valid archdata containing the necessary iommu information, which
is SoC-specific. Add a check in the omap_iommu_attach_dev to make
sure that the device has valid archdata before accessing
different SoC-specific fields of the
The following changes since commit 69e273c0b0a3c337a521d083374c918dc52c666f:
Linux 3.17-rc3 (2014-08-31 18:23:04 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
tags/omap-fixes-against-v3.17-rc3
for you to fetch changes up to
38 matches
Mail list logo
