On Thu, Jul 23, 2015 at 02:07:59PM +0200, Pavel Machek wrote:
On Tue 2015-07-21 09:21:32, Sascha Hauer wrote:
The thermal code uses int, long and unsigned long for temperatures
in different places.
Using an unsigned type limits the thermal framework to positive
temperatures without
Hi Greg,
On Tuesday 14 July 2015 06:19 PM, Tony Lindgren wrote:
* Peter Hurley pe...@hurleysoftware.com [150714 05:24]:
On 07/14/2015 04:02 AM, Sekhar Nori wrote:
This series works around Advisory 21 as documented in
AM437x SoC errata[1]. This errata prevents UART module
from idling after
Patch series first fixes memory corruption and then adds support to
handle non maxpacket aligned transfers.
Patch series adds support to handle non maxpacket aligned transfers
greater than bounce buffer size (512). It first adds chained TRB
support and then uses it to handle non maxpacket aligned
The thermal code uses int, long and unsigned long for temperatures
in different places.
Using an unsigned type limits the thermal framework to positive
temperatures without need. Also several drivers currently will report
temperatures near UINT_MAX for temperatures below 0°C. This will probably
No functional change. Used _roundup_ macro to calculate the transfer
size aligned to maxpacket in dwc3_ep0_complete_data. It also makes it
similar to how transfer size is calculated in __dwc3_ep0_do_control_data.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/dwc3/ep0.c |
No functional change. Added a new parameter in _dwc3_ep0_start_trans_ to
indicate whether the TRB is a chained TRB or last TRB. This is in
preparation for adding chained TRB support for ep0.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/dwc3/ep0.c | 15 ---
1
No functional change. This is in preparation for handling non maxpacket
aligned transfers greater than bounce buffer size. This is basically to
avoid code duplication when using chained TRB transfers to handle
non maxpacket aligned transfers greater than bounce buffer size.
Signed-off-by: Kishon
Hi Greg,
On Friday 24 July 2015 03:55 AM, Greg Kroah-Hartman wrote:
On Thu, Jun 25, 2015 at 03:45:04PM +0530, Sekhar Nori wrote:
omap_device infrastructure has a suspend_noirq hook which
runtime suspends all devices late in the suspend cycle (see
_od_suspend_noirq() in
DWC3 uses bounce buffer to handle non max packet aligned OUT transfers and
the size of bounce buffer is 512 bytes. However if the host initiates OUT
transfers of size more than 512 bytes (and non max packet aligned), the
driver throws a WARN dump but still programs the TRB to receive more than
512
DWC3 uses bounce buffer to handle non max packet aligned OUT transfers and
the size of bounce buffer is 512 bytes. However if the host initiates OUT
transfers of size more than 512 bytes (and non max packet aligned), the
driver throws a WARN dump but still programs the TRB to receive more than
512
Use chained TRB mechanism to handle non maxpacket aligned transfers
greater than bounce buffer size. With this the first TRB will be programmed
to receive 'ALIGN(ur-length - maxp, maxp)' data and the second TRB
will be programmed to receive the remaining data using bounce buffer.
Signed-off-by:
Add chained TRB support to ep0. Now TRB's can be chained just by
invoking _dwc3_ep0_start_trans_ with 'chain' parameter set to true.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/dwc3/ep0.c| 16 +---
drivers/usb/dwc3/gadget.c |2 +-
2 files changed, 14
On 07/11/15 at 02:05pm, Pali Rohár wrote:
Hello,
now I tested 4.2-rc1 release on Nokia N900 and couple of drivers are
broken and cause kernel oops...
Basically wifi, touchscreen and rtc drivers not working...
Pali, could you tell how do you test mainline kernel on n900?
I used to use
On Fri 2015-07-24 16:18:09, Dave Young wrote:
On 07/11/15 at 02:05pm, Pali Rohár wrote:
Hello,
now I tested 4.2-rc1 release on Nokia N900 and couple of drivers are
broken and cause kernel oops...
Basically wifi, touchscreen and rtc drivers not working...
Pali, could you tell
On Friday 24 July 2015 16:18:09 Dave Young wrote:
On 07/11/15 at 02:05pm, Pali Rohár wrote:
Hello,
now I tested 4.2-rc1 release on Nokia N900 and couple of drivers are
broken and cause kernel oops...
Basically wifi, touchscreen and rtc drivers not working...
Pali, could you
On 24.07.2015 11:18, Dave Young wrote:
Pali, could you tell how do you test mainline kernel on n900?
I used to use n900 as a usb dbgp gadget with a backport patch to
2.6.28 so that I can get early debug kernel message from my laptop.
I tried mainline previously with Fedora arm, text mode
Hello.
On 7/24/2015 9:47 AM, Kishon Vijay Abraham I wrote:
No functional change. Added a new parameter in _dwc3_ep0_start_trans_ to
indicate whether the TRB is a chained TRB or last TRB. This is in
preparation for adding chained TRB support for ep0.
Signed-off-by: Kishon Vijay Abraham I
On 07/24/15 at 11:30am, Ivaylo Dimitrov wrote:
On 24.07.2015 11:18, Dave Young wrote:
Pali, could you tell how do you test mainline kernel on n900?
I used to use n900 as a usb dbgp gadget with a backport patch to
2.6.28 so that I can get early debug kernel message from my laptop.
I
Hi, Pali
On 07/24/15 at 10:40am, Pali Rohár wrote:
On Friday 24 July 2015 16:18:09 Dave Young wrote:
On 07/11/15 at 02:05pm, Pali Rohár wrote:
Hello,
now I tested 4.2-rc1 release on Nokia N900 and couple of drivers are
broken and cause kernel oops...
Basically wifi,
On 07/24/15 at 10:51am, Pavel Machek wrote:
On Fri 2015-07-24 16:18:09, Dave Young wrote:
On 07/11/15 at 02:05pm, Pali Rohár wrote:
Hello,
now I tested 4.2-rc1 release on Nokia N900 and couple of drivers are
broken and cause kernel oops...
Basically wifi, touchscreen and rtc
On Friday 24 July 2015 18:33:51 Dave Young wrote:
Hi, Pali
On 07/24/15 at 10:40am, Pali Rohár wrote:
On Friday 24 July 2015 16:18:09 Dave Young wrote:
On 07/11/15 at 02:05pm, Pali Rohár wrote:
Hello,
now I tested 4.2-rc1 release on Nokia N900 and couple of drivers are
On Friday 24 July 2015 18:28:44 Dave Young wrote:
On 07/24/15 at 11:30am, Ivaylo Dimitrov wrote:
On 24.07.2015 11:18, Dave Young wrote:
Pali, could you tell how do you test mainline kernel on n900?
I used to use n900 as a usb dbgp gadget with a backport patch to
2.6.28 so that
Hi,
On Mon, Mar 23, 2015 at 10:20:28AM +1100, NeilBrown wrote:
From: NeilBrown ne...@suse.de
This simplifies the error paths.
Signed-off-by: NeilBrown ne...@suse.de
I queued this with Pavel's ACK after a rebase to current master:
On Friday 24 July 2015 10:40:58 Pali Rohár wrote:
On Friday 24 July 2015 16:18:09 Dave Young wrote:
On 07/11/15 at 02:05pm, Pali Rohár wrote:
Hello,
now I tested 4.2-rc1 release on Nokia N900 and couple of drivers
are broken and cause kernel oops...
Basically wifi,
Hi Tony,
On 07/23/2015 11:30 PM, Tony Lindgren wrote:
* Suman Anna s-a...@ti.com [150723 09:25]:
Hi Tony,
On 07/23/2015 02:24 AM, Tony Lindgren wrote:
* Suman Anna s-a...@ti.com [150722 09:25]:
On 07/22/2015 12:26 AM, Tony Lindgren wrote:
I don't like using syscon for tinkering directly
Hello,
when on N900 (real HW or qemu) I run this command
/ # echo 0 /sys/devices/platform/omapdss/overlay0/enabled echo 0
/sys/class/graphics/fb0/size
then kernel crash with this error message
/ # [ 29.904113] Division by zero in kernel.
** 3375 printk messages dropped ** [ 29.963836]
On Wed, Jul 22, 2015 at 08:46:09PM +0200, Sebastian Reichel wrote:
Since commit ddcad7e9068eb omap2_mcspi_set_cs() is called without
runtime power management requested. Thus the below kernel oops may be
generated if a device is accessed after the runtime power management
timeout. This patch
Hi,
On Mon, Mar 23, 2015 at 10:20:28AM +1100, NeilBrown wrote:
From: NeilBrown ne...@suse.de
Final allocations/registrations are now managed by devres.
Signed-off-by: NeilBrown ne...@suse.de
Thanks for the patch, rebased to current master and queued with
Pavel's ACK:
Hi Neil,
On Mon, Mar 23, 2015 at 10:20:28AM +1100, NeilBrown wrote:
here is V2 of my patches to improve the twl4030 charger.
They include improved documentation and removal of changes
to the CVENAC bit which I didn't properly understand.
I rebased and queued patches 1 and 2. Can you rebase
On 07/24/2015 03:11 PM, Pavel Machek wrote:
On Fri 2015-07-24 06:59:26, Guenter Roeck wrote:
On 07/23/2015 11:29 PM, Sascha Hauer wrote:
On Thu, Jul 23, 2015 at 02:07:59PM +0200, Pavel Machek wrote:
On Tue 2015-07-21 09:21:32, Sascha Hauer wrote:
The thermal code uses int, long and unsigned
On 07/23/2015 11:29 PM, Sascha Hauer wrote:
On Thu, Jul 23, 2015 at 02:07:59PM +0200, Pavel Machek wrote:
On Tue 2015-07-21 09:21:32, Sascha Hauer wrote:
The thermal code uses int, long and unsigned long for temperatures
in different places.
Using an unsigned type limits the thermal framework
On Fri, Jul 24, 2015 at 12:11:20PM +0530, Sekhar Nori wrote:
Hi Greg,
On Tuesday 14 July 2015 06:19 PM, Tony Lindgren wrote:
* Peter Hurley pe...@hurleysoftware.com [150714 05:24]:
On 07/14/2015 04:02 AM, Sekhar Nori wrote:
This series works around Advisory 21 as documented in
AM437x
On Fri 2015-07-24 06:59:26, Guenter Roeck wrote:
On 07/23/2015 11:29 PM, Sascha Hauer wrote:
On Thu, Jul 23, 2015 at 02:07:59PM +0200, Pavel Machek wrote:
On Tue 2015-07-21 09:21:32, Sascha Hauer wrote:
The thermal code uses int, long and unsigned long for temperatures
in different places.
Dear Friend ,
I have a good business proposal for you ,
it's easy and no risk involve,
please get back to me for brief details
Regards
Alexander Flockhart
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More
This series adds PM support to pci-dra7xx so that PCI clocks can be disabled
during suspend and enabled back during resume without affecting
PCI functionality.
Changes from v1:
*) Moved resetting and setting of MSE bit to pci-dra7xx.
The comment to reset and set ISE is not done now since I don't
DRA7xx require MSE bit to be cleared to set the master in
standby mode. (In DRA7xx TRM_vE, section 24.9.4.5.2.2.1 PCIe
Controller Master Standby Behavior advises to use the clearing
of the local MSE bit to set the master in standby. Without this
some of the clocks do not idle).
Cleared the MSE
Fix the error handling code in case pm_runtime_get_sync fails. Now
when pm_runtime_get_sync fails pm_runtime_disable is invoked so that
there is no unbalanced pm_runtime_enable calls.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/pci/host/pci-dra7xx.c |4 +++-
1 file
Add PM support to pci-dra7xx so that PCI clocks can be disabled
during suspend and enabled back during resume without affecting
PCI functionality.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/pci/host/pci-dra7xx.c | 77 +
1 file
The following changes since commit f9d50fef4b6447527c2be1ad07499221c2511391:
ARM: OMAP2+: omap3-pandora: add wifi support (2015-07-21 04:07:42 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
tags/omap-for-v4.3/dt-dm814x
for
* Tony Lindgren t...@atomide.com [150724 05:09]:
SoC changes for omaps for v4.3 merge window:
- Clean-up omap4_local_timer_init to drop deal legacy code
And this typo translatges to drop dead leagcy code :)
Regards,
Tony
--
To unsubscribe from this list: send the line unsubscribe linux-omap
* Sekhar Nori nsek...@ti.com [150723 23:44]:
Hi Greg,
On Tuesday 14 July 2015 06:19 PM, Tony Lindgren wrote:
* Peter Hurley pe...@hurleysoftware.com [150714 05:24]:
On 07/14/2015 04:02 AM, Sekhar Nori wrote:
This series works around Advisory 21 as documented in
AM437x SoC errata[1].
* Sekhar Nori nsek...@ti.com [150714 01:05]:
Add ti,dra742-uart to the compatible list so the driver
workaround for UART module disable errata is enabled.
This does not break backward compatibility as existing DTBs
should continue to work with newer kernels albeit without the
capability to
The following changes since commit bc0195aad0daa2ad5b0d76cce22b167bc3435590:
Linux 4.2-rc2 (2015-07-12 15:10:30 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
tags/omap-for-v4.3/soc-signed
for you to fetch changes up to
43 matches
Mail list logo
