On Wed, Sep 23, 2015 at 03:48:34PM +0100, Ben Dooks wrote:
> On the OMAP AM3517 platform the uart4_ick gets registered
> twice, causing any power managment to /dev/ttyO3 to fail
> when trying to wake the device up.
>
> This solves the following oops:
>
> [] Unhandled fault: external abort on
On Sat, Aug 08, 2015 at 11:32:05AM +0200, Sebastian Andrzej Siewior wrote:
On 08/08/2015 02:28 AM, Peter Hurley wrote:
diff --git a/drivers/tty/serial/8250/8250_omap.c
b/drivers/tty/serial/8250/8250_omap.c
index 0340ee6ba970..07a11e0935e4 100644
--- a/drivers/tty/serial/8250/8250_omap.c
On Fri, Aug 07, 2015 at 10:41:57AM +0200, Sebastian Andrzej Siewior wrote:
This DMA driver is used by 8250-omap on DRA7-evm. There is one
requirement that is to pause a transfer. This is currently used on the RX
side. It is possible that the UART HW aborted the RX (UART's RX-timeout)
but the
On Fri, Apr 03, 2015 at 10:14:14AM -0500, Felipe Balbi wrote:
Hi Greg,
On Wed, Mar 25, 2015 at 02:18:37PM -0700, Tony Lindgren wrote:
Commit 3e457371f436 (usb: musb: Fix fifo reads for dm816x with musb_dsps)
fixed a USB error on dm816x, but introduced a new build error on i386
when
On Mon, Mar 23, 2015 at 05:38:44PM -0500, Doug Kehn wrote:
When wakeirq is not used/enabled, no wakeirq for uart0 is output for
all TTY as the log message is generated before the port line is
initialized.
[0.802656] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[0.811700]
On Wed, Jan 14, 2015 at 02:39:55PM +0530, Amit Virdi wrote:
Alright, I just applied your patches to testing/fixes. I'll start
testing today and should be able to send a pull request to Greg by the
end of the week, hopefully.
Thanks! Just a small clarification - git failed to send patches
On Mon, Sep 29, 2014 at 08:06:36PM +0200, Sebastian Andrzej Siewior wrote:
The queue is getting smaller. The highlights of v9…v10
- the DMA stall Frans Klaver reported which popped up in yocto is gone. It
also seems that the ack the err-irq even if nothing happened in EDMA
can be dropped.
On Mon, Oct 13, 2014 at 12:43:07PM +0100, Russell King - ARM Linux wrote:
On Mon, Oct 13, 2014 at 09:11:34AM +, David Laight wrote:
From: Nathan Lynch
On 10/10/2014 11:25 AM, Russell King - ARM Linux wrote:
Right, so GCC 4.8.{1,2} are totally unsuitable for kernel building (and
On Wed, Sep 17, 2014 at 11:05:06AM +0200, Sebastian Andrzej Siewior wrote:
On 2014-09-10 21:29:55 [+0200], Sebastian Andrzej Siewior wrote:
the diff of v8…v9 is small:
Greg, do you mind taking patches from this series up to [PATCH 05/16]?
Nobody complained about those so far and it would
On Fri, Sep 05, 2014 at 01:42:09AM +0400, Sergei Shtylyov wrote:
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
On Tue, Jul 22, 2014 at 01:08:38PM +0200, Enric Balletbo i Serra wrote:
Looks like the default location for TI firmware is inside the ti-connectivity
directory, to be coherent with other firmware request used by TI drivers, load
the TIInit firmware from this directory instead of /lib/firmware
On Tue, Jul 22, 2014 at 01:08:38PM +0200, Enric Balletbo i Serra wrote:
Looks like the default location for TI firmware is inside the ti-connectivity
directory, to be coherent with other firmware request used by TI drivers, load
the TIInit firmware from this directory instead of /lib/firmware
On Thu, Jul 10, 2014 at 08:54:18AM +0300, Ivaylo Dimitrov wrote:
On 9.07.2014 10:07, Tony Lindgren wrote:
* Suman Anna s-a...@ti.com [140708 11:40]:
Hi Peter,
On 07/08/2014 09:36 AM, Greg KH wrote:
On Tue, Jul 08, 2014 at 03:03:58PM +0200, Peter Meerwald wrote:
Hello,
Given
Ok, this has been fun to watch on lkml for a while now, but really,
please, just stop doing this. Randomly searching the kernel source for
FIXME lines and just commenting them out, isn't ok. Almost always,
those lines are there because the original developer really doesn't know
how else to
On Tue, Jul 08, 2014 at 03:03:58PM +0200, Peter Meerwald wrote:
Hello,
Given the total lack of response here, I suggest just deleting the
driver. No one has ever done the real work that is going to be
required to get this code out of staging. It has had build errors
causing it to
On Tue, Jul 08, 2014 at 09:58:39PM -0400, Nicholas Krause wrote:
This patch removes a fixme message in this file:wq for setting the usb 2
I don't think you did this correctly :)
speed on the board to the correct level. We need to depend on the
bootloader for doing this as the wires may be
On Thu, Jun 12, 2014 at 04:15:32PM +0200, Arnd Bergmann wrote:
On Thursday 12 June 2014 16:12:17 Laurent Pinchart wrote:
From 3a965f4fd5a6b3ef4a66aa4e7c916cfd34fd5706 Mon Sep 17 00:00:00 2001
From: Arnd Bergmann a...@arndb.de
Date: Tue, 21 Jan 2014 09:32:43 +0100
Subject: [PATCH]
On Thu, Jun 12, 2014 at 04:28:39PM +0200, Arnd Bergmann wrote:
On Thursday 12 June 2014 07:25:15 Greg KH wrote:
On Thu, Jun 12, 2014 at 04:15:32PM +0200, Arnd Bergmann wrote:
On Thursday 12 June 2014 16:12:17 Laurent Pinchart wrote:
From 3a965f4fd5a6b3ef4a66aa4e7c916cfd34fd5706 Mon Sep
On Thu, May 29, 2014 at 02:26:55PM +0530, Satish Patel wrote:
On 5/29/2014 12:14 AM, Greg KH wrote:
On Wed, May 28, 2014 at 02:27:13PM +0530, Satish Patel wrote:
+/**
+ * struct sc_phy - The basic smart card phy structure
+ *
+ * @dev: phy device
+ * @pdata: pointer to phy's private
On Thu, May 29, 2014 at 08:47:31AM -0500, Rob Herring wrote:
On Thu, May 29, 2014 at 3:34 AM, Satish Patel satish.pa...@ti.com wrote:
On 5/29/2014 12:23 AM, Greg KH wrote:
On Wed, May 28, 2014 at 02:27:13PM +0530, Satish Patel wrote:
SmartCard controller uses this interface
On Thu, May 29, 2014 at 02:07:59PM +0530, Satish Patel wrote:
On 5/29/2014 12:14 AM, Greg KH wrote:
On Wed, May 28, 2014 at 02:27:14PM +0530, Satish Patel wrote:
TDA8026 is a SmartCard PHY from NXP.
The PHY interfaces with the main processor over the
I2C interface and acts as a slave
On Wed, May 28, 2014 at 02:27:13PM +0530, Satish Patel wrote:
+/**
+ * struct sc_phy - The basic smart card phy structure
+ *
+ * @dev: phy device
+ * @pdata: pointer to phy's private data structure
+ * @set_config: called to set phy's configuration
+ * @get_config: called to get phy's
On Wed, May 28, 2014 at 02:27:14PM +0530, Satish Patel wrote:
TDA8026 is a SmartCard PHY from NXP.
The PHY interfaces with the main processor over the
I2C interface and acts as a slave device.
The driver also exposes the phy interface
(defined@include/linux/sc_phy.h) for SmartCard
On Wed, May 28, 2014 at 02:27:13PM +0530, Satish Patel wrote:
SmartCard controller uses this interface to communicate with
SmartCard via PHY
Some SmartCard PHY has multiple slots for cards.
This inerface also enables controller to communicate
with one or more SmartCard connected over phy.
On Fri, May 16, 2014 at 09:14:34AM +0530, Satish Patel wrote:
On 1/30/2014 6:35 PM, Greg KH wrote:
On Thu, Jan 30, 2014 at 11:22:48AM +0530, Satish Patel wrote:
On 1/20/2014 10:03 AM, Satish Patel wrote:
Changes from v1:
* RFC(v1) comments are fixed
** removed gpio_to_irq as GPIO
On Mon, Apr 14, 2014 at 01:46:11PM +0200, Robert Baldyga wrote:
This patchset adds many improvements to extcon class driver and extcon
provider drivers. It changes extcon API to faster and safer by replaceing
function taking extcon and cable names with functions working with
structures
On Thu, Apr 24, 2014 at 11:24:30AM +0200, yegorsli...@googlemail.com wrote:
This patch is based on Richard Genoud' patch adding generic GPIO support [1]
and my patch adding get_direction() functionality to OMAP's GPIO driver [2].
So far RTS/DTR are working both as modem control outputs and
On Tue, Apr 22, 2014 at 09:22:56AM -0500, Felipe Balbi wrote:
Hi,
On Thu, Mar 20, 2014 at 02:29:57PM -0500, Felipe Balbi wrote:
per CodingStyle we should have those braces, no
functional changes.
Signed-off-by: Felipe Balbi ba...@ti.com
Greg, do you want me to refresh and resend
On Mon, Apr 21, 2014 at 10:56:47AM -0500, Felipe Balbi wrote:
We only support GPL drivers in the USB Gadget Framework,
it sounds correct to make all exported symbols GPL too.
Signed-off-by: Felipe Balbi ba...@ti.com
Acked-by: Greg Kroah-Hartman gre...@linuxfoundation.org
--
To unsubscribe
On Mon, Apr 21, 2014 at 10:56:45AM -0500, Felipe Balbi wrote:
by removing the _relaxed suffix, we can build
this driver in other architectures.
Odd, why was the _relaxed variants used here at all? Someone trying to
optimize something ahead of time?
greg k-h
--
To unsubscribe from this list:
On Fri, Mar 21, 2014 at 12:36:53PM -0500, Felipe Balbi wrote:
Hi,
On Fri, Mar 21, 2014 at 10:10:30AM -0700, Tony Lindgren wrote:
On the support side, I'm not looking forward to this for beagle/panda
users. We've already converted them once from ttySx - ttyOx back in
2.6.33/2.6.34?
On Thu, Mar 20, 2014 at 06:52:10PM -0500, Felipe Balbi wrote:
Hi folks,
I've been toying with the idea of removing
drivers/tty/serial/omap-serial.c since that's, to put it bluntly, an
ungly copy of 8250 driver.
The original concern was wrt suspend/resume but I think it'd be a far
better
On Thu, Mar 20, 2014 at 08:37:29PM -0500, Felipe Balbi wrote:
On Thu, Mar 20, 2014 at 08:35:57PM -0500, Felipe Balbi wrote:
Hi,
On Thu, Mar 20, 2014 at 05:12:28PM -0700, Greg KH wrote:
On Thu, Mar 20, 2014 at 06:52:10PM -0500, Felipe Balbi wrote:
Hi folks,
I've been toying
On Tue, Feb 18, 2014 at 10:20:54AM -0600, Felipe Balbi wrote:
On Fri, Jan 17, 2014 at 10:22:35AM +0100, Markus Pargmann wrote:
debugfs files to show the contents of important dsps registers.
Signed-off-by: Markus Pargmann m...@pengutronix.de
---
drivers/usb/musb/musb_dsps.c | 54
On Tue, Feb 18, 2014 at 11:03:35AM -0600, Felipe Balbi wrote:
On Tue, Feb 18, 2014 at 08:59:11AM -0800, Greg KH wrote:
On Tue, Feb 18, 2014 at 10:20:54AM -0600, Felipe Balbi wrote:
On Fri, Jan 17, 2014 at 10:22:35AM +0100, Markus Pargmann wrote:
debugfs files to show the contents
On Tue, Feb 04, 2014 at 03:25:47PM +0200, Roger Quadros wrote:
Hi Greg,
Patch 1 fixes SuperSpeed hub enumeration on beaglebone.
Patch 2 fixes remote-wakeup resume on beaglebone.
Felipe has Acked the 1st patch but still needs to Ack the 2nd one.
Patches are based on 3.14-rc1
Why
On Thu, Jan 30, 2014 at 11:22:48AM +0530, Satish Patel wrote:
On 1/20/2014 10:03 AM, Satish Patel wrote:
Changes from v1:
* RFC(v1) comments are fixed
** removed gpio_to_irq as GPIO controller process cell from DT and
give it to DT node
** comments on documentation
** few other
On Fri, Oct 04, 2013 at 01:46:08PM +0300, Roger Quadros wrote:
Greg,
On 10/03/2013 06:41 PM, Greg KH wrote:
On Thu, Oct 03, 2013 at 05:54:14PM +0300, Roger Quadros wrote:
On 10/03/2013 03:29 PM, Felipe Balbi wrote:
Hi,
On Wed, Oct 02, 2013 at 04:41:53PM +0300, Roger Quadros wrote
On Thu, Oct 03, 2013 at 05:54:14PM +0300, Roger Quadros wrote:
On 10/03/2013 03:29 PM, Felipe Balbi wrote:
Hi,
On Wed, Oct 02, 2013 at 04:41:53PM +0300, Roger Quadros wrote:
On 10/02/2013 04:11 PM, Felipe Balbi wrote:
On Mon, Sep 23, 2013 at 04:11:30PM +0300, Roger Quadros wrote:
Hi
On Fri, Sep 27, 2013 at 11:53:24AM +0530, Kishon Vijay Abraham I wrote:
Added a generic PHY framework that 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.
This framework will be of
On Wed, Aug 21, 2013 at 11:16:07AM +0530, Kishon Vijay Abraham I wrote:
Used the generic PHY framework API to create the PHY. Now the power off and
power on are done in omap_usb_power_off and omap_usb_power_on respectively.
The omap-usb2 driver is also moved to driver/phy.
However using the
On Fri, Sep 20, 2013 at 11:04:40AM +0530, Kishon Vijay Abraham I wrote:
Hi Greg,
On Tuesday 17 September 2013 09:11 PM, Felipe Balbi wrote:
On Wed, Sep 04, 2013 at 02:27:06PM +0530, Kishon Vijay Abraham I wrote:
On Tuesday 03 September 2013 09:20 PM, Greg KH wrote:
On Tue, Sep 03, 2013
On Mon, Sep 09, 2013 at 03:45:50PM +0200, Koen Kooi wrote:
The BeagleBone Black is basically a regular BeagleBone with eMMC and HDMI
added,
so create a common dtsi both can use.
IMPORTANT: booting the existing am335x-bone.dts will blow up the HDMI
transceiver
after a dozen boots with an
On Tue, Sep 03, 2013 at 08:55:23PM +0530, Kishon Vijay Abraham I wrote:
Hi Greg,
On Wednesday 28 August 2013 12:50 AM, Felipe Balbi wrote:
Hi,
On Mon, Aug 26, 2013 at 01:44:49PM +0530, Kishon Vijay Abraham I wrote:
On Wednesday 21 August 2013 11:16 AM, Kishon Vijay Abraham I wrote:
On Tue, Aug 27, 2013 at 07:30:19AM -0700, Kevin Hilman wrote:
Greg,
On Tue, Aug 20, 2013 at 8:44 AM, Kevin Hilman khil...@linaro.org wrote:
+Felipe
On Wed, Jul 17, 2013 at 6:29 AM, Alexander Savchenko
oleksandr.savche...@ti.com wrote:
From: Ruchika Kharwar ruch...@ti.com
Ensure
On Tue, Aug 13, 2013 at 12:54:47PM +0200, Javier Martinez Canillas wrote:
On Tue, Aug 13, 2013 at 12:22 PM, Mark Jackson mpfj-l...@newflow.co.uk
wrote:
On 12/08/13 23:56, Greg KH wrote:
On Sun, Aug 11, 2013 at 02:56:50PM +0100, Mark Jackson wrote:
This patch adds RS485 support to the OMAP
On Tue, Aug 13, 2013 at 12:07:01PM +0100, Mark Jackson wrote:
On 13/08/13 11:54, Javier Martinez Canillas wrote:
snip
Hi Mark,
I've seen several attempts to add RS485 support to the omap serial
driver and it is always nack-ed. There seems to be concerns about
controlling the
On Tue, Aug 13, 2013 at 11:22:54AM +0100, Mark Jackson wrote:
On 12/08/13 23:56, Greg KH wrote:
On Sun, Aug 11, 2013 at 02:56:50PM +0100, Mark Jackson wrote:
This patch adds RS485 support to the OMAP serial driver, as
defined in:-
Documentation/devicetree/bindings/serial/rs485.txt
On Sun, Aug 11, 2013 at 02:56:50PM +0100, Mark Jackson wrote:
This patch adds RS485 support to the OMAP serial driver, as
defined in:-
Documentation/devicetree/bindings/serial/rs485.txt
When a UART transmitter is connected to (eg) a RS485 driver, it is
necessary to turn the driver on/off
On Tue, Aug 06, 2013 at 06:25:32PM +0530, Bharathraj Nagaraju wrote:
Dear All,
We are working on omap4470 based device,kernel-3.0.31 is running on this.
Have you tried the 3.10 kernel for this? I think you might find that
this already is resolved there, as lots of pm USB work has
On Fri, Jul 26, 2013 at 06:19:16PM +0530, Kishon Vijay Abraham I wrote:
+static int phy_get_id(void)
+{
+ int ret;
+ int id;
+
+ ret = ida_pre_get(phy_ida, GFP_KERNEL);
+ if (!ret)
+ return -ENOMEM;
+
+ ret = ida_get_new(phy_ida, id);
+ if (ret 0)
+
On Tue, Jul 30, 2013 at 11:15:20AM +0300, Felipe Balbi wrote:
look at Greg's and my reply to that email.
but finally Greg agreed to what Tomasz proposed no?
that's not what I see in the thread. I see Greg agreed to regulator's
own IDs being sequentially created, but he mentions device
On Tue, Jul 23, 2013 at 08:48:24PM +0530, Kishon Vijay Abraham I wrote:
Hi,
On Tuesday 23 July 2013 08:07 PM, Alan Stern wrote:
On Tue, 23 Jul 2013, Tomasz Figa wrote:
On Tuesday 23 of July 2013 09:29:32 Tomasz Figa wrote:
Hi Alan,
Thanks for helping to clarify the issues here.
On Tue, Jul 23, 2013 at 09:58:34PM +0530, Kishon Vijay Abraham I wrote:
Hi Greg,
On Tuesday 23 July 2013 09:48 PM, Greg KH wrote:
On Tue, Jul 23, 2013 at 08:48:24PM +0530, Kishon Vijay Abraham I wrote:
Hi,
On Tuesday 23 July 2013 08:07 PM, Alan Stern wrote:
On Tue, 23 Jul 2013
On Tue, Jul 23, 2013 at 06:50:29PM +0200, Tomasz Figa wrote:
Ick, no. Why can't you just pass the pointer to the phy itself? If you
had a priv pointer to search from, then you could have just passed the
original phy pointer in the first place, right?
IMHO it would be better if you
On Tue, Jul 23, 2013 at 06:44:56PM +0100, Mark Brown wrote:
On Tue, Jul 23, 2013 at 10:37:11AM -0700, Greg KH wrote:
On Tue, Jul 23, 2013 at 06:50:29PM +0200, Tomasz Figa wrote:
I fully agree that a simple, single string will not scale even in some,
not
so uncommon cases
On Tue, Jul 23, 2013 at 07:48:11PM +0200, Tomasz Figa wrote:
On Tuesday 23 of July 2013 10:37:11 Greg KH wrote:
On Tue, Jul 23, 2013 at 06:50:29PM +0200, Tomasz Figa wrote:
Ick, no. Why can't you just pass the pointer to the phy itself? If
you
had a priv pointer to search from
On Tue, Jul 23, 2013 at 08:31:05PM +0100, Mark Brown wrote:
You don't know the id of the device you are looking up, due to
multiple devices being in the system (dynamic ids, look back earlier in
this thread for details about that.)
I got copied in very late so don't have most of the
On Tue, Jul 23, 2013 at 10:07:52PM +0200, Tomasz Figa wrote:
On Tuesday 23 of July 2013 12:44:23 Greg KH wrote:
On Tue, Jul 23, 2013 at 08:31:05PM +0100, Mark Brown wrote:
You don't know the id of the device you are looking up, due to
multiple devices being in the system (dynamic ids
On Tue, Jul 23, 2013 at 11:05:48PM +0200, Tomasz Figa wrote:
That's not so bad, as long as you let the phy core use whatever name it
wants for the device when it registers it with sysfs.
Yes, in regulator core consumer names are completely separated from this.
Regulator core simply
On Mon, Jul 22, 2013 at 12:55:18PM +0530, Kishon Vijay Abraham I wrote:
The issue (or one of the issues) in this discussion is that
Greg does not like the idea of using names or IDs to associate
PHYs with controllers, because they are too prone to
duplications or other
On Sun, Jul 21, 2013 at 01:12:07PM +0200, Tomasz Figa wrote:
On Sunday 21 of July 2013 16:37:33 Kishon Vijay Abraham I wrote:
Hi,
On Sunday 21 July 2013 04:01 PM, Tomasz Figa wrote:
Hi,
On Saturday 20 of July 2013 19:59:10 Greg KH wrote:
On Sat, Jul 20, 2013 at 10:32:26PM
On Sun, Jul 21, 2013 at 12:22:48PM +0200, Sascha Hauer wrote:
On Sat, Jul 20, 2013 at 07:59:10PM -0700, Greg KH wrote:
On Sat, Jul 20, 2013 at 10:32:26PM -0400, Alan Stern wrote:
On Sat, 20 Jul 2013, Greg KH wrote:
That should be passed using platform data.
Ick, don't
On Sat, Jul 20, 2013 at 08:49:32AM +0530, Kishon Vijay Abraham I wrote:
Hi,
On Saturday 20 July 2013 05:20 AM, Greg KH wrote:
On Fri, Jul 19, 2013 at 12:06:01PM +0530, Kishon Vijay Abraham I wrote:
Hi,
On Friday 19 July 2013 11:59 AM, Greg KH wrote:
On Fri, Jul 19, 2013 at 11:25:44AM
On Sat, Jul 20, 2013 at 10:32:26PM -0400, Alan Stern wrote:
On Sat, 20 Jul 2013, Greg KH wrote:
That should be passed using platform data.
Ick, don't pass strings around, pass pointers. If you have platform
data you can get to, then put the pointer there, don't use a name
On Fri, Jul 19, 2013 at 11:25:44AM +0530, Kishon Vijay Abraham I wrote:
Hi,
On Friday 19 July 2013 11:13 AM, Greg KH wrote:
On Fri, Jul 19, 2013 at 11:07:10AM +0530, Kishon Vijay Abraham I wrote:
+ ret = dev_set_name(phy-dev, %s.%d, dev_name(dev), id);
Your naming is odd, no phy
On Fri, Jul 19, 2013 at 12:06:01PM +0530, Kishon Vijay Abraham I wrote:
Hi,
On Friday 19 July 2013 11:59 AM, Greg KH wrote:
On Fri, Jul 19, 2013 at 11:25:44AM +0530, Kishon Vijay Abraham I wrote:
Hi,
On Friday 19 July 2013 11:13 AM, Greg KH wrote:
On Fri, Jul 19, 2013 at 11:07:10AM
On Thu, Jul 18, 2013 at 11:33:17AM +0530, Kishon Vijay Abraham I wrote:
Wanted to group all the PHY drivers to be used by different subsystems
(SATA/USB/PCIE/HDMI/VIDEO) into a single entity. There were some comments
in my
initial version [3] on using a bus_type instead of class but then
On Thu, Jul 18, 2013 at 12:16:10PM +0530, Kishon Vijay Abraham I wrote:
+struct phy_provider *__of_phy_provider_register(struct device *dev,
+ struct module *owner, struct phy * (*of_xlate)(struct device *dev,
+ struct of_phandle_args *args));
+struct phy_provider
On Thu, Jul 18, 2013 at 12:16:11PM +0530, Kishon Vijay Abraham I wrote:
Used the generic PHY framework API to create the PHY. Now the power off and
power on are done in omap_usb_power_off and omap_usb_power_on respectively.
However using the old USB PHY library cannot be completely removed
On Thu, Jul 18, 2013 at 02:29:52PM +0530, Kishon Vijay Abraham I wrote:
Hi,
On Thursday 18 July 2013 12:50 PM, Greg KH wrote:
On Thu, Jul 18, 2013 at 12:16:10PM +0530, Kishon Vijay Abraham I wrote:
+struct phy_provider *__of_phy_provider_register(struct device *dev,
+ struct module
On Fri, Jul 19, 2013 at 11:07:10AM +0530, Kishon Vijay Abraham I wrote:
+ret = dev_set_name(phy-dev, %s.%d, dev_name(dev), id);
Your naming is odd, no phy anywhere in it? You rely on the sender to
never send a duplicate name.id pair? Why not create your own ids based
on the
On Wed, Jun 26, 2013 at 05:17:29PM +0530, Kishon Vijay Abraham I wrote:
+menuconfig GENERIC_PHY
+ tristate PHY Subsystem
+ help
+ Generic PHY support.
+
+ This framework is designed to provide a generic interface for PHY
+ devices present in the kernel. This layer
On Wed, Jul 17, 2013 at 03:02:59PM +0530, Kishon Vijay Abraham I wrote:
Hi,
On Wednesday 17 July 2013 11:59 AM, Greg KH wrote:
On Wed, Jun 26, 2013 at 05:17:29PM +0530, Kishon Vijay Abraham I wrote:
+menuconfig GENERIC_PHY
+ tristate PHY Subsystem
+ help
+Generic PHY support
On Fri, May 31, 2013 at 02:29:01PM +0300, Roger Quadros wrote:
Hi,
Improve Kconfig so that the relevant PHY driver can be explicitely
selected by the controller driver instead of relying on the user
to do so.
Detailed description in patch 1.
Felipe needs to take these, not I.
thanks,
On Thu, May 23, 2013 at 05:46:44PM +0300, Roger Quadros wrote:
On 05/23/2013 05:11 PM, Alan Stern wrote:
On Thu, 23 May 2013, Roger Quadros wrote:
Device tree probed devices don't get dma_mask set. Previously
we were setting the dma_mask pointer only if it was NULL.
However, the
On Wed, May 15, 2013 at 08:13:09PM +0530, Sourav Poddar wrote:
Hi Greg,
On Saturday 27 April 2013 03:48 AM, Greg KH wrote:
On Fri, Apr 26, 2013 at 03:03:07PM -0700, Kevin Hilman wrote:
Hi Greg,
Sourav Poddarsourav.pod...@ti.com writes:
Move uart_console definition to serial core header
On Tue, May 14, 2013 at 06:07:01PM +0200, jp.franc...@cynove.com wrote:
_enable_preprogram is marked as __init, but is called from _enable which is
not.
This results in oops once init is freed.
Fix this by removing the __init marker.
Signed-off-by: Jean-Philippe François
On Fri, Apr 26, 2013 at 03:03:07PM -0700, Kevin Hilman wrote:
Hi Greg,
Sourav Poddar sourav.pod...@ti.com writes:
Move uart_console definition to serial core header file, so that it can be
used by serial drivers.
Get rid of the uart_console defintion from mpc52xx_uart driver.
Cc:
On Wed, Apr 03, 2013 at 08:16:18PM +, Paul Walmsley wrote:
Hi Greg, Alexey,
On Wed, 3 Apr 2013, Alexey Pelykh wrote:
From: Alexey Pelykh alexey.pel...@gmail.com
Partially reverts 1776fd059c40907297d6c26c51876575d63fd9e2
that introduced regression reported by Paul Walmsley.
On Tue, Mar 19, 2013 at 10:54:25AM -0400, Eduardo Valentin wrote:
This patch updates the documentation to remove
all warnings and errors reported by scripts/kernel-doc.
Most are missing arguments due to wrong format.
Cc: Nishanth Menon n...@ti.com
Signed-off-by: Eduardo Valentin
On Sat, Mar 16, 2013 at 08:46:03AM -0400, Eduardo Valentin wrote:
Hello Dan,
On 16-03-2013 05:05, Dan Carpenter wrote:
I've reviewed this set.
I hate to make people redo whole patchset sets, and I hate
re-reviewing code. Obviously, I don't really like the bunny hop
patches and I'm
On Mon, Mar 11, 2013 at 10:35:57AM +0530, Lokesh Vutla wrote:
This series resolves a few minor issues for EMIF driver.
Tested all patches on OMAP4430-sdp.
Patch : memory: emif: setup LP settings on freq update
is tested on a local tree, since freq update cannot be
tested on mainline.
Can
On Thu, Feb 14, 2013 at 02:14:11PM +0200, Roger Quadros wrote:
Hi Greg,
This pull request contains 2 bug fixes for ehci-omap for 3.9 as well
as older kernels. It is based on 3.8-rc6.
Please pull. Thanks.
The following changes since commit 88b62b915b0b7e25870eb0604ed9a92ba4bfc9f7:
On Tue, Nov 27, 2012 at 11:30:11AM -0500, Alan Stern wrote:
On Tue, 27 Nov 2012, Ming Lei wrote:
IMO, all matches mean the devices are inside the ehci-omap bus, so
the direct/simple way is to enable/disable the regulators in the probe() and
remove() of ehci-omap controller driver.
When
On Mon, Nov 26, 2012 at 12:45:34PM +, Andy Green wrote:
+struct device_path list;
+DEFINE_MUTEX(lock);
Those are some very descriptive global variables you just created :(
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to
On Mon, Nov 26, 2012 at 12:45:34PM +, Andy Green wrote:
This adds a small optional API into drivers/base which deals with generating,
matching and registration of wildcard device paths.
From a struct device * you can generate a string like
/platform/usbhs_omap/ehci-omap.0/usb1/1-1
On Mon, Nov 26, 2012 at 12:45:45PM +, Andy Green wrote:
This adds the config option to associate a regulator with each hub,
when the hub on a specific, interesting device path appears, then
the regular is powered while the logical hub exists.
Signed-off-by: Andy Green
On Mon, Nov 26, 2012 at 11:22:06AM -0800, Greg KH wrote:
On Mon, Nov 26, 2012 at 12:45:34PM +, Andy Green wrote:
This adds a small optional API into drivers/base which deals with
generating,
matching and registration of wildcard device paths.
From a struct device * you can
On Mon, Nov 26, 2012 at 04:07:38PM -0500, Alan Stern wrote:
On Mon, 26 Nov 2012, Greg KH wrote:
Ah, here's the root of your problem, right? You need a way for your
hardware to tell the kernel that you have a regulator attached to a
specific device? Using the device path and hard-coding
On Wed, Nov 07, 2012 at 10:56:59AM +0100, Andreas Bießmann wrote:
On 16.10.2012 16:09, Felipe Balbi wrote:
This reverts commit 957ee7270d632245b43f6feb0e70d9a5e9ea6cf6
(serial: omap: fix software flow control).
As Russell has pointed out, that commit isn't fixing
Software Flow Control
On Thu, Nov 15, 2012 at 06:00:58PM -0600, Rob Clark wrote:
This patch changes the omapdrm KMS to bypass the omapdss compat
layer and use the core omapdss API directly. This solves some layering
issues that would cause unpin confusion vs GO bit status, because we
would not know whether a
On Fri, Nov 16, 2012 at 10:17:19AM +0200, Felipe Balbi wrote:
Hi,
On Fri, Nov 16, 2012 at 12:07:54PM +0530, Kishon Vijay Abraham I wrote:
commit 392142 moved event buffer allocation out of dwc3_core_init() but
event buffer allocation uses the cached copy of hwparams to determine
the
On Wed, Oct 24, 2012 at 01:02:55PM +0300, Felipe Balbi wrote:
Hi Greg,
On Tue, Oct 16, 2012 at 08:13:59AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [121016 07:16]:
This reverts commit 957ee7270d632245b43f6feb0e70d9a5e9ea6cf6
(serial: omap: fix software flow control).
On Mon, Oct 15, 2012 at 09:49:20AM +0200, Sebastian Andrzej Siewior wrote:
On 10/12/2012 06:39 PM, Fengguang Wu wrote:
Hi Sebastian,
Hi Fengguang,
FYI, kernel build failed on
tree: git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git
merge-result-for-greg
head:
On Wed, Sep 26, 2012 at 03:09:03PM +0530, Thirumalesha N wrote:
Dear Sir/Madam,
I'm testing PMC type SM502 based Graphics card which has usb,
audio and display interfaces.
I'm using kernel version linux-2.6.21 with redhat enterprise 5.5
OS.
As you are testing
On Wed, Sep 26, 2012 at 08:31:15PM +0530, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of API's for the PHY drivers to
create/destroy a PHY and API's for the PHY users to obtain a reference to the
PHY with or without using phandle. To obtain a reference to the PHY without
On Mon, Sep 17, 2012 at 12:53:18PM +0530, AnilKumar Ch wrote:
Adds device tree support to lis3lv02d_i2c driver. Along with this
DT init is moved from core driver to individual drivers, with the
current implementation some pdata is missing in lis3lv02d_i2c driver.
Also adds platform data for
On Tue, Sep 25, 2012 at 01:52:03PM +0530, Poddar, Sourav wrote:
Hi Greg,
Ping on this?
It was a RFT patch, with a huge thread. What's the resolution here?
Did people figure out the real problem here or not? If so, care to
resend the proper patch so I know what to apply?
thanks,
greg k-h
On Wed, Sep 26, 2012 at 01:34:50PM -0700, Andrew Morton wrote:
On Wed, 26 Sep 2012 13:24:00 -0700
Greg KH gre...@linuxfoundation.org wrote:
On Mon, Sep 17, 2012 at 12:53:18PM +0530, AnilKumar Ch wrote:
Adds device tree support to lis3lv02d_i2c driver. Along with this
DT init is moved
1 - 100 of 340 matches
Mail list logo
