Hi,
On Tue, Jun 18, 2013 at 08:07:01PM +0300, Aaro Koskinen wrote:
+static ssize_t vbus_state_show(struct device *device,
+struct device_attribute *attr, char *buf)
+{
+ struct tahvo_usb *tu = dev_get_drvdata(device);
+ return sprintf(buf, %d\n,
On 06/29/2013 12:03 AM, Mike Turquette wrote:
Quoting Tero Kristo (2013-06-27 01:38:17)
cclock54xx_data.c now contains only init function and the clkdev mapping
that is still needed by some drivers. Eventually most of this file can
be removed, once a common location for the clk init can be
On Fri, Jun 21, 2013 at 10:46:10AM -0500, Ruchika Kharwar wrote:
Addition of the M and N recommended values for the USB3 PHY DPLL.
Sysclk for DRA7xx is 20MHz.
This yields:
Clk = 20MHz * M/(N+1) = 20MHz * 1000 /(7+1) = 2.5 Ghz
Signed-off-by: Nikhil Devshatwar nikhil...@ti.com
Signed-off-by:
On 06/29/2013 12:04 AM, Mike Turquette wrote:
Quoting Tero Kristo (2013-06-27 01:38:19)
cclock7xx_data.c now contains only init function and the clkdev mapping
that is still needed by some drivers. Eventually most of this file can
be removed, once a common location for the clk init can be
Hi,
On Fri, Apr 12, 2013 at 02:38:25PM +0200, Andreas Fenkart wrote:
Without functional clock the omap_hsmmc module can't forward
SDIO IRQs to the system. This patch reconfigures dat1 line as a
gpio while the fclk is off. It uses regulare SDIO IRQ detection of
the module, while fclk is
On Fri, Apr 12, 2013 at 02:38:26PM +0200, Andreas Fenkart wrote:
Signed-off-by: Andreas Fenkart andreas.fenk...@streamunlimited.com
-ENODESCRIPTION ??
Also, looking at the patch, I wonder if it really needs to be applied in
mainline. Seems like you only needed it to count how many times it went
On Fri, Apr 12, 2013 at 02:38:27PM +0200, Andreas Fenkart wrote:
PSTATE shows current state of data lines.
Signed-off-by: Andreas Fenkart andreas.fenk...@streamunlimited.com
this looks useful
Reviewed-by: Felipe Balbi ba...@ti.com
--
balbi
signature.asc
Description: Digital signature
On 07/06/2013 11:39 PM, Ezequiel Garcia wrote:
Hi Sebastian,
Hello Ezequiel,
On Fri, Jul 5, 2013 at 10:32 AM, Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
This enables the two musb instances on am335x to work.
I like a lot the idea of splitting the DT representation of the two
hi Ohad/all,
i am trying to find some real users of rpmsg, here i only get
samples/rpmsg/rpmsg_client_sample.c, does it mean other real drivers
are out of mainline? where could i get them?
i am also trying to find source codes running in Cortex-M3 which use
rpmsg and hope to find some Linux
On Fri, Jun 07, 2013 at 02:49:52PM -0700, Tony Lindgren wrote:
From: Andreas Fenkart andreas.fenk...@streamunlimited.com
Without functional clock the omap_hsmmc module can't forward SDIO IRQs to
the system. This patch reconfigures dat1 line as a gpio while the fclk is
off. When the fclk is
* Russell King - ARM Linux li...@arm.linux.org.uk [130706 06:42]:
Okay, I guessed that the OMAP4430SDP was blaze (it's not obvious to
use internal codenames for boards when they're known as SDP etc -
especially when they have stickers on them saying that they're SDP.)
Agreed, let's update
Remove usb phy control module access from platform glue.
The same is now done using am phy driver and phy-omap-control.
Signed-off-by: George Cherian george.cher...@ti.com
---
drivers/usb/musb/musb_dsps.c | 105 +++
1 file changed, 36 insertions(+), 69
Add API to power on/off USB PHY for AM335X. This API will be called
from phy-am-usb driver.
Signed-off-by: George Cherian george.cher...@ti.com
---
drivers/usb/phy/phy-omap-control.c | 32
include/linux/usb/omap_control_usb.h | 11 +++
2 files
From: Ravi Babu ravib...@ti.com
The dsps am33xx platform has two instances of musb controller,
enable the support for dual musb instances
Signed-off-by: Ravi Babu ravib...@ti.com
---
drivers/usb/musb/musb_dsps.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Add DT bindings of phy nodes for AM33XX platform.
Signed-off-by: George Cherian george.cher...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi | 22 ++
1 file changed, 22 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 8e1248f..4f3cca0
Adds phy driver support for am33xx platform, the host/device
peripheral controller shall get this phy object to control the phy
operations.
Signed-off-by: George Cherian george.cher...@ti.com
---
drivers/phy/Kconfig | 12 +++
drivers/phy/Makefile | 1 +
This patch series adds phy support for AM335X platform.
This patch series is based on Generic PHY framework [1].
This series has
- adds dual musb instances support for am335x platform (just for
testing)
- adds phy-am-usb driver used in AM platforms
- adds dt
commit 09fc7d (usb: musb: fix incorrect usage of resource pointer)
assumes musb core will always have only 2 resources. But for OMAP
platforms there can be 3 resources (2 irq resource and 1 iomem
resource). Fixed it here.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
After the devices are created using PLATFORM_DEVID_AUTO,
devm_usb_get_phy_dev and usb_get_phy_dev can't be used reliably
as it relies on the device_names passed in usb_bind_phy. So
added a new API to get the PHY reference by PHY label (PHY label
should be filled which creating the PHY).
Now that MUSB for OMAP started using devm_usb_get_phy_by_name
which does not require PHY library to already have the binding
information, removed usb_bind_phy calls that binds the MUSB controller
with the PHY from the board files.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Acked-by:
In order for controllers to get PHY in case of non dt boot, the phy
binding information (phy label) should be added in the platform
data of the controller.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
Tested-by: Tomi Valkeinen tomi.valkei...@ti.com
---
After the devices are created using PLATFORM_DEVID_AUTO,
devm_usb_get_phy_dev and usb_get_phy_dev can't be used reliably
as it relies on the device_names passed in usb_bind_phy. So used the
new API devm_usb_get_phy_by_name to get the PHY reference.
Signed-off-by: Kishon Vijay Abraham I
This series fixes the USB enumeration issue caused because of the controller
not able to get a reference to the PHY because of incorrect binding in the
board file.
In the case of non-dt boot, the platform specific initialization file
(board file) will do usb_bind_phy that binds the usb controller
* Bedia, Vaibhav vaibhav.be...@ti.com [130705 06:37]:
On Fri, Jul 05, 2013 at 18:50:10, Bedia, Vaibhav wrote:
Hi Tony,
On Fri, Jul 05, 2013 at 17:29:59, Tony Lindgren wrote:
* Bedia, Vaibhav vaibhav.be...@ti.com [130705 01:17]:
I just checked the behavior on my AM335x-EVM.
Hi,
On Monday 08 July 2013 04:13 PM, George Cherian wrote:
Add API to power on/off USB PHY for AM335X. This API will be called
from phy-am-usb driver.
Signed-off-by: George Cherian george.cher...@ti.com
---
drivers/usb/phy/phy-omap-control.c | 32
Hi,
On Monday 08 July 2013 04:13 PM, George Cherian wrote:
Adds phy driver support for am33xx platform, the host/device
peripheral controller shall get this phy object to control the phy
operations.
Signed-off-by: George Cherian george.cher...@ti.com
---
drivers/phy/Kconfig | 12
Hi,
On Monday 08 July 2013 04:13 PM, George Cherian wrote:
Add DT bindings of phy nodes for AM33XX platform.
Signed-off-by: George Cherian george.cher...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi | 22 ++
1 file changed, 22 insertions(+)
diff --git
Hi,
On Monday 08 July 2013 04:13 PM, George Cherian wrote:
Remove usb phy control module access from platform glue.
The same is now done using am phy driver and phy-omap-control.
Signed-off-by: George Cherian george.cher...@ti.com
---
drivers/usb/musb/musb_dsps.c | 105
* Tony Lindgren t...@atomide.com [130708 04:32]:
* Bedia, Vaibhav vaibhav.be...@ti.com [130705 06:37]:
On Fri, Jul 05, 2013 at 18:50:10, Bedia, Vaibhav wrote:
Hi Tony,
On Fri, Jul 05, 2013 at 17:29:59, Tony Lindgren wrote:
* Bedia, Vaibhav vaibhav.be...@ti.com [130705 01:17]:
Hello.
On 08-07-2013 14:55, Kishon Vijay Abraham I wrote:
commit 09fc7d (usb: musb: fix incorrect usage of resource pointer)
assumes musb core will always have only 2 resources. But for OMAP
platforms there can be 3 resources (2 irq resource and 1 iomem
resource). Fixed it here.
On Monday 08 July 2013 04:55 PM, Tony Lindgren wrote:
* Bedia, Vaibhav vaibhav.be...@ti.com [130705 06:37]:
On Fri, Jul 05, 2013 at 18:50:10, Bedia, Vaibhav wrote:
Hi Tony,
On Fri, Jul 05, 2013 at 17:29:59, Tony Lindgren wrote:
* Bedia, Vaibhav vaibhav.be...@ti.com [130705 01:17]:
I just
On 18/01/13 05:14, Mugunthan V N wrote:
On 1/18/2013 3:48 AM, Peter Korsgaard wrote:
When booting with CONFIG_ARM_APPENDED_DTB (either because of using an old
U-Boot, not wanting the hassle of 2 files or when using Falcon fast boot
mode in U-Boot), nothing updates the ethernet hwaddr specified
* Rajendra Nayak rna...@ti.com [130708 05:48]:
On Monday 08 July 2013 04:55 PM, Tony Lindgren wrote:
* Bedia, Vaibhav vaibhav.be...@ti.com [130705 06:37]:
On Fri, Jul 05, 2013 at 18:50:10, Bedia, Vaibhav wrote:
Hi Tony,
On Fri, Jul 05, 2013 at 17:29:59, Tony Lindgren wrote:
* Bedia,
On Monday 08 July 2013 06:40 PM, Tony Lindgren wrote:
* Rajendra Nayak rna...@ti.com [130708 05:48]:
On Monday 08 July 2013 04:55 PM, Tony Lindgren wrote:
* Bedia, Vaibhav vaibhav.be...@ti.com [130705 06:37]:
On Fri, Jul 05, 2013 at 18:50:10, Bedia, Vaibhav wrote:
Hi Tony,
On Fri, Jul 05,
On Monday 08 July 2013 06:50 PM, Rajendra Nayak wrote:
On Monday 08 July 2013 06:40 PM, Tony Lindgren wrote:
* Rajendra Nayak rna...@ti.com [130708 05:48]:
On Monday 08 July 2013 04:55 PM, Tony Lindgren wrote:
* Bedia, Vaibhav vaibhav.be...@ti.com [130705 06:37]:
On Fri, Jul 05, 2013 at
Hi,
On Mon, Jul 08, 2013 at 06:50:01PM +0530, Rajendra Nayak wrote:
I wonder if this is because the timeouts get now initialized to 0
instead
of -1 for the serial driver?
You meant initialized to -1, right? There's an additional check for
timeout being 0. Unless i
am missing
Add support for calculating message length in spi framework.
Add support for quad spi controller.
Patch 2 of this series had been posted before. Sending along
with the series along with ather propsed change.
Sourav Poddar (3):
driver: spi: Modify core to compute the message length
drivers:
Make spi core calculate the message length while
populating the other transfer parameters. This will
be useful in cases where controller driver need to configure its
framelength field without iterating through the linklist again in the
driver controller.
Signed-off-by: Sourav Poddar
The patch add basic support for the quad spi controller.
QSPI is a kind of spi module that allows single,
dual and quad read access to external spi devices. The module
has a memory mapped interface which provide direct interface
for accessing data form external spi devices.
The patch will
Since, qspi controller uses quad read.
Configuring the command register, if the transfer of data needs
quad lines.
This patch has been done on top of the following patch[1], which is still
under review/comments.
This patch will also go changes, as the parent patch[1] does.
[1]:
Hi,
On Mon, Jul 8, 2013 at 10:31 AM, Barry Song 21cn...@gmail.com wrote:
hi Ohad/all,
i am trying to find some real users of rpmsg, here i only get
samples/rpmsg/rpmsg_client_sample.c, does it mean other real drivers
are out of mainline?
Yes
where could i get them?
TI maintains them in
On Mon, Jul 08, 2013 at 02:34:11AM -0700, Tony Lindgren wrote:
* Russell King - ARM Linux li...@arm.linux.org.uk [130706 06:42]:
Okay, I guessed that the OMAP4430SDP was blaze (it's not obvious to
use internal codenames for boards when they're known as SDP etc -
especially when they have
Hi,
On Mon, Jul 08, 2013 at 07:12:59PM +0530, Sourav Poddar wrote:
+static inline unsigned long dra7xxx_readl(struct dra7xxx_qspi *qspi,
+ unsigned long reg)
+{
+ return readl(qspi-base + reg);
+}
+
+static inline void dra7xxx_writel(struct dra7xxx_qspi *qspi,
+
On 07/08/2013 02:28 AM, Felipe Balbi wrote:
On Fri, Jun 21, 2013 at 10:46:10AM -0500, Ruchika Kharwar wrote:
Addition of the M and N recommended values for the USB3 PHY DPLL.
Sysclk for DRA7xx is 20MHz.
This yields:
Clk = 20MHz * M/(N+1) = 20MHz * 1000 /(7+1) = 2.5 Ghz
Signed-off-by: Nikhil
On Mon, Jul 08, 2013 at 07:13:00PM +0530, Sourav Poddar wrote:
Since, qspi controller uses quad read.
Configuring the command register, if the transfer of data needs
quad lines.
This patch has been done on top of the following patch[1], which is still
under review/comments.
This patch
On Mon, Jul 08, 2013 at 07:12:58PM +0530, Sourav Poddar wrote:
Make spi core calculate the message length while
populating the other transfer parameters. This will
be useful in cases where controller driver need to configure its
framelength field without iterating through the linklist again
On 07/05/2013 12:47 PM, Mark Brown wrote:
On Fri, Jul 05, 2013 at 12:33:10PM -0500, Nishanth Menon wrote:
Taking an example of twl-regulator and omap_pmic, are you suggesting
omap_pmic to be a user twl-regulator using
include/linux/regulator/consumer.h? or are you suggesting that
omap_pmic
NanoBone Specification:
---
CPU:
TI AM335x @ 720MHz
Memory:
256MB DDR3
128MB NOR flash
128KB FRAM
Ethernet:
2 x 10/100 connected to SMSC LAN8710 PHY
USB:
1 x USB2.0 Type A
I2C:
2Kbit EEPROM (Microchip 24AA02)
RTC (Maxim DS1338)
GPIO Expander (Microchip
Hi,
On Mon, Jul 08, 2013 at 10:21:09AM +0300, Felipe Balbi wrote:
On Tue, Jun 18, 2013 at 08:07:01PM +0300, Aaro Koskinen wrote:
+static ssize_t vbus_state_show(struct device *device,
+ struct device_attribute *attr, char *buf)
+{
+ struct tahvo_usb *tu =
On 07/08/2013 12:43 PM, George Cherian wrote:
This patch series adds phy support for AM335X platform.
This patch series is based on Generic PHY framework [1].
This series has
- adds dual musb instances support for am335x platform (just for
testing)
- adds phy-am-usb
On 10:46-20130708, Felipe Balbi wrote:
On Sun, Jul 07, 2013 at 05:13:10PM -0300, Ezequiel Garcia wrote:
Hi guys,
On Fri, Jun 28, 2013 at 09:27:20PM +0530, Balaji T K wrote:
On Friday 28 June 2013 06:04 PM, a-bin...@ti.com wrote:
From: Amarinder Bindra a-bin...@ti.com
OMAP's
On Mon, Jul 08, 2013 at 02:58:28PM -0500, Nishanth Menon wrote:
On 10:46-20130708, Felipe Balbi wrote:
On Sun, Jul 07, 2013 at 05:13:10PM -0300, Ezequiel Garcia wrote:
Hi guys,
On Fri, Jun 28, 2013 at 09:27:20PM +0530, Balaji T K wrote:
On Friday 28 June 2013 06:04 PM, a-bin
On 19:12-20130708, Sourav Poddar wrote:
[..]
generic comment, given our historical mistakes of making drivers
specific to a SoC family, it never is.
Now, ti-qspi in file name is a step in the right direction, but, rest
of the code(function names etc) is just married to DRA7 family of
processor
Hi,
On Mon, Jul 08, 2013 at 09:44:33PM +0200, Sebastian Andrzej Siewior wrote:
We need two nodes each one with a glue layer and a musb child node. The
instances crap in kernel has to vanish. Also that means your phy nodes
are wrong. This is not musb with two ports but two musb instances each
On Monday 08 July 2013 07:05 PM, Felipe Balbi wrote:
Hi,
On Mon, Jul 08, 2013 at 06:50:01PM +0530, Rajendra Nayak wrote:
I wonder if this is because the timeouts get now initialized to 0
instead
of -1 for the serial driver?
You meant initialized to -1, right? There's an additional check
On 7/9/2013 1:14 AM, Sebastian Andrzej Siewior wrote:
On 07/08/2013 12:43 PM, George Cherian wrote:
This patch series adds phy support for AM335X platform.
This patch series is based on Generic PHY framework [1].
This series has
- adds dual musb instances support for am335x platform
56 matches
Mail list logo
