On 22 May 2014 17:18, Peter Griffin wrote:
> This patch adds the device tree binding documentation for ST
> SDHCI driver. It contains the differences between the core properties
> in mmc.txt and the properties used by the sdhci-st driver.
>
> Signed-off-by: Peter Griffin
> Signed-off-by: Giuseppe
On 23 May 2014 00:16, Sebastian Hesselbarth
wrote:
> Commit f8ec589b86f6
> "mmc: sdhci-dove: allow GPIOs to be used for card detection on Dove"
> added a gpio based card detect interrupt handler that was hooked up
> into card_tasket.
>
> Commit 3560db8e247a
> "mmc: sdhci: push card_tasklet int
Hi Pete,
On 22/05/14 16:18, Peter Griffin wrote:
ifeq ($(CONFIG_CB710_DEBUG),y)
CFLAGS-cb710-mmc+= -DDEBUG
diff --git a/drivers/mmc/host/sdhci-st.c b/drivers/mmc/host/sdhci-st.c
new file mode 100644
index 000..1790fa7
--- /dev/null
+++ b/drivers/mmc/host/sdhci-st.c
@@ -0,
Hi, All.
This patch is working on progress?
I want to merge this patch for fixing dw-mmc controller problem.
If this patch didn't work on progress, i will send the patch based-on this
patch.
Best Regards,
Jaehoon Chung
On 05/14/2014 06:53 PM, Ulf Hansson wrote:
> On 7 May 2014 12:06, Ludovic D
Sorry, add a title .
Hi
I have a problems that I want create a watchpoint to monitor a data for Debug
in kernel , but I don't know how to do it , I try the kprobes , but seems it
only support create .text section probe , Can't monitor data access , then I
try perf_event_create to create a h
Hi
I have a problems that I want create a watchpoint to monitor a data for
Debug in kernel , but I don't know how to do it ,
I try the kprobes , but seems it only support create .text section probe ,
Can't monitor data access , then I try perf_event_create to create a
hardware
Data watchpoin
On Fri, May 16, 2014 at 6:43 PM, Stephen Boyd wrote:
> On 05/16/14 09:24, Linus Walleij wrote:
>> On Wed, May 14, 2014 at 12:13 AM, Stephen Boyd wrote:
>>
>>> Please add a note that this id is fake in the commit text or in
>>> the code as well.
>> You just need one of your hardware engineers to a
Commit f8ec589b86f6
"mmc: sdhci-dove: allow GPIOs to be used for card detection on Dove"
added a gpio based card detect interrupt handler that was hooked up
into card_tasket.
Commit 3560db8e247a
"mmc: sdhci: push card_tasklet into threaded irq handler"
now removed that very card_tasklet causin
On 05/22/2014 12:21 PM, Sascha Hauer wrote:
> On Thu, May 22, 2014 at 10:16:35AM -0600, Stephen Warren wrote:
>> On 05/22/2014 09:30 AM, Sascha Hauer wrote:
>>> Hi all,
>>>
>>> The wish to have persistent MMC block device names for passing a suitable
>>> root=/dev/mmcblkX option came up several tim
On Mon, May 19, 2014 at 6:49 PM, Seungwon Jeon wrote:
> On Sat, May 17, 2014, Sonny Rao wrote:
>> On Tue, May 13, 2014 at 4:09 AM, Seungwon Jeon wrote:
>> > On Tuesday, May 13, Sonny Rao wrote:
>> >> On Mon, May 12, 2014 at 10:02 PM, Seungwon Jeon
>> >> wrote:
>> >> > As I mentioned in previous
On Thu, May 22, 2014 at 10:16:35AM -0600, Stephen Warren wrote:
> On 05/22/2014 09:30 AM, Sascha Hauer wrote:
> > Hi all,
> >
> > The wish to have persistent MMC block device names for passing a suitable
> > root=/dev/mmcblkX option came up several times already and has been
> > discussed
> > at
Hi,
On 22.05.2014 13:38, Hans de Goede wrote:
> On 05/22/2014 12:23 PM, Chen-Yu Tsai wrote:
>> On Thu, May 22, 2014 at 5:49 PM, Hans de Goede wrote:
snip
>>> I've been thinking a bit about this, and it is a non trivial problem since
>>> sdio devices are normally instantiated when probed, unlik
> This platform driver adds initial support for the SDHCI host controller
> found on STMicroelectronics SoCs.
>
> It has been tested on STiH41x b2020 platforms currently.
>
> Signed-off-by: Peter Griffin
> Signed-off-by: Giuseppe Cavallaro
> ---
> drivers/mmc/host/Kconfig| 12 +++
> driv
On 05/22/2014 09:30 AM, Sascha Hauer wrote:
> Hi all,
>
> The wish to have persistent MMC block device names for passing a suitable
> root=/dev/mmcblkX option came up several times already and has been discussed
> at least in these threads:
>
> http://lists.infradead.org/pipermail/linux-arm-kerne
> This patch adds the device tree binding documentation for ST
> SDHCI driver. It contains the differences between the core properties
> in mmc.txt and the properties used by the sdhci-st driver.
>
> Signed-off-by: Peter Griffin
> Signed-off-by: Giuseppe Cavallaro
> ---
> Documentation/devicetr
On Thu, 22 May 2014, Peter Griffin wrote:
> This adds the required pin config for both SDHCI controllers on
> the stih416 SoC.
>
> Signed-off-by: Peter Griffin
> Signed-off-by: Giuseppe Cavallaro
> ---
> arch/arm/boot/dts/stih416-pinctrl.dtsi | 39
> ++
> 1 fil
On Thu, 22 May 2014, Peter Griffin wrote:
> This patch adds device tree config for both sdhci controllers
> on the stih416 SoC.
>
> Signed-off-by: Peter Griffin
> Signed-off-by: Giuseppe Cavallaro
> ---
> arch/arm/boot/dts/stih416.dtsi | 24
> 1 file changed, 24 insert
> This patch adds the required pin config for the sdhci controller
> present in the stih415 SoC.
>
> Signed-off-by: Peter Griffin
> Signed-off-by: Giuseppe Cavallaro
Switch these round - same with all the other patches.
> ---
> arch/arm/boot/dts/stih415-pinctrl.dtsi | 21 +
Program TEGRA_SDHCI_VENDOR_MISC_CTRL so that UHS modes aren't advertised
in SDHCI_CAPABILITIES_1. While the Tegra SDHCI controller does support
these modes, they require Tegra-specific tuning and calibration routines
which the driver does not support yet.
Signed-off-by: Andrew Bresticker
Tested-
Tegra SDHCI controllers, by default, report a base clock frequency
of 208Mhz in SDHCI_CAPABILTIES which may or may not be equal to the
actual base clock frequency. This is because the clock rate is
configured by the clock controller, which is external to the SD/MMC
controller. Since the SD/MMC co
On 05/22/2014 05:18 PM, Peter Griffin wrote:
This adds the required pin config for both SDHCI controllers on
the stih416 SoC.
Signed-off-by: Peter Griffin
Signed-off-by: Giuseppe Cavallaro
---
arch/arm/boot/dts/stih416-pinctrl.dtsi | 39 ++
1 file changed,
On 05/22/2014 05:18 PM, Peter Griffin wrote:
This patch adds the device tree binding documentation for ST
SDHCI driver. It contains the differences between the core properties
in mmc.txt and the properties used by the sdhci-st driver.
Signed-off-by: Peter Griffin
Signed-off-by: Giuseppe Caval
Hi Peter,
On 05/22/2014 05:18 PM, Peter Griffin wrote:
This series adds a SDHCI platform driver for ST SoCs, along with
the additional device tree bindings and configuration to enable
the controller to work properly.
Initially it supports the stih416 and stih415 SoCs, and has
been tested on a s
Hi Peter
On 05/22/2014 05:18 PM, Peter Griffin wrote:
This platform driver adds initial support for the SDHCI host controller
found on STMicroelectronics SoCs.
It has been tested on STiH41x b2020 platforms currently.
Signed-off-by: Peter Griffin
Signed-off-by: Giuseppe Cavallaro
---
driver
On Thu, 22 May 2014, Peter Griffin wrote:
> Because the first sdhci controller is present on both stih415 and
> stih416 SoC which can both populate the b2020 board, it can be
> enabled in the generic DT file.
>
> Signed-off-by: Peter Griffin
> Signed-off-by: Giuseppe Cavallaro
These are the wr
On Thu, 22 May 2014, Peter Griffin wrote:
> The second controller is only present on the stih416 SoC. Also
> mark this as non-removeable as its eMMC.
>
> Signed-off-by: Peter Griffin
> Signed-off-by: Giuseppe Cavallaro
> ---
> arch/arm/boot/dts/stih416-b2020.dts | 8
> 1 file changed,
> This patch enables SDHCI STI platform driver.
>
> Signed-off-by: Peter Griffin
> ---
> arch/arm/configs/multi_v7_defconfig | 1 +
> 1 file changed, 1 insertion(+)
Acked-by: Lee Jones
> diff --git a/arch/arm/configs/multi_v7_defconfig
> b/arch/arm/configs/multi_v7_defconfig
> index d4e8a47.
As with gpio, uart and others, allow specifying the name_idx via the
aliases-node in the devicetree.
On embedded devices, there is often a combination of removable (e.g.
SD card) and non-removable mmc devices (e.g. eMMC).
Therefore the name_idx might change depending on
- host of removable
of_alias_max_index will return the maximum number for which an
alias of a given stem exists. This is useful for frameworks
whishing to reserve a number of device slots from dynamic
allocation.
Signed-off-by: Sascha Hauer
---
drivers/of/base.c | 29 +
include/linux/of
Hi all,
The wish to have persistent MMC block device names for passing a suitable
root=/dev/mmcblkX option came up several times already and has been discussed
at least in these threads:
http://lists.infradead.org/pipermail/linux-arm-kernel/2012-July/109984.html
https://www.mail-archive.com/linux
> Hi Stephen/Andrew,
>
> I tried to include the v2 of patch1 and patch2 in PR I just sent to
> Chris - but needed to omit them due to conflicts.
>
> Could you please re-base them on top of my PR and resend them? I
> suppose Chris can take them separately once he pulled my PR.
Will do.
Thanks,
And
This platform driver adds initial support for the SDHCI host controller
found on STMicroelectronics SoCs.
It has been tested on STiH41x b2020 platforms currently.
Signed-off-by: Peter Griffin
Signed-off-by: Giuseppe Cavallaro
---
drivers/mmc/host/Kconfig| 12 +++
drivers/mmc/host/Makefile
This adds the required pin config for both SDHCI controllers on
the stih416 SoC.
Signed-off-by: Peter Griffin
Signed-off-by: Giuseppe Cavallaro
---
arch/arm/boot/dts/stih416-pinctrl.dtsi | 39 ++
1 file changed, 39 insertions(+)
diff --git a/arch/arm/boot/dts/st
This patch enables SDHCI STI platform driver.
Signed-off-by: Peter Griffin
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
index d4e8a47..48951fc 100644
--- a/arch/arm/configs/m
Because the first sdhci controller is present on both stih415 and
stih416 SoC which can both populate the b2020 board, it can be
enabled in the generic DT file.
Signed-off-by: Peter Griffin
Signed-off-by: Giuseppe Cavallaro
---
arch/arm/boot/dts/stih41x-b2020x.dtsi | 4
1 file changed, 4 i
The second controller is only present on the stih416 SoC. Also
mark this as non-removeable as its eMMC.
Signed-off-by: Peter Griffin
Signed-off-by: Giuseppe Cavallaro
---
arch/arm/boot/dts/stih416-b2020.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/stih416-b2
This patch adds the required pin config for the sdhci controller
present in the stih415 SoC.
Signed-off-by: Peter Griffin
Signed-off-by: Giuseppe Cavallaro
---
arch/arm/boot/dts/stih415-pinctrl.dtsi | 21 +
arch/arm/boot/dts/stih415.dtsi | 12
2 files ch
This patch adds the device tree binding documentation for ST
SDHCI driver. It contains the differences between the core properties
in mmc.txt and the properties used by the sdhci-st driver.
Signed-off-by: Peter Griffin
Signed-off-by: Giuseppe Cavallaro
---
Documentation/devicetree/bindings/mmc/
This patch adds device tree config for both sdhci controllers
on the stih416 SoC.
Signed-off-by: Peter Griffin
Signed-off-by: Giuseppe Cavallaro
---
arch/arm/boot/dts/stih416.dtsi | 24
1 file changed, 24 insertions(+)
diff --git a/arch/arm/boot/dts/stih416.dtsi b/arch
This series adds a SDHCI platform driver for ST SoCs, along with
the additional device tree bindings and configuration to enable
the controller to work properly.
Initially it supports the stih416 and stih415 SoCs, and has
been tested on a stih416-b2020 board.
regards,
Peter.
--
To unsubscribe f
* Chris Ball [140522 05:42]:
> Hi,
>
> On Thu, May 22 2014, Ulf Hansson wrote:
> > I had a second look at Andreas Fenkart's patchset to enable SDIO irq
> > for omap. Those needs an additional iteration, since there are
> > unresolved dependencies to CONFIG_PM_RUNTIME (and possibly to other
> > Kc
On 05/22/2014 11:09 AM, Ulf Hansson wrote:
On 19 May 2014 20:02, Sebastian Hesselbarth
wrote:
DT-enabled Dove moved over from ARCH_DOVE in mach-dove to MACH_DOVE in
mach-mvebu. As non-DT ARCH_DOVE will stay to rot for a while, add a new
DT-only MACH_DOVE Kconfig. This slipped through the cracks
Hi,
On Thu, May 22 2014, Ulf Hansson wrote:
> I had a second look at Andreas Fenkart's patchset to enable SDIO irq
> for omap. Those needs an additional iteration, since there are
> unresolved dependencies to CONFIG_PM_RUNTIME (and possibly to other
> Kconfigs as well). Apparently I had all the ne
On 22 May 2014 14:02, kbuild test robot wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc.git mmc-next
> head: 830bb78ad0985cc44246fcd6f6c1f04c5abb
> commit: f6a903a75eff1eb6d53703543b1674da211b0b28 [79/96] mmc: omap_hsmmc:
> Extend debugfs by SDIO IRQ handling, runtime
Hi,
On Thu, May 22 2014, Ulf Hansson wrote:
> "mmc: sdhci: convert sdhci_set_uhs_signaling() into a library function"
>
> The following lines...
> + else if ((ios->timing == MMC_TIMING_UHS_DDR50) ||
> +(ios->timing == MMC_TIMING_MMC_DDR52))
> + ctrl_2 |= SDHCI_C
On 22 May 2014 14:05, Chris Ball wrote:
> Hi Ulf,
>
> On Thu, May 22 2014, Ulf Hansson wrote:
>> Here are a third and final collection of patches for 3.16.
>>
>> I have as you and I discussed (off list), collected the patches from
>> Russell's sdhci patchset. I needed to resolve some conflicts whi
Hi Ulf,
On Thu, May 22 2014, Ulf Hansson wrote:
> Here are a third and final collection of patches for 3.16.
>
> I have as you and I discussed (off list), collected the patches from
> Russell's sdhci patchset. I needed to resolve some conflicts while
> applying them, but it was manageable. I also
Hi,
On 05/22/2014 12:23 PM, Chen-Yu Tsai wrote:
> Hi,
>
> On Thu, May 22, 2014 at 5:49 PM, Hans de Goede wrote:
>> Hi All,
>>
>> Arend asked me to test these 2 patches for adding devicetree support to
>> brcmfmac sdio devices:
>> "dt: bindings: add bindings for Broadcom bcm43xx sdio devices"
>>
On 21 May 2014 02:43, Chris Ball wrote:
> Hi Stephen,
>
> On Tue, May 20 2014, Stephen Warren wrote:
>> On 04/16/2014 05:08 PM, Andrew Bresticker wrote:
>>> Program TEGRA_SDHCI_VENDOR_MISC_CTRL so that UHS modes aren't advertised
>>> in SDHCI_CAPABILITIES_1. While the Tegra SDHCI controller does
Hi Chris,
Here are a third and final collection of patches for 3.16.
I have as you and I discussed (off list), collected the patches from
Russell's sdhci patchset. I needed to resolve some conflicts while
applying them, but it was manageable. I also omitted the patch which
was reported to caused
Hi,
On Thu, May 22, 2014 at 5:49 PM, Hans de Goede wrote:
> Hi All,
>
> Arend asked me to test these 2 patches for adding devicetree support to
> brcmfmac sdio devices:
> "dt: bindings: add bindings for Broadcom bcm43xx sdio devices"
> "brcmfmac: add device tree support for SDIO devices"
> https
Hi All,
Arend asked me to test these 2 patches for adding devicetree support to
brcmfmac sdio devices:
"dt: bindings: add bindings for Broadcom bcm43xx sdio devices"
"brcmfmac: add device tree support for SDIO devices"
https://groups.google.com/forum/#!msg/linux-sunxi/Zph6zDTnAcw/_-wOO-gnIuQJ
Ge
On 19 May 2014 20:02, Sebastian Hesselbarth
wrote:
> DT-enabled Dove moved over from ARCH_DOVE in mach-dove to MACH_DOVE in
> mach-mvebu. As non-DT ARCH_DOVE will stay to rot for a while, add a new
> DT-only MACH_DOVE Kconfig. This slipped through the cracks and now is
> a fix to allow to build Do
On Mon, May 19, 2014@08:02:51PM +0200, Sebastian Hesselbarth wrote:
> DT-enabled Dove moved over from ARCH_DOVE in mach-dove to MACH_DOVE in
> mach-mvebu. As non-DT ARCH_DOVE will stay to rot for a while, add a new
> DT-only MACH_DOVE Kconfig. This slipped through the cracks and now is
> a fix to a
54 matches
Mail list logo
