On Wed, Sep 24, 2014 at 10:28:07PM +0200, Rafael J. Wysocki wrote:
OK, I guess this is as good as it gets.
What tree would you like it go through?
Since rest of the patches are dependent upon 1st patch which should go thru
your tree, we should merge this thru your tree
Thanks
--
~Vinod
If the chosen baud rate is large enough (e.g. 3.5 megabaud), the
calculated n values in serial_omap_is_baud_mode16() may become 0. This
causes a division by zero when calculating the difference between
calculated and desired baud rates. To prevent this, cap the n13 and n16
values on 1.
Division
* Heikki Krogerus | 2014-09-22 10:46:05 [+0300]:
Well, there are no other SoCs at the moment that would need it, and
it's actually possible that there never will be. So yes, just handle
that also in the omap specific code.
Okay. So let me move the irq routine and the workarounds into omap then.
Currently all the device data is declared globally which will be a
problem if more than one instance of device is present. So consolidate
all the data into rtc_omap_dev struct and adopt the driver to use this.
Suggested-by: Felipe Balbi ba...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
On some Soc's RTC is powered by an external power regulator.
e.g. RTC on DRA7 SoC. Make the OMAP RTC driver support a
power regulator.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
Changes since v1:
- Separated probe deferral supporting into a new patch.
module_platform_driver_probe() prevents driver from requesting probe deferral.
So using module_platform_drive() to support probe deferral.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
Changes since V1:
- New patch, seperated from patch 4/4.
drivers/rtc/rtc-omap.c | 5 +++--
1 file
From: Tero Kristo t-kri...@ti.com
RTC is present in AM43xx and DRA7xx also. Updating the
same in Kconfig.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
Signed-off-by: Tero Kristo t-kri...@ti.com
---
Changes since v1:
- New patch
drivers/rtc/Kconfig| 6 +++---
drivers/rtc/rtc-omap.c
This series cleans up the OMAP RTC driver to use per device data structure.
And adds support for regulator supply.
Testing:
RTC functionality test on:
DRA742-evm: http://hastebin.com/avowiyegut.xml
DRA722-evm: http://hastebin.com/hujuyuyato.xml
Beagle Bone Black: http://hastebin.com/fawahapuyi.rb
On Thu, Sep 25, 2014 at 11:19:51AM +0200, Frans Klaver wrote:
If the chosen baud rate is large enough (e.g. 3.5 megabaud), the
calculated n values in serial_omap_is_baud_mode16() may become 0. This
causes a division by zero when calculating the difference between
calculated and desired baud
On Thu, Sep 25, 2014 at 12:16:28PM +0200, Greg Kroah-Hartman wrote:
On Thu, Sep 25, 2014 at 11:19:51AM +0200, Frans Klaver wrote:
If the chosen baud rate is large enough (e.g. 3.5 megabaud), the
calculated n values in serial_omap_is_baud_mode16() may become 0. This
causes a division by zero
* Sebastian Andrzej Siewior | 2014-09-24 09:53:46 [+0200]:
* Peter Hurley | 2014-09-23 13:03:51 [-0400]:
But DMA is cheating if the UART driver's tx_empty() method is saying the
transmitter is empty while TX DMA is still running.
This shouldn't be the case. But I will check this once I able to.
On Wed, 2014-09-24 at 16:48 +0530, Kiran Padwal wrote:
There is no need to init .owner field.
Based on the patch from Peter Griffin peter.grif...@linaro.org
mmc: remove .owner field for drivers using module_platform_driver
This patch removes the superflous .owner field for drivers which
On 09/25/2014 06:42 AM, Sebastian Andrzej Siewior wrote:
* Sebastian Andrzej Siewior | 2014-09-24 09:53:46 [+0200]:
* Peter Hurley | 2014-09-23 13:03:51 [-0400]:
But DMA is cheating if the UART driver's tx_empty() method is saying the
transmitter is empty while TX DMA is still running.
* Peter Hurley | 2014-09-25 07:31:32 [-0400]:
I just verified that GNU readline6 uses ioctl(TCSETSW, ...) to do the
set_termios
(which is the ioctl that libc should use for tcsetattr(TCSADRAIN)).
Maybe this userspace is using a readline()-alike that has a bug by not using
the
correct
On Tue, Sep 09, 2014 at 06:45:45PM +0300, Laurent Pinchart wrote:
The owner field is never set. Remove it.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
drivers/iommu/omap-iommu.c | 11 ---
drivers/iommu/omap-iommu.h | 1 -
2 files changed, 12 deletions(-)
On Thu, Sep 25, 2014 at 03:02:08PM +0530, Lokesh Vutla wrote:
From: Tero Kristo t-kri...@ti.com
RTC is present in AM43xx and DRA7xx also. Updating the
same in Kconfig.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
Signed-off-by: Tero Kristo t-kri...@ti.com
---
Changes since v1:
* Frans Klaver | 2014-09-22 11:28:54 [+0200]:
I guess then we'd still have to answer the question why the yocto build
calls set_termios() so often, but that's not on you then. Did you notice
it even changing settings? We might want to fix this even if the kernel
should be able to cope.
could you
On 25 September 2014 17:14:03 CEST, Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
* Frans Klaver | 2014-09-22 11:28:54 [+0200]:
I guess then we'd still have to answer the question why the yocto
build
calls set_termios() so often, but that's not on you then. Did you
notice
it even
* Peter Ujfalusi | 2014-09-20 00:29:01 [+0300]:
mask 800 means URXEVT0 (UART0 rx), 400 is UTXEVT0 (UART0 tx) events.
But it is clear that my theory was not even close to what's going on.
Do you have some tool which can be used to reproduce this issue?
The latest uart patch set is at
On Thursday, September 25, 2014 04:27:58 PM Wolfram Sang wrote:
--Bn2rw/3z4jIqBvZU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Sep 25, 2014 at 09:22:01AM -0500, Felipe Balbi wrote:
On Thu, Sep 25, 2014 at
Ohad,
On 09/17/2014 08:37 AM, Ohad Ben-Cohen wrote: Hi Suman,
On Tue, Sep 16, 2014 at 7:14 PM, Suman Anna s-a...@ti.com wrote:
The current remoteproc infrastructure automatically calls rproc_boot only
as part of the rpmsg/virtio stack (in remoteproc_virtio.c), but since the
WkupM3 does not
On Thursday 18 September 2014, Tony Lindgren wrote:
The following changes since commit 55601c9f24670ba926ebdd4d712ac3b177232330:
arm: omap: intc: switch over to linear irq domain (2014-09-11 13:05:50
-0700)
are available in the git repository at:
On Thursday 18 September 2014, Tony Lindgren wrote:
Few hwmod changes to support upcoming 8250 driver with DMA,
start using the SRAM driver for some omaps, and update the
defconfig.
Pulled into next/soc, thanks!
Arnd
--
To unsubscribe from this list: send the line unsubscribe
On Thursday 18 September 2014, Tony Lindgren wrote:
The following changes since commit d27704d1ec2f9ba06247b402c58a6f2febecef78:
ARM: dts: OMAP2+: Add sub mailboxes device node information (2014-09-11
11:46:30 -0700)
are available in the git repository at:
On Thursday 18 September 2014, Tony Lindgren wrote:
Clean-up for omaps for v3.18 merge window:
- Remove unused pieces of the legacy DMA API as we're moving to
dmaengine API
- Search and replace to standardize on pr_warn instead of pr_warning
Nice cleanup!
Merged into next/cleanup,
Quoting Kiran Padwal (2014-09-24 02:45:29)
There is no need to init .owner field.
Based on the patch from Peter Griffin peter.grif...@linaro.org
mmc: remove .owner field for drivers using module_platform_driver
This patch removes the superflous .owner field for drivers which
use the
On 09/23/14 06:38, Tero Kristo wrote:
On 09/22/2014 10:18 PM, Stephen Boyd wrote:
On 08/21, Tero Kristo wrote:
/* Skip children who will be reparented to another clock */
if (child-new_parent child-new_parent != clk)
continue;
Are we not hitting the
27 matches
Mail list logo
