On Fri, 25 Jan 2013, Aaro Koskinen wrote:
There is a long-standing bug that OHCI USB host controller does
not respond on 1710, because of wrong clock definitions. See e.g.
http://marc.info/?l=linux-omapm=119634441229321w=2. All register reads
return just zeroes:
Thanks, queued for v3.8-rc
On Fri, 25 Jan 2013, Rajendra Nayak wrote:
dpll_usb needs the clkdm association so the clkdm can be
turned on before a relock. All other dplls for omap4 belong
to the ALWON (always on) domain.
The association was present as part of the older data file
(clock44xx_data.c) but looks like was
Hi Paul,
Any comments on this?
-Original Message-
From: J, KEERTHY
Sent: Friday, January 18, 2013 3:52 PM
To: linux-omap@vger.kernel.org; p...@pwsan.com
Cc: J, KEERTHY; Valentin, Eduardo
Subject: [PATCH] ARM: OMAP2+: OMAP44XX: Clock: Correct the clock identifiers
for OMAP4460 and
Hi
On Wed, 23 Jan 2013, Afzal Mohammed wrote:
Currently round rate function would return proper rate iff requested
rate exactly matches the PLL lockable rate. This causes set_rate to
fail if exact rate could not be set. Instead round rate may return
closest rate possible (less than the
Hello Jan,
On Tue, 22 Jan 2013, Jan Lübbe wrote:
Just a guess, but there can be problems when the appended DTB crosses an
1MB boundary. See this mail for details and a patch:
http://www.spinics.net/lists/arm-kernel/msg216898.html
Thanks for the suggestion. That patch didn't fix it for me.
On 01/24/2013 10:14 PM, Florian Vaussard wrote:
You are right. But then the pwm core must provide a way to know if the pwm
access function are callable
from atomic context or not (the gpio framework provides gpio_cansleep()).
This implies a good amount of changes to the pwm framework, and
Hi,
On Thu, 24 Jan 2013, Bedia, Vaibhav wrote:
Can you update your AM335x-only config to disable CONFIG_EARLY_PRINTK or
just skip earlyprintk option in the bootargs for now?
I'll give this a try over the next few days.
If EARLY_PRINTK is known to be broken for DT boots, could you please put
On Friday 25 January 2013 01:18 PM, Felipe Balbi wrote:
On Thu, Jan 24, 2013 at 09:32:46PM -0800, Stephen Warren wrote:
On 01/24/2013 06:19 PM, Kishon Vijay Abraham I wrote:
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to
On Friday 25 January 2013 01:13 PM, Felipe Balbi wrote:
Hi,
On Fri, Jan 25, 2013 at 08:42:24AM +0530, Kishon Vijay Abraham I wrote:
palmas-usb is made as a comparator driver to omap usb2 phy, so that
omap usb can make use of palmas for srp and also to set vbus.
Signed-off-by: Kishon Vijay
On Tue, 22 Jan 2013, Afzal Mohammed wrote:
am335x does not have freqsel, avoid it.
Signed-off-by: Afzal Mohammed af...@ti.com
Thanks, queued for 3.9.
- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More
hi,
On Fri, Jan 25, 2013 at 02:12:41PM +0530, kishon wrote:
On Friday 25 January 2013 01:18 PM, Felipe Balbi wrote:
On Thu, Jan 24, 2013 at 09:32:46PM -0800, Stephen Warren wrote:
On 01/24/2013 06:19 PM, Kishon Vijay Abraham I wrote:
Added a new driver for the usb part of control module. This
On Friday 25 January 2013 02:15 PM, Felipe Balbi wrote:
hi,
On Fri, Jan 25, 2013 at 02:12:41PM +0530, kishon wrote:
On Friday 25 January 2013 01:18 PM, Felipe Balbi wrote:
On Thu, Jan 24, 2013 at 09:32:46PM -0800, Stephen Warren wrote:
On 01/24/2013 06:19 PM, Kishon Vijay Abraham I wrote:
Hi,
On Fri, 18 Jan 2013, J Keerthy wrote:
The previous logic to detect the clocks for OMAP4460
was to combine the clocks marked as CK_443X and CK_446X. This would be
fine as long as OMAP4460 was a super set of OMAP4430 clock set.
This is not the case as there are clocks which are specific to
On Fri, Jan 25, 2013 at 02:14:07PM +0530, kishon wrote:
On Friday 25 January 2013 01:13 PM, Felipe Balbi wrote:
Hi,
On Fri, Jan 25, 2013 at 08:42:24AM +0530, Kishon Vijay Abraham I wrote:
palmas-usb is made as a comparator driver to omap usb2 phy, so that
omap usb can make use of palmas for
Remove some clocks that don't appear to be used by anything
and which are not associated with any hardware registers.
Signed-off-by: Paul Walmsley p...@pwsan.com
Cc: Rajendra Nayak rna...@ti.com
---
arch/arm/mach-omap2/cclock2420_data.c | 16 +---
The platform data is used not only by wlcore-based drivers, but also
by wl1251. Move it up in the directory hierarchy to reflect this.
Additionally, make it truly optional. At the moment, disabling
platform data while wl1251_sdio or wlcore_sdio are enabled doesn't
work, but it will be necessary
A seperate driver has been added to handle the usb part of control
module. A device for the above driver is created here, using the register
address information to be used by the driver for powering on the PHY and
for writing to the mailbox.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Writing to control module registers for doing the above task which was
previously done in omap
Added has_mailbox to the musb platform data to specify that omap uses
an external mailbox (in control module) to communicate with the musb
core during device connect and disconnect.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/mach-omap2/usb-musb.c |3 +++
Start using the control module driver for powering on the PHY and for
writing to the mailbox instead of writing to the control module
registers on their own.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/usb/omap-usb.txt |4 ++
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Also added an API to power on usb3 phy (omap5).
Writing to control module registers for doing the
Add usb otg data node in omap4/omap3 device tree file. Also update
the node with board specific setting in omapx-board.dts file.
The dt data specifies among others the interface type (ULPI or UTMI), mode
which is mostly OTG, power that specifies the amount of power this can supply
when in host
Add omap control usb data in omap4 device tree file. This will have the
register address of registers to power on the PHY and to write to
mailbox. The information about this data node is available @
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I
Add omap-usb2 data node in omap4 device tree file. Since omap-usb2 is
connected to ocp2scp, omap-usb2 dt data is added as a child node
of ocp2scp. The information about this data node is availabe @
Documentation/devicetree/bindings/usb/usb-phy.txt
Acked-by: Felipe Balbi ba...@ti.com
Hi,
On Fri, Jan 25, 2013 at 03:54:00PM +0530, Kishon Vijay Abraham I wrote:
Start using the control module driver for powering on the PHY and for
writing to the mailbox instead of writing to the control module
registers on their own.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
This patch series adds dt data to get MUSB working in omap4 and omap3.
Long time back a patch series with the same title was sent but only
a part of it got merged. The rest of it wasn't merged because of
adding omap control usb data to glue and usb phy.
Now there exists a separate driver for
The OMAP glue has been modified to get PHY by phandle for dt boot.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
There were some comments w.r.t this patch for returning EPROBE_DEFER if
not able to get the phy, in my previous version.
Currently we can't have that because the gadget
usb_otg_ss_refclk960m is needed for usb2 phy present in omap5. For
omap4, the clk_get of this clock will fail since it does not have this
clock.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/phy/omap-usb2.c | 28 +++-
1 file changed, 27
Apologies for the delay in sending this version.
Added a driver for usb3 phy that handles the interaction between usb phy
device and dwc3 controller.
Changes from v3:
* Changed the property name from ctrl_module to ctrl-module
Changes from v2:
* used control module driver APIs to write to
Added a driver for usb3 phy that handles the interaction between usb phy
device and dwc3 controller.
This also includes device tree support for usb3 phy driver and
the documentation with device tree binding information is updated.
Currently writing to control module register is taken care in
On Fri, Jan 25, 2013 at 10:23:57AM +, Kishon Vijay Abraham I wrote:
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Writing to control
Added dt support for dwc3 core and update the documentation with
device tree binding information. Getting a PHY is now done using
devm_usb_get_phy_by_phandle() for dt boot.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/usb/dwc3.txt | 22
On Fri, Jan 25, 2013 at 11:01:41AM +, Mark Rutland wrote:
On Fri, Jan 25, 2013 at 10:23:57AM +, Kishon Vijay Abraham I wrote:
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB
Add omap control usb data in omap5 device tree file. This will have the
register address of registers to power on the USB2 PHY and USB3 PHY. The
information for the node added here is available in
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I
Add ocp2scp data node in omap5 device tree file. The information for
the node added here can be found @
Documentation/devicetree/bindings/bus/omap-ocp2scp.txt
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap5.dtsi |8
1 file changed, 8 insertions(+)
Add dwc3 omap glue data to the omap5 dt data file. The information about
the dt node added here is available @
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 11 +++
1 file changed, 11
Add dwc3 core dt data as a subnode to dwc3 omap glue data in omap5 dt
data file. The information for the entered data node is available @
Documentation/devicetree/bindings/usb/dwc3.txt
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap5.dtsi |7 +++
1 file
Update palmas-usb data node in palmas device tree file
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/palmas.dtsi |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/palmas.dtsi b/arch/arm/boot/dts/palmas.dtsi
index
This patch series adds dt data to get dwc3 working in omap5.
Changes from v1:
* rename ctrl_module to ctrl-module and usb_phy to usb-phy
This patch series is developed on
git://github.com/rrnayak/linux.git omap5-3.8-rc4-base-palmas
This is the last series of the series of patches.
I've kept
Add omap-usb3 and omap-usb2 data node in omap5 device tree file.
The information for the node added here is available @
Documentation/devicetree/bindings/usb/usb-phy.txt
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 14 ++
1 file changed, 14
Multiple dwc3 controllers will try to allocate multiple platform
devices for no_op_xceive (for usb2_phy and usb3_phy) as well as
xhci-hcd.
This patchset updates the platform devices IDs for allocated
devices to AUTO in order to support multiple dwc3 controllers.
This is based on 'dwc3' branch of
Multiple dwc3 probe calls try to allocate no_op_xceive platform
device. Having static IDs for these will throw sysfs error -EEXIST.
Changing these static platform device IDs to AUTO to enable
multiple dwc3 controller support on a SoC.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
Multiple dwc3 controllers will try to allocate multiple xhci-hcd
interfaces.
Changing platform device IDs from NONE to AUTO to support
such cases.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
drivers/usb/dwc3/host.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff
On Friday 25 January 2013 03:57 PM, Felipe Balbi wrote:
Hi,
On Fri, Jan 25, 2013 at 03:54:00PM +0530, Kishon Vijay Abraham I wrote:
Start using the control module driver for powering on the PHY and for
writing to the mailbox instead of writing to the control module
registers on their own.
Hi Mike,
On Thu, Jan 24, 2013 at 22:30:44, Mike Turquette wrote:
Quoting Mohammed, Afzal (2013-01-24 03:36:02)
So there are 3 - LIDD is actually not for present use case, CORE could
be clubbed with the divider to have a composite clock. And CORE is
in functional clock path and logically
Hi Mike,
On Thu, Jan 24, 2013 at 22:36:30, Mike Turquette wrote:
Quoting Mohammed, Afzal (2013-01-24 03:29:15)
It is a functional constraint: divider has 8 bits and it can have
all possible values (0 to 255) and divider value corresponds to
value set in the 8 bits. But depending on the
On 01/25/2013 09:29 AM, Peter Ujfalusi wrote:
On 01/24/2013 10:14 PM, Florian Vaussard wrote:
You are right. But then the pwm core must provide a way to know if the pwm
access function are callable
from atomic context or not (the gpio framework provides gpio_cansleep()).
This implies a good
Hi Paul,
On Fri, Jan 25, 2013 at 13:48:11, Paul Walmsley wrote:
On Wed, 23 Jan 2013, Afzal Mohammed wrote:
Currently round rate function would return proper rate iff requested
rate exactly matches the PLL lockable rate. This causes set_rate to
fail if exact rate could not be set. Instead
Hi,
On Fri, Jan 25, 2013 at 04:41:46PM +0530, Kishon Vijay Abraham I wrote:
This patch series adds dt data to get dwc3 working in omap5.
Changes from v1:
* rename ctrl_module to ctrl-module and usb_phy to usb-phy
This patch series is developed on
git://github.com/rrnayak/linux.git
for_each_node_by_name() automatically calls of_node_put() on each
node passed; so don't do it explicitly unless there's an error.
Reported-by: Mark Rutland mark.rutl...@arm.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/mach-omap2/gpmc.c |5 +++--
1 files
We have two drivers at the moment: pwm-twl and pwm-twl-led. However new out of
SoC PWM drivers might come (for example for palmas). So it worth take a look
at some generic implementation.
OK. So I have the series. I need to add few more things but pwm-leds on
BeagleBoard works fine when I put
Pass an optional device_node pointer in the platform data,
which in turn will be put into a mtd_part_parser_data.
This way, code that sets up the platform devices can pass
along the node from DT so that the partitions can be parsed.
For non-DT boards, this change has no effect.
Acked-by: Artem
Hello.
On 25-01-2013 7:00, Kishon Vijay Abraham I wrote:
No functional change. Stray statements where removed from dwc3 core.
s/where/are/
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/dwc3/core.c |3 ---
1 file changed, 3 deletions(-)
WBR, Sergei
--
To
gpmc_onenand_init() will be called from another driver's probe() function,
so drop the __init annotation, in order to prevent section mismatches.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/mach-omap2/gpmc-onenand.c |2 +-
1 files changed, 1 insertions(+),
This patch adds device tree bindings for OMAP OneNAND devices.
Tested on an OMAP3 3430 IGEPv2 board.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
Changes from v2:
* Remove unneeded of_node_put() as reported by Mark Rutland
Changes from v1:
* Fix typo in
[...]
+OMAP CONTROL USB
+
+Required properties:
+ - compatible: Should be ti,omap-control-usb
+ - reg : Address and length of the register set for the device. It
contains
+ the address of control_dev_conf and otghs_control or
phy_power_usb
Could you not use '-'
On 01/25/2013 01:21 PM, Florian Vaussard wrote:
We have two drivers at the moment: pwm-twl and pwm-twl-led. However new out
of
SoC PWM drivers might come (for example for palmas). So it worth take a look
at some generic implementation.
OK. So I have the series. I need to add few more
Hi Rob,
On Wed, Jan 23, 2013 at 04:06:22, Rob Clark wrote:
A simple DRM/KMS driver for the TI LCD Controller found in various
smaller TI parts (AM33xx, OMAPL138, etc). This driver uses the
+void tilcdc_crtc_update_clk(struct drm_crtc *crtc)
+ /* in raster mode, minimum divisor is 2:
On 01/25/2013 04:33 AM, Kishon Vijay Abraham I wrote:
In order to support platforms which has multiple PHY's (of same type) and
which has multiple USB controllers, a new design is adopted wherin the binding
information (between the PHY and the USB controller) should be passed to the
PHY
On 01/25/2013 04:33 AM, Kishon Vijay Abraham I wrote:
In order to add support for multipe PHY's of the same type, new API's
for adding PHY and getting PHY has been added. Now the binding
information for the PHY and controller should be done in platform file
using usb_bind_phy API. And for
On Fri, Jan 25, 2013 at 7:19 AM, Mohammed, Afzal af...@ti.com wrote:
Hi Rob,
On Wed, Jan 23, 2013 at 04:06:22, Rob Clark wrote:
A simple DRM/KMS driver for the TI LCD Controller found in various
smaller TI parts (AM33xx, OMAPL138, etc). This driver uses the
+void
Hi Rob,
On Fri, Jan 25, 2013 at 19:29:40, Rob Clark wrote:
On Fri, Jan 25, 2013 at 7:19 AM, Mohammed, Afzal af...@ti.com wrote:
On Wed, Jan 23, 2013 at 04:06:22, Rob Clark wrote:
A simple DRM/KMS driver for the TI LCD Controller found in various
smaller TI parts (AM33xx, OMAPL138, etc).
On 01/25/2013 06:19 AM, Ezequiel Garcia wrote:
for_each_node_by_name() automatically calls of_node_put() on each
node passed; so don't do it explicitly unless there's an error.
Reported-by: Mark Rutland mark.rutl...@arm.com
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
Hi Ricardo,
You need to rebase this patch as the code has been moved to dss-common.c
file now. So it would not apply.
Sebastien
On 01/05/2013 12:26 AM, Ricardo Neri wrote:
While Pandaboard and SDP4430 have only one HDMI output connector, it may be
possible that future boards and SoCs
Hi Kishon,
On Thu, Jan 24, 2013 at 17:21:45, Mohammed, Afzal wrote:
On Wed, Jan 23, 2013 at 19:56:37, ABRAHAM, KISHON VIJAY wrote:
On Wednesday 23 January 2013 07:28 PM, Mohammed, Afzal wrote:
USB first instance of am335x works in mainline as of now.
Can you check if this series indeed
On Fri, Jan 25, 2013 at 8:15 AM, Mohammed, Afzal af...@ti.com wrote:
Hi Rob,
On Fri, Jan 25, 2013 at 19:29:40, Rob Clark wrote:
On Fri, Jan 25, 2013 at 7:19 AM, Mohammed, Afzal af...@ti.com wrote:
On Wed, Jan 23, 2013 at 04:06:22, Rob Clark wrote:
A simple DRM/KMS driver for the TI LCD
Hi,
On Fri, Jan 25, 2013 at 12:29:43PM +, Mark Rutland wrote:
+ depending upon omap4 or omap5.
+ - reg-names: The names of the register addresses corresponding to the
registers
+ filled in reg.
+ - ti,type: This is used to differentiate whether the control module
Hi,
I have a couple more comments after looking though this a bit more thoroughly.
On Fri, Jan 25, 2013 at 12:23:11PM +, Ezequiel Garcia wrote:
This patch adds device tree bindings for OMAP OneNAND devices.
Tested on an OMAP3 3430 IGEPv2 board.
Signed-off-by: Ezequiel Garcia
On Fri, Jan 25, 2013 at 02:59:28PM +, Felipe Balbi wrote:
Hi,
On Fri, Jan 25, 2013 at 12:29:43PM +, Mark Rutland wrote:
+ depending upon omap4 or omap5.
+ - reg-names: The names of the register addresses corresponding to
the registers
+ filled in reg.
+ -
Hi Sebastien,
On 01/25/2013 08:44 AM, Sebastien Guiriec wrote:
Hi Ricardo,
You need to rebase this patch as the code has been moved to dss-common.c
file now. So it would not apply.
Thanks! I will send a new rebased version.
Ricardo
Sebastien
On 01/05/2013 12:26 AM, Ricardo Neri wrote:
Hi,
On Fri, Jan 25, 2013 at 04:14:02PM +, Mark Rutland wrote:
On Fri, Jan 25, 2013 at 02:59:28PM +, Felipe Balbi wrote:
Hi,
On Fri, Jan 25, 2013 at 12:29:43PM +, Mark Rutland wrote:
+ depending upon omap4 or omap5.
+ - reg-names: The names of the register
* Rajendra Nayak rna...@ti.com [130124 01:54]:
On Wednesday 23 January 2013 12:09 AM, Tony Lindgren wrote:
It seems that we should have the iospace available in the driver
at that point. And it should be also available to the runtime PM
code in hwmod in the device somewhere?
I couldn't find
* Bedia, Vaibhav vaibhav.be...@ti.com [130123 06:35]:
Hi Tony,
On Tue, Jan 22, 2013 at 23:53:32, Tony Lindgren wrote:
[...]
But I should get *something* from the kernel before it starts trying to
access the rootfs ?
Here's something Kevin fixed but did not send it out before
On Fri, Jan 25, 2013 at 04:23:46PM +, Felipe Balbi wrote:
Hi,
On Fri, Jan 25, 2013 at 04:14:02PM +, Mark Rutland wrote:
On Fri, Jan 25, 2013 at 02:59:28PM +, Felipe Balbi wrote:
Hi,
On Fri, Jan 25, 2013 at 12:29:43PM +, Mark Rutland wrote:
+ depending upon
* Luciano Coelho coe...@ti.com [130125 02:09]:
The platform data is used not only by wlcore-based drivers, but also
by wl1251. Move it up in the directory hierarchy to reflect this.
Additionally, make it truly optional. At the moment, disabling
platform data while wl1251_sdio or
Hi Mark,
First of all: thanks for reviewing.
On Fri, Jan 25, 2013 at 12:56 PM, Mark Rutland mark.rutl...@arm.com wrote:
Hi,
I have a couple more comments after looking though this a bit more thoroughly.
On Fri, Jan 25, 2013 at 12:23:11PM +, Ezequiel Garcia wrote:
This patch adds device
Quoting Mohammed, Afzal (2013-01-25 04:18:22)
Hi Paul,
On Fri, Jan 25, 2013 at 13:48:11, Paul Walmsley wrote:
On Wed, 23 Jan 2013, Afzal Mohammed wrote:
Currently round rate function would return proper rate iff requested
rate exactly matches the PLL lockable rate. This causes
Quoting Mohammed, Afzal (2013-01-25 04:06:41)
Hi Mike,
On Thu, Jan 24, 2013 at 22:36:30, Mike Turquette wrote:
Quoting Mohammed, Afzal (2013-01-24 03:29:15)
It is a functional constraint: divider has 8 bits and it can have
all possible values (0 to 255) and divider value corresponds
Quoting Mohammed, Afzal (2013-01-25 04:05:44)
Hi Mike,
On Thu, Jan 24, 2013 at 22:30:44, Mike Turquette wrote:
Quoting Mohammed, Afzal (2013-01-24 03:36:02)
So there are 3 - LIDD is actually not for present use case, CORE could
be clubbed with the divider to have a composite clock.
When using LPAE the call to alloc_init_pte is passed then end address
for the entire 1st level page table region, and the code unluckily ends
up going over the bounds of the single allocated PTE, which is sad.
This caused LPAE boot on omap5 to crash.
There may be some hidden mystery in the boot
Hi Christoffer,
On Saturday 26 January 2013 06:01 AM, Christoffer Dall wrote:
When using LPAE the call to alloc_init_pte is passed then end address
for the entire 1st level page table region, and the code unluckily ends
up going over the bounds of the single allocated PTE, which is sad.
This
On Fri, Jan 25, 2013 at 11:50 PM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Hi Christoffer,
On Saturday 26 January 2013 06:01 AM, Christoffer Dall wrote:
When using LPAE the call to alloc_init_pte is passed then end address
for the entire 1st level page table region, and the code
82 matches
Mail list logo
