On Tue, Aug 25, 2015 at 01:03:04PM +0300, Grygorii Strashko wrote:
On 08/19/2015 09:11 PM, Mark Brown wrote:
So substract this address from the start of the resource to get the
offset? Or provide a wrapper function in the resource code which does
that.
I'd be very appreciated if you
On 25 August 2015 at 11:05, Kishon Vijay Abraham I kis...@ti.com wrote:
From: Balaji T K balaj...@ti.com
MMC tuning procedure is required to support SD card
UHS1-SDR104 mode and EMMC HS200 mode.
The tuning function omap_execute_tuning() will only
be called by the MMC/SD core if the
On 3 August 2015 at 14:26, Kishon Vijay Abraham I kis...@ti.com wrote:
From: Roger Quadros rog...@ti.com
For platforms that doesn't have explicit regulator control in MMC,
populate voltage-ranges in MMC device tree node and use
mmc_of_parse_voltage to get ocr_avail
I don't like this.
If we
The question is two-folded, hence the crossposting.
I have a kernel that runs perfectly on my beaglebone black, except for one thing
- the kmod for the watchdog is not autoloaded upon boot albeit the device-tree
node is present:
ubuntu@beaglebone:~$ dmesg | grep wdt
ubuntu@beaglebone:~$ ll
On 23 August 2015 at 02:11, Julia Lawall julia.law...@lip6.fr wrote:
Return a negative error code on failure.
A simplified version of the semantic match that finds this problem is as
follows: (http://coccinelle.lip6.fr/)
// smpl
@@
identifier ret; expression e1,e2;
@@
(
if (\(ret
Currently apart from dra7, omap5 and amx3 all the other SoCs
are identified using cpu_is_* functions which is not right since
they are all SoCs(System on Chips). Hence changing the SoC
identification code to use soc_is instead of cpu_is and keeping
defines for cpu_is where needed. This allows us
On Monday 24 August 2015 03:34 PM, Sekhar Nori wrote:
Hi Mugunthan,
On Wednesday 12 August 2015 03:22 PM, Mugunthan V N wrote:
+static const struct of_device_id cpsw_of_mtable[] = {
+ { .compatible = ti,cpsw, .data = cpsw_devtype[CPSW], },
+ { .compatible = ti,am335x-cpsw, .data =
Hi Tony,
On Thursday 30 July 2015 01:07 AM, Nishanth Menon wrote:
On 07/29/2015 06:09 AM, Kishon Vijay Abraham I wrote:
For beagle x15, both the vdd and io lines are connected to the
same regulator (ldo1_reg). However vmmc_aux is populated to vdd_3v3.
Remove it.
Signed-off-by: Kishon Vijay
On 08/20/2015 11:25 PM, Mark Brown wrote:
On Thu, Aug 20, 2015 at 04:00:59PM +0530, Vignesh R wrote:
-writeb(*txbuf, qspi-base + QSPI_SPI_DATA_REG);
+if (count = QSPI_WLEN_MAX_BYTES) {
+u32 *txp = (u32 *)txbuf;
+
+
Hi Mark,
On 08/19/2015 09:11 PM, Mark Brown wrote:
On Tue, Aug 18, 2015 at 11:23:54AM +0530, Kishon Vijay Abraham I wrote:
On Friday 14 August 2015 11:30 PM, Mark Brown wrote:
On Mon, Jul 27, 2015 at 04:54:09PM +0530, Kishon Vijay Abraham I wrote:
is moved as a child node of syscon, vsel_reg
Added a separate function to set the voltage capabilities of the host
controller. Voltage capabilities should be set only once during
controller initialization but bus power can be changed every time there
is a voltage switch and whenever a different card is inserted.
This allows
Add support for vmmc_aux to switch to 1.8v. Also use iov instead of
vdd to indicate io voltage. This is in preparation for adding support
for io signal voltage switch.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/mmc/host/omap_hsmmc.c | 48
From: Balaji T K balaj...@ti.com
UHS sd card i/o data line can operate at 3V and 1.8V on UHS speed
modes. Add support for signal voltage switch and check for card_busy.
Signed-off-by: Balaji T K balaj...@ti.com
Signed-off-by: Sourav Poddar sourav.pod...@ti.com
[kis...@ti.com : cleanup the
HCTL is now set based on ios.signal_voltage set by mmc core and not
hardcoded to 3V0 if OMAP_HSMMC_SUPPORTS_DUAL_VOLT is set. If
OMAP_HSMMC_SUPPORTS_DUAL_VOLT is set, it means HCTL can be set to either
3V0 or 1V8. And it should be set to 3V0 or 1V8 depending on
ios.signal_voltage.
Also it is now
From: Balaji T K balaj...@ti.com
MMC tuning procedure is required to support SD card
UHS1-SDR104 mode and EMMC HS200 mode.
The tuning function omap_execute_tuning() will only
be called by the MMC/SD core if the corresponding
speed modes are supported by the OMAP silicon which
is set in the mmc
According to errata i802, DCRC error interrupts
(MMCHS_STAT[21] DCRC=0x1) can occur during the tuning procedure.
The DCRC interrupt, occurs when the last tuning block fails
(the last ratio tested). The delay from CRC check until the
interrupt is asserted is bigger than the delay until assertion
From: Mugunthan V N mugunthan...@ti.com
DRA7 Errata No i834: When using high speed HS200 and SDR104
cards, the functional clock for MMC module will be 192MHz.
At this frequency, the maximum obtainable timeout (DTO =0xE)
in hardware is (1/192MHz)*2^27 = 700ms. Commands taking longer
than 700ms
Now that vmmc regulator is made optional, do not bail out if vmmc
regulator is not found.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/mmc/host/omap_hsmmc.c |7 ---
1 file changed, 7 deletions(-)
diff --git a/drivers/mmc/host/omap_hsmmc.c
ios-vdd is set only in mmc_power_up and mmc_power_off and not in
mmc_select_voltage as mentioned in the code comment. This seems to be
legacy code that has been carried for a long time without being
tested.
This will be replaced with a proper voltage switch sequence and
populated in
Add a separate function to set the UHSMS field to one
of SDR104, SDR50, DDR50, SDR25 or SDR12 depending on the
inserted SD card. This is required for
tuning to succeed in the case of SDR104/HS200 or SDR50.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/mmc/host/omap_hsmmc.c |
Set the clock rate of the functional clock to the max frequency
that is passed to the driver either using pdata or dt.
Also remove unnecessary setting of host-fclk to NULL.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/mmc/host/omap_hsmmc.c | 13 -
1 file
Patch series implements voltage switching and tuning for omap_hsmmc
driver.
Changes from v1:
*) rebased on top of [1]
*) Patch breaking omap3 beagle xm is fixed. (set clk rate patch was
breaking beagle xm)
[1] - https://lkml.org/lkml/2015/8/21/125
Did basic read/write test in J6, J6 Eco,
Register address in name of the node is wrong
Signed-off-by: Vishal Mahaveer vish...@ti.com
Acked-by: Mugunthan V N mugunthan...@ti.com
---
arch/arm/boot/dts/dra7.dtsi |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/boot/dts/dra7.dtsi
If we don't insert resources into the resource tree,
calls to of_platform_depopulate() will end up in NULL
pointer dereferences because the resource parent will
be set to NULL even though we still have more resources
to go through.
Without this patch, the result is as follows:
[ 28.238158]
On 08/21/2015 11:13 AM, Tony Lindgren wrote:
* Tony Lindgren t...@atomide.com [150818 23:42]:
Hi,
* Grygorii Strashko grygorii.stras...@ti.com [150818 04:14]:
Hi,
This patch series contains set of trivial fixes and improvements, and also
patches which fixes wrong APIs usage in atomic
On 3 August 2015 at 14:26, Kishon Vijay Abraham I kis...@ti.com wrote:
Changes from v1:
*) return on -EPROBE_DEFER and other fatal errors. (Don't return only
if the return value is -ENODEV)
*) Remove the beagle x15 dts patch. It can be part of a different
series.
*) Avoid using
Hi Ingo,
I'm facing an issue with CONFIG_DEBUG_SHIRQ and pm_runtime when using
devm_request_*irq().
If we using devm_request_*irq(), that irq will be freed after device
drivers' -remove() gets called. If on -remove(), we're calling
pm_runtime_put_sync(); pm_runtime_disable(), device's clocks
27 matches
Mail list logo
