Actually, I've tested my patch on DM3730, and, at least, can prove
that original settings of UART are incorrect according to TRM of
processor. What settings of UART you were using to reproduce issue?
I'd like to kindly ask you to describe your test environment, since
I've never experiences issues
On Sunday 31 March 2013 07:24 PM, Pali Rohár wrote:
Closed and signed Nokia X-Loader bootloader stored in RX-51 nand does not set
IBE bit in ACTLR and starting kernel in non-secure mode. So direct write to
ACTLR by our kernel does not working and the code for ARM errata 430973 in
commit
Hi
On Mon, 1 Apr 2013, Alexey Pelykh wrote:
Actually, I've tested my patch on DM3730,
What board, bootloader, and test steps did you use? Can you post a dmesg?
and, at least, can prove that original settings of UART are incorrect
according to TRM of processor.
The TRM could be buggy or
Hi,
On Mon, Apr 1, 2013 at 12:13 PM, Paul Walmsley p...@pwsan.com wrote:
Hi
On Mon, 1 Apr 2013, Alexey Pelykh wrote:
Actually, I've tested my patch on DM3730,
What board, bootloader, and test steps did you use? Can you post a dmesg?
I've used LogicPD Torpedo Wireless SoM + DevKit board.
cc Kevin, Felipe
Hi
On Mon, 1 Apr 2013, Alexey Pelykh wrote:
On Mon, Apr 1, 2013 at 12:13 PM, Paul Walmsley p...@pwsan.com wrote:
On Mon, 1 Apr 2013, Alexey Pelykh wrote:
Actually, I've tested my patch on DM3730,
What board, bootloader, and test steps did you use? Can you post a
Hi,
On Thu, 14 Mar 2013, Chen Gang wrote:
if pwrdm_read_pwrst returns negative number, curr_pwrst can not notice it.
since really need check curr_pwrst whether is negative,
need let the check valid in _pwrdm_save_clkdm_state_and_activate.
and also better to check the return
On Thu, 28 Mar 2013, Rajendra Nayak wrote:
omap3_noncore_dpll_set_rate() attempts an enable of bypass clk as well
as ref clk for every .set_rate attempt on a noncore DPLL, regardless of
whether the .set_rate results in the DPLL being locked or put in bypass.
Early at boot, while some of these
Hi Rajendra/Paul/Mike,
I am debugging the issue reported by Michal on AM33xx clock tree
In the context of LCDC driver functionality-
http://www.mail-archive.com/dri-devel@lists.freedesktop.org/msg36102.html
Where, the clk_set_rate() seems to be not working, and that's true
with the current
On 2013年04月01日 18:25, Paul Walmsley wrote:
Hi,
On Thu, 14 Mar 2013, Chen Gang wrote:
if pwrdm_read_pwrst returns negative number, curr_pwrst can not notice it.
since really need check curr_pwrst whether is negative,
need let the check valid in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tony
The following changes since commit 07961ac7c0ee8b546658717034fe692fd12eefa9:
Linux 3.9-rc5 (2013-03-31 15:12:43 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git
Where, the clk_set_rate() seems to be not working, and that's true
with the current implementation of OMAP/AM33xx clock tree,
as the CLK_SET_RATE_PARENT flag is not set to any of the clock nodes.
Please note that I am using DEFINE_STRUCT_CLK() macro for defining clocks
And which doesn't
On Mon, Mar 25, 2013 at 12:57:56PM +0530, Mugunthan V N wrote:
am33xx_pinmux: pinmux@44e10800 {
pinctrl-names = default;
- pinctrl-0 = user_leds_s0;
+ pinctrl-0 = user_leds_s0 cpsw_s0;
Why do you add cpsw_s0 to the pinmux node? This should go into
On Mon, Apr 1, 2013 at 1:19 PM, Paul Walmsley p...@pwsan.com wrote:
cc Kevin, Felipe
Hi
On Mon, 1 Apr 2013, Alexey Pelykh wrote:
On Mon, Apr 1, 2013 at 12:13 PM, Paul Walmsley p...@pwsan.com wrote:
On Mon, 1 Apr 2013, Alexey Pelykh wrote:
Actually, I've tested my patch on DM3730,
Hi,
Subject changed to Re: [*RFC* PATCH 5/6] ARM: OMAP3+: ABB: introduce
ABB driver
On 03/29/2013 12:35 AM, Nishanth Menon wrote:
- ti internal list which got into the git send-email by error.
Apologies on the bounces which might have resulted... On
14:27-20130328, Mike Turquette wrote:
-Original Message-
From: Nayak, Rajendra
Sent: Monday, April 01, 2013 4:14 PM
To: Hiremath, Vaibhav
Cc: mturque...@linaro.org; Paul Walmsley; Tony Lindgren; linux-
o...@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
khil...@deeprootsystems.com
Subject: Re: Query regarding
Hi,
Subject changed to Re: [*RFC* PATCH 5/6] ARM: OMAP3+: ABB: introduce
ABB driver
On 03/29/2013 12:35 AM, Nishanth Menon wrote:
- ti internal list which got into the git send-email by error.
Apologies on the bounces which might have resulted... On
14:27-20130328, Mike Turquette wrote:
Paul,
Please, correct me if I'm wrong, you're experiencing issues on Tx, or
Rx direction? You've said that characters are echoed incorrectly, but
haven't mentioned in what direction issue appears?
For reference, I'll quote TI DM3730 Rev.R TRM:
TRM page 2953, LSR_REG
Bit #5: TX_FIFO_E
0x0
-Original Message-
From: Hiremath, Vaibhav
Sent: Monday, April 01, 2013 4:37 PM
To: Nayak, Rajendra
Cc: mturque...@linaro.org; Paul Walmsley; Tony Lindgren; linux-
o...@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
khil...@deeprootsystems.com
Subject: RE: Query regarding
This patch-series enables runtime power management on xhci-plat,
dwc3-core, dwc3-exynos as well as on Samsung's USB 2.0 type and
USB 3.0 type PHYs.
Based on 'next' branch of Felipe Balbi's USB tree.
Changes from v2:
- Using separate functions for USB PHY runtime power management, instead of
By enabling runtime pm in this driver allows users of
xhci-plat to enter into runtime pm. This is not full
runtime pm support (AKA xhci-plat doesn't actually power
anything off when in runtime suspend mode) but,
just basic enablement.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
CC: Doug
Enable autosuspending of Samsung usb2.0 PHY
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
drivers/usb/phy/phy-samsung-usb2.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/phy/phy-samsung-usb2.c
b/drivers/usb/phy/phy-samsung-usb2.c
index
Enable autosuspending of Samsung usb3.0 PHY
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
drivers/usb/phy/phy-samsung-usb3.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/phy/phy-samsung-usb3.c
b/drivers/usb/phy/phy-samsung-usb3.c
index
Enabling runtime power management on dwc3-exynos
letting dwc3 controller to be autosuspended on exynos
platform when not in use.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
drivers/usb/dwc3/dwc3-exynos.c | 12
1 files changed, 12 insertions(+), 0 deletions(-)
diff
Adding APIs to handle runtime power management on PHY
devices. PHY consumers may need to wake-up/suspend PHYs
when they work across autosuspend.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
include/linux/usb/phy.h | 141 +++
1 files
Right now it doesn't handle full runtime suspend/resume
functionality. However it allows to handle PHYs' sleep
and wakeup across runtime suspend/resume.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
drivers/usb/dwc3/core.c | 43 +++
1 files
Allow dwc3 to enable auto power management only after its PHYs
are initialized so that any further PHY handling by dwc3's
runtime power management callbacks is fine.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
drivers/usb/dwc3/core.c | 18 +-
1 files changed, 9
The current code in the dwc3 probe effectively disables runtime pm
from ever working because it calls a get() that was never put() until
device removal. Change the runtime pm code to match the standard
formula and allow runtime pm to function.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
* Paul Bolle pebo...@tiscali.nl [130321 14:40]:
The Kconfig symbol MACH_OMAP_HTCWIZARD got added in v2.6.30. It has
never been used. Its entry can safely be removed.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
Untested.
Thanks, applying into omap-for-v3.10/fixes-non-critical.
* Paul Bolle pebo...@tiscali.nl [130325 16:34]:
Commit 90173882ed15a8034d6d162da5f343a2c7d87587 (omap: add dsp platform
device) used CONFIG_BRIDGE_DVFS were it obviously meant
CONFIG_TIDSPBRIDGE_DVFS. Fix that.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
Untested. As this typo has
* Paul Walmsley p...@pwsan.com [130401 03:48]:
Hi Tony
The following changes since commit 07961ac7c0ee8b546658717034fe692fd12eefa9:
Linux 3.9-rc5 (2013-03-31 15:12:43 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git
Hello Greg,
Here is a new series of patches for ti-soc-thermal. It will contain
a couple of minor fixes, but it has also support for trending,
computed by HW history buffer.
These patches are also available here:
g...@gitorious.org:thermal-framework/thermal-framework.git
Improve ti_bandgap_power by returning an error code in case
the device does not support controlling its power state.
Signed-off-by: Eduardo Valentin eduardo.valen...@ti.com
---
drivers/staging/ti-soc-thermal/ti-bandgap.c |8 +---
1 files changed, 5 insertions(+), 3 deletions(-)
diff
Whenever a sensor has an alert to be reported to the thermal framework,
it can use the report ti_thermal_report_temperature helper. This patch
expose this function so that bandgap data config declarations could use it.
Signed-off-by: Eduardo Valentin eduardo.valen...@ti.com
---
OMAP4460 and OMAP4470 devices have the capability to generate
alert temperature. Thus, whenever a T_ALERT IRQ is served,
the ti-bandgap will call .report_temperature to notify the
thermal framework about thermal zone update request.
This patch allows OMAP4460 and OMAP4470 devices to notify
the
From: Nishanth Menon n...@ti.com
Fix all kernel-doc warnings by add documentation about returns.
Signed-off-by: Nishanth Menon n...@ti.com
Signed-off-by: Eduardo Valentin eduardo.valen...@ti.com
---
drivers/staging/ti-soc-thermal/ti-bandgap.c | 58 +-
1 files changed,
OMAP5430 devices have the capability to generate
alert temperature. Thus, whenever a T_ALERT IRQ is served,
the ti-bandgap will call .report_temperature to notify the
thermal framework about thermal zone update request.
This patch allows OMAP5430 devices to notify
the thermal framework about
From: J Keerthy j-keer...@ti.com
Add counter_delay_mask field to temp_sensor_registers structure.
Signed-off-by: J Keerthy j-keer...@ti.com
Signed-off-by: Eduardo Valentin eduardo.valen...@ti.com
---
drivers/staging/ti-soc-thermal/ti-bandgap.h |2 ++
1 files changed, 2 insertions(+), 0
From: J Keerthy j-keer...@ti.com
Initialize all 3 temperature sensors of OMAP5 bandgap with the counter delay
mask.
Signed-off-by: J Keerthy j-keer...@ti.com
Signed-off-by: Eduardo Valentin eduardo.valen...@ti.com
---
.../staging/ti-soc-thermal/omap5-thermal-data.c|3 +++
From: J Keerthy j-keer...@ti.com
Introduce HAS_COUNTER_DELAY feature for bandgap.
Signed-off-by: J Keerthy j-keer...@ti.com
Signed-off-by: Eduardo Valentin eduardo.valen...@ti.com
---
drivers/staging/ti-soc-thermal/ti-bandgap.h |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff
From: J Keerthy j-keer...@ti.com
Enable COUNTER_DELAY feature for OMAP5.
Signed-off-by: J Keerthy j-keer...@ti.com
Signed-off-by: Eduardo Valentin eduardo.valen...@ti.com
---
.../staging/ti-soc-thermal/omap5-thermal-data.c|3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff
From: J Keerthy j-keer...@ti.com
Update ti_bandgap_write_update_interval and ti_bandgap_read_update_interval
functions to incorporate the OMAP5 feature of COUNTER_DELAY. The way we
program the delay between two successive temperature conversions
is different for OMAP5 as when compared with OMAP4.
From: J Keerthy j-keer...@ti.com
The patch introduces HISTORY_BUFFER feature. This is present in OMAP5 bandgap
and it is a hardware history buffer of previously read temperatures.
Signed-off-by: J Keerthy j-keer...@ti.com
Signed-off-by: Eduardo Valentin eduardo.valen...@ti.com
---
From: J Keerthy j-keer...@ti.com
This patch enables the HISTORY_BUFFER eature for OMAP5.
Signed-off-by: J Keerthy j-keer...@ti.com
Signed-off-by: Eduardo Valentin eduardo.valen...@ti.com
---
.../staging/ti-soc-thermal/omap5-thermal-data.c|3 ++-
1 files changed, 2 insertions(+), 1
From: J Keerthy j-keer...@ti.com
The patch adds ti_bandgap_get_trend function. This is specific
to OMAP5 for now it computes the trend from the temp values stored
in the hardware history buffer.
Formula: (T1 - T2) / P.
Where:
T1: Last read valid temperature.
T2:
From: J Keerthy j-keer...@ti.com
Patch adds get_trend functionality for OMAP Bandgap thermal devices.
Signed-off-by: J Keerthy j-keer...@ti.com
Signed-off-by: Eduardo Valentin eduardo.valen...@ti.com
---
drivers/staging/ti-soc-thermal/ti-thermal-common.c | 27 +++-
1 files
* Pali Rohár pali.ro...@gmail.com [130331 02:32]:
On Thursday 28 March 2013 22:44:11 Tony Lindgren wrote:
You can use regular clk_get if you add the alias to
struct omap_clk omap3xxx_clks table.
Tony, can you show me how?
Take a look at the omap3xxx_clks in cclock3xxx_data.c.
Note how
Hi Javier
On Sat, 2013-03-30 at 14:18 +0100, Javier Martinez Canillas wrote:
A call to gpio_request() to enable the GPIO bank is needed before
using a GPIO as an IRQ source, otherwise accesses to the GPIO bank
registers fails making the kernel to hang.
Yes, that is exactly my problem here.
* Santosh Shilimkar santosh.shilim...@ti.com [130320 01:42]:
Tony,
Here is the pull request for various OMAP5 generic updates which are posted
earlier on the list. It contains OMAP5 es2 related updates like idcode,
RAM base and couple of initialisation fixes.
The following changes since
* Ивайло Димитров freemangor...@abv.bg [130331 05:10]:
Hi Pali,
Yep, the code looks almost identical, I guess with some tweaks all SMC code
from that patch could be removed and instead used the one from SMC PPA API.
What I don't get, is why one needs to disable/enable fiqs/irqs:
* Santosh Shilimkar santosh.shilim...@ti.com [130320 01:43]:
Tony,
Here is the pull request for OMAP5 data file patches which are on list from
last merge window. As aligned on list, I have dropped clock data from the
series. That means for the boot, one clock data patch needs to be applied.
* Paul Walmsley p...@pwsan.com [130330 15:51]:
Hi Tony,
The following changes since commit 78e52e026d288aad88b46bff0d94b05e145c4583:
ARM: OMAP2+: clock data: Remove CK_* flags (2013-03-18 09:57:39 -0600)
are available in the git repository at:
On Mon, 1 Apr 2013, Alexey Pelykh wrote:
Please, correct me if I'm wrong, you're experiencing issues on Tx, or
Rx direction? You've said that characters are echoed incorrectly, but
haven't mentioned in what direction issue appears?
The problem seems to be on the Rx path. If I 'cat' a file,
* Tero Kristo t-kri...@ti.com [130327 02:15]:
On Tue, 2013-03-26 at 18:43 +, Paul Walmsley wrote:
So what I'd like you to do is:
1. Determine what devices are remaining to be reset and idled on OMAP4
with the bootloader that I use. As far as I know, there are only four
Vinod,
On 03/20/2013 11:36 AM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [130319 09:08]:
Vinod, Tony, Benoit,
On 02/26/2013 12:27 PM, Jon Hunter wrote:
If the device-tree blob is present during boot, then register the SDMA
controller with the device-tree DMA driver so that we can
Paul, can you please try to comment out change related to Rx line
(granulation one). That's only Rx line related change in the patch.
On Mon, Apr 1, 2013 at 8:09 PM, Paul Walmsley p...@pwsan.com wrote:
On Mon, 1 Apr 2013, Alexey Pelykh wrote:
Please, correct me if I'm wrong, you're
Andrii,
Sorry to nitpick further but this your replies look very non-standard.
Typically a right chevron and a space is used to indent replies instead
of a tab. Something like this:
https://wiki.openstack.org/wiki/MailingListEtiquette#Reply_Level_Indication
Quoting Andrii Tseglytskyi
On Mon, Apr 01, 2013 at 12:48:26PM -0500, Jon Hunter wrote:
Vinod,
On 03/20/2013 11:36 AM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [130319 09:08]:
Vinod, Tony, Benoit,
On 02/26/2013 12:27 PM, Jon Hunter wrote:
If the device-tree blob is present during boot, then register
On Mon, Apr 1, 2013 at 1:10 PM, Mike Turquette mturque...@linaro.org wrote:
Andrii,
Sorry to nitpick further but this your replies look very non-standard.
Typically a right chevron and a space is used to indent replies instead
of a tab. Something like this:
Just couple minor comments...
On 03/28/2013 06:43 AM, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without using phandle. To obtain a reference to the PHY
omap_udc platform device is not registered properly anymore:
CONFIG_USB_GADGET_OMAP was deleted by 193ab2a6 (usb: gadget: allow
multiple gadgets to be built) already in v3.1.
Fix by using CONFIG_USB_OMAP instead. Tested on Nokia 770 by checking
that omap_udc is probed working properly when built
Add missing regulator definitions for lis3lv02d accelerometer. Fixes
the following probe issue:
[ 57.737518] lis3lv02d_i2c 3-001d: Failed to get supply 'Vdd': -517
[ 57.747100] i2c 3-001d: Driver lis3lv02d_i2c requests probe deferral
Reported-by: Pali Rohár pali.ro...@gmail.com
Reviewed-by:
On Mon, Apr 1, 2013 at 6:41 PM, Christoph Fritz
chf.fr...@googlemail.com wrote:
Hi Javier
On Sat, 2013-03-30 at 14:18 +0100, Javier Martinez Canillas wrote:
A call to gpio_request() to enable the GPIO bank is needed before
using a GPIO as an IRQ source, otherwise accesses to the GPIO bank
It could be that I am misreading something, but RX51 is OMAP3.
Regards,
Ivo
Оригинално писмо
От: Tony Lindgren
Относно: Re: [PATCH] OMAP3 ROM Random Number Generator support
До: Ивайло Димитров
Изпратено на: Понеделник, 2013, Април 1 19:59:50 EEST
* Ивайло
On Sat, Mar 30, 2013 at 7:35 PM, Paul Walmsley p...@pwsan.com wrote:
Hi Mike, Kevin,
On Wed, 3 Oct 2012, Mike Turquette wrote:
From: Mike Turquette mturque...@linaro.org
This series creates a new callback for struct voltagedomain,
.get_voltage. This fetches the voltage from hardware, if
Hi,
On Sun, Mar 31, 2013 at 03:05:42PM +0300, Ивайло Димитров wrote:
Yep, the code looks almost identical, I guess with some tweaks all SMC
code from that patch could be removed and instead used the one from SMC
PPA API.
What I don't get, is why one needs to disable/enable fiqs/irqs:
[..]
From: Rob Herring rob.herr...@calxeda.com
This converts arm and arm64 to use CLKSRC_OF DT based initialization for
the arch timer. A new function arch_timer_arch_init is added to allow for
arch specific setup.
This has a side effect of enabling sched_clock on omap5 and exynos5. There
should not
On 03/28/2013 06:43 AM, Kishon Vijay Abraham I wrote:
diff --git a/Documentation/devicetree/bindings/phy/phy-bindings.txt
b/Documentation/devicetree/bindings/phy/phy-bindings.txt
new file mode 100644
index 000..35696b2
--- /dev/null
+++
On 04/01/2013 04:27 PM, Sylwester Nawrocki wrote:
On 03/28/2013 06:43 AM, Kishon Vijay Abraham I wrote:
diff --git a/Documentation/devicetree/bindings/phy/phy-bindings.txt
+example2:
+phys: phy {
+compatible = xxx;
+reg =...;
+.
+.
+phys =phys 1;
+.
+.
+};
On 14:34-20130401, Mike Turquette wrote:
Quoting Nishanth Menon (2013-04-01 12:28:20)
On Mon, Apr 1, 2013 at 1:10 PM, Mike Turquette mturque...@linaro.org
wrote:
Let's figure out what is happening to the VC/VP code first and then
figure out what to do about ABB.
http
The following changes since commit 2d61aecee8f32259920cdf90a452fa26ffc64e9f:
Merge commit '6bb27d7349db51b50c40534710fe164ca0d58902' into
omap-timer-for-v3.10 (2013-04-01 13:47:29 -0500)
are available in the git repository at:
git://github.com/jonhunter/linux.git omap-timer-for-v3.10
for
On Tuesday 02 April 2013 03:51 AM, Rob Herring wrote:
From: Rob Herring rob.herr...@calxeda.com
This converts arm and arm64 to use CLKSRC_OF DT based initialization for
the arch timer. A new function arch_timer_arch_init is added to allow for
arch specific setup.
This has a side effect of
On 17:05-20130401, Mike Turquette wrote:
OK, so we're in agreement on what The Future looks like. What does that
mean for Andrii's patchset?
Unless anyone has an fundamental issue with the approach of an Super
regulator controlling sub regulators, I think, in-line with your
view, we should
72 matches
Mail list logo
