* Rajendra Nayak rna...@ti.com [130704 22:49]:
On Thursday 04 July 2013 10:14 PM, Paul Walmsley wrote:
You mentioned that these patches were generated with some kind of awk/grep
scripting. Can you integrate that in an automated way into the
autogeneration flow? If the answer is yes,
Please call the helpdesk x14357 for assistance in sending out this work related
attachment.
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Jul 04, 2013 at 21:30:14, Mark Jackson wrote:
On 04/07/13 16:14, Mark Jackson wrote:
On 04/07/13 14:25, Mark Jackson wrote:
Our custom AM335x board has been booting just fine under 3.10.0-rc4.
I've just done a git pull to update to 3.10 (now that it's released)
and the board now
Over the years the PRM and CM headers for OMAP have been growing largely
due to autogeneration which creates headers for complete PRM and
CM register space, regardless of the actual usage of these registers in
the kernel.
The PRM and CM regbit headers in particular were found to be around
90%
Cleanup unused parts of the PRM and CM regbit headers leaving only whats
used.
Signed-off-by: Rajendra Nayak rna...@ti.com
---
arch/arm/mach-omap2/cm-regbits-24xx.h | 318
arch/arm/mach-omap2/prm-regbits-24xx.h | 247 -
2 files changed,
* Bedia, Vaibhav vaibhav.be...@ti.com [130705 01:17]:
On Thu, Jul 04, 2013 at 21:30:14, Mark Jackson wrote:
On 04/07/13 16:14, Mark Jackson wrote:
On 04/07/13 14:25, Mark Jackson wrote:
Our custom AM335x board has been booting just fine under 3.10.0-rc4.
I've just done a git pull to
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. Current mainline boots fine
provided I don't use earlyprintk. The offending patch [1] in this case is
the one
that
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. Current mainline boots fine
provided I don't use earlyprintk.
The am335x PHY code is well hidden in multiple places. The glue layer
uses the nop and does up/down in the background. This patch copies the
power on / power off part out of dsps so it can be removed later in
dsps. At this point I am not sure if it is better to write a new phy
driver for am335x or
This enables the two musb instances on am335x to work.
Could someone explain what
ti,hwmods = usb_otg_hs;
doing? I would want to have something like
| musb {
|/* glue /*
| {
| musb child node
|}
| }
and this twice. This would put the glue layer
The memory address contains three pieces that is the reset module which
is currently the only one used and two other pices which seem
interresting based on what the register.
The phy id (0 or 1) can be obtained via of_alias_get_id(). However once
we need this, we should used something for common
This moves the two instances from the big node into two child nodes. The
glue layer ontop does almost nothing.
This could be two indepentant child nodes but I have no idea how
'ti,hwmods = usb_otg_hs;' affects the two musb controler.
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
Remove the instances variable, there is no single use of it.
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
drivers/usb/musb/musb_dsps.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/usb/musb/musb_dsps.c b/drivers/usb/musb/musb_dsps.c
index 0e01cc1..edeb2ad
dsps uses a nop driver which is added in dsps itself and does the PHY
on/off calls within dsps. Since those calls are now moved the nop driver
itself, we can now request the phy proper phy and remove those calls.
Currently only the first musb interface is used so we only add one phy
node for now.
On 16:41-20130704, Mark Brown wrote:
On Fri, Jun 21, 2013 at 04:25:42PM -0500, Nishanth Menon wrote:
+static const struct omap_pmic_info omap_twl4030_vdd1 = {
+ .slave_addr = 0x12,
+ .voltage_reg_addr = 0x00,
+ .cmd_reg_addr = 0x00,
+ .i2c_timeout_us = 200,
+ .slew_rate_uV
On Fri, Jul 05, 2013 at 08:55:07AM -0500, Nishanth Menon wrote:
Please write in paragraphs, an enormous wall of unbroken text isn't
helpful for legibility.
On 16:41-20130704, Mark Brown wrote:
So, this still has the thing where all the data about the PMIC is
replicated (but now in this
On 07/05/2013 01:48 AM, Rajendra Nayak wrote:
On Thursday 04 July 2013 11:42 PM, Paul Walmsley wrote:
On Wed, 3 Jul 2013, Paul Walmsley wrote:
As far as Lokesh's patch goes: it doesn't make sense to me to remove a
file during 'make clean' that the build process doesn't create. So while
I
On 07/04/2013 01:26 AM, Ruchika Kharwar wrote:
DRA7XX has several USB OTG subsystems. USB_OTG_SS1 includes a USB1 and USB2
phy. USB_OTG_SS2 includes only a USB2 phy.
This patch allows the dwc3 probe to continue if a usb3_phy is not found.
The need for this will go away as soon as
On 07/05/2013 08:32 AM, Sebastian Andrzej Siewior wrote:
The memory address contains three pieces that is the reset module which
is currently the only one used and two other pices which seem
interresting based on what the register.
Please fix typos pices.. interresting.. also the description
On 07/05/2013 04:41 PM, Ruchika Kharwar wrote:
On 07/05/2013 08:32 AM, Sebastian Andrzej Siewior wrote:
The memory address contains three pieces that is the reset module which
is currently the only one used and two other pices which seem
interresting based on what the register.
Please fix
On 07/05/2013 09:08 AM, Mark Brown wrote:
On Fri, Jul 05, 2013 at 08:55:07AM -0500, Nishanth Menon wrote:
Please write in paragraphs, an enormous wall of unbroken text isn't
helpful for legibility.
Apologies on the same. Will try to do better.
On 16:41-20130704, Mark Brown wrote:
So,
Hi Sebastian,
2013/7/5 Sebastian Andrzej Siewior bige...@linutronix.de:
This moves the two instances from the big node into two child nodes. The
glue layer ontop does almost nothing.
This could be two indepentant child nodes but I have no idea how
'ti,hwmods = usb_otg_hs;' affects the two
Register target address to be used for cpgmac is the second device
address space. By default, hwmod picks first address space (0th index)
for register target.
With removal of address space from hwmod and using DT instead, cpgmac
is getting wrong address space for register target.
Fix it by
Address space is being removed from hwmod database and DT information
in reg property is being used. Currently the 0th index of device
address space is used to map for register target address. This is not
always true, eg. cpgmac has it's sysconfig in second address space.
Handle it by specifying
On 07/05/2013 05:08 PM, Enric Balletbo Serra wrote:
Hi Sebastian,
Hi Enric,
I'm trying to test these patches but I've problems, I've following error,
[ 10.096492] musb-dsps 4740.usb: failed to get memory for instance 0
[ 10.103481] musb-dsps 4740.usb: failed to create child
2013/7/5 Sebastian Andrzej Siewior bige...@linutronix.de:
On 07/05/2013 05:08 PM, Enric Balletbo Serra wrote:
Hi Sebastian,
Hi Enric,
I'm trying to test these patches but I've problems, I've following error,
[ 10.096492] musb-dsps 4740.usb: failed to get memory for instance 0
[
On 07/05/2013 05:22 PM, Enric Balletbo Serra wrote:
Fixed, I didn't update my DT for my custom board properly. Thanks.
Good. I hate breaking the compatibility for DT but unfortunately it is
beyond repair.
Sebastian
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the
On Fri, 5 Jul 2013, Rajendra Nayak wrote:
Grant already made it clear when he posted that patch that neither that nor
anything similar would be taken up mainline because the appended dtb was only
meant for folks stuck with legacy bootloaders and have no way to upgrade.
He's not the final
On Fri, Jul 05, 2013 at 09:50:34AM -0500, Nishanth Menon wrote:
On 07/05/2013 09:08 AM, Mark Brown wrote:
option 1) we just bypass get_voltage/set_voltage to point through to
this function. result will be something similar to what we got here[1]
I don't really know what you mean when you say
On 07/05/2013 11:52 AM, Mark Brown wrote:
On Fri, Jul 05, 2013 at 09:50:34AM -0500, Nishanth Menon wrote:
On 07/05/2013 09:08 AM, Mark Brown wrote:
option 1) we just bypass get_voltage/set_voltage to point through to
this function. result will be something similar to what we got here[1]
I
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 should not be a regulator at all?
No, I'm
IGEP Processor Boards based on OMAP3 have the MCBSP2 connected to the TDM
interface. The kernel should configure the pinmux for these pins in order
to get TWL4030 codec working. Without this, for example, playing a wav file
doesn't work.
Signed-off-by: Enric Balletbo i Serra eballe...@gmail.com
32 matches
Mail list logo
