Hi,
On 21-01-16 06:26, Chen-Yu Tsai wrote:
According to Allwinner, only mmc3 supports 8 bit DDR transfers for eMMC.
Switch to mmc3 for the onboard eMMC, and also assign vqmmc for signal
voltage sensing/switching, and "cap-mmc-hw-reset" to denote this
instance can use eMMC hardware reset.
This
Hi,
On 21-01-16 13:28, Chen-Yu Tsai wrote:
On Thu, Jan 21, 2016 at 8:25 PM, Hans de Goede wrote:
Hi,
On 21-01-16 13:23, Chen-Yu Tsai wrote:
On Thu, Jan 21, 2016 at 7:16 PM, Hans de Goede
wrote:
Hi,
On 21-01-16 06:26, Chen-Yu Tsai wrote:
Hi,
On 21-01-16 06:26, Chen-Yu Tsai wrote:
DDR transfer modes include UHS-1 DDR50 and MMC HS-DDR (or MMC_DDR52).
Consider MMC_DDR52 when setting clock delays.
Signed-off-by: Chen-Yu Tsai
---
drivers/mmc/host/sunxi-mmc.c | 6 --
1 file changed, 4 insertions(+), 2
Hi,
On 21-01-16 12:55, Chen-Yu Tsai wrote:
On Thu, Jan 21, 2016 at 7:14 PM, Hans de Goede wrote:
Hi,
On 21-01-16 06:26, Chen-Yu Tsai wrote:
DDR transfer modes include UHS-1 DDR50 and MMC HS-DDR (or MMC_DDR52).
Consider MMC_DDR52 when setting clock delays.
Hi,
On 21-01-16 06:26, Chen-Yu Tsai wrote:
Hi everyone,
This series adds support for vqmmc regulator and eMMC DDR modes for
sunxi-mmc. Allwinner's MMC controller supports eMMC 4.41 on earlier
SoCs, and up to 5.0 on latest ones. UHS-1 modes are also supported
by the hardware, but these are not
Hi,
On 21-01-16 13:23, Chen-Yu Tsai wrote:
On Thu, Jan 21, 2016 at 7:16 PM, Hans de Goede wrote:
Hi,
On 21-01-16 06:26, Chen-Yu Tsai wrote:
According to Allwinner, only mmc3 supports 8 bit DDR transfers for eMMC.
Switch to mmc3 for the onboard eMMC, and also assign
On Thu, Jan 21, 2016 at 7:16 PM, Hans de Goede wrote:
> Hi,
>
> On 21-01-16 06:26, Chen-Yu Tsai wrote:
>>
>> According to Allwinner, only mmc3 supports 8 bit DDR transfers for eMMC.
>> Switch to mmc3 for the onboard eMMC, and also assign vqmmc for signal
>> voltage
On Thu, Jan 21, 2016 at 8:25 PM, Hans de Goede wrote:
> Hi,
>
> On 21-01-16 13:23, Chen-Yu Tsai wrote:
>>
>> On Thu, Jan 21, 2016 at 7:16 PM, Hans de Goede
>> wrote:
>>>
>>> Hi,
>>>
>>> On 21-01-16 06:26, Chen-Yu Tsai wrote:
According to
Hi,
On 21-01-16 00:43, Dan MacDonald wrote:
Hi Hans
Thanks for your reply but I've not got much further.
I don't have a /sys/class/ir but I do have /sys/class/lirc so maybe thats
it?
No I believe that that is wrong.
> However, nowhere within there can I find a file containing protocol
mmc2 has a special pin for eMMC hardware reset, which is controllable
from the controller. Add the "mmc-cap-hw-reset" property to denote that
this controller supports this function, and the pins are actually used.
Also increase the signal drive strength for mmc2 pins, for HS-DDR mode
support.
mmc2 has a special pin for eMMC hardware reset, which is controllable
from the controller. Add the "mmc-cap-hw-reset" property to denote that
this controller supports this function, and the pins are actually used.
Also increase the signal drive strength for mmc2 pins, for HS-DDR mode
support.
Hi,
I used the existing Android image for the Pine64 to hack the crippled U-Boot to
boot my own kernels (and DTs and rootfs').
Kindly find the first result here:
https://github.com/apritzel/pine64
It is still a giant hack, but a better start than the existing images for
people who want to
Let .set_ios() fail if mmc_regulator_set_ocr() fails to enable and set a
proper voltage for vmmc.
Signed-off-by: Chen-Yu Tsai
---
drivers/mmc/host/sunxi-mmc.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/mmc/host/sunxi-mmc.c
mmc2 has a special pin for eMMC hardware reset, which is controllable
from the controller. Add the "mmc-cap-hw-reset" property to denote that
this controller supports this function, and the pins are actually used.
Also increase the signal drive strength for mmc2 pins, for HS-DDR mode
support.
Hi everyone,
This series adds support for vqmmc regulator and eMMC DDR modes for
sunxi-mmc. Allwinner's MMC controller supports eMMC 4.41 on earlier
SoCs, and up to 5.0 on latest ones. UHS-1 modes are also supported
by the hardware, but these are not covered in this series, as no
boards have
Now that clock delay settings for 8 bit DDR are correct, and vqmmc
support is available, we can enable MMC_CAP_1_8V_DDR support. This
enables MMC HS-DDR at up to 52 MHz, even if signal voltage switching
is not available.
Signed-off-by: Chen-Yu Tsai
---
sun9i/A80 MMC controllers have a larger FIFO, and the FIFO DMA
trigger levels can be increased. Also, the mmc module clock parent
has a higher clock rate, and the sample and output delay phases
are different.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun9i-a80.dtsi | 8
Allwinner's mmc controller supports signal voltage switching. This is
supported in code in Allwinner's kernel. However, publicly available
boards all tie it to a fixed 3.0/3.3V regulator, with options to tie
it to 1.8V for eMMC on some.
Since Allwinner's kernel is an ancient 3.4, it is hard to
sunxi_mmc_init_host() originated from Allwinner kernel sources. The
magic numbers written to various registers was never documented.
Add comments for values found in Allwinner user manuals.
Signed-off-by: Chen-Yu Tsai
---
drivers/mmc/host/sunxi-mmc.c | 12
1 file
mmc2_8bit_pins is used with eMMC chips, which also have a reset pin.
The MMC controller also has a reset output that is supported.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun8i-a23-a33.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Allwinner's MMC controller needs to run at double the card clock rate
for 8 bit DDR transfer modes. Interestingly, this is not needed for
4 bit DDR transfers.
Different clock delays are needed for 8 bit eMMC DDR, due to the
increased module clock rate. For the A80 though, the same values for
4
mmc2 and mmc3 are available on the same pins, with different mux values.
However, only mmc3 supports 8 bit DDR transfer modes.
Since preference for mmc3 over mmc2 is due to DDR transfer modes, just
set the drive strength to 40mA, which is needed for DDR.
This pinmux setting also includes the
mmc2_8bit_pins is used with eMMC chips, which also have a reset pin.
The MMC controller also has a reset output that is supported.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun9i-a80.dtsi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
Hi,
On 01/06/2016 08:13 AM, Chen-Yu Tsai wrote:
Secure Memory Touch Arbiter is the same thing as the TrustZone
Protection Controller found on A31/A31s.
Access to many peripherals on the H3 can be controlled by the SMTA,
and the settings default to secure access only.
This patch supports the
Hi,
On 01/06/2016 08:13 AM, Chen-Yu Tsai wrote:
Hi everyone,
This series enables PSCI support for the H3. Like other Allwinner SoCs,
the implementation only supports PSCI 0.1, specifically only secondary
CPU boot/hotplug.
Patch 1 supports the SMTA (previously called TZPC) TrustZone hardware
Thanks for explaining that Code Kipper!
With your help I have been able to get IR (mostly) working under 4.4.0 so I
have updated my 'Remote controlled BananaPi music alarm clock' guide here
with the details on how I bring up IR at boot under Arch:
Hi,
On Fri, Jan 22, 2016 at 9:23 AM, Siarhei Siamashka
wrote:
> On Thu, 21 Jan 2016 21:38:39 +0100
> Karsten Merker wrote:
>
>> Hello everybody,
>>
>> I have read today's IRC discussion about handling the regulator
>> control on the A64 via the
On Thu, 21 Jan 2016 21:38:39 +0100
Karsten Merker wrote:
> Hello everybody,
>
> I have read today's IRC discussion about handling the regulator
> control on the A64 via the SCPI protocol implemented by a
> firmware running on the "arisc"/AR100 (OpenRisc Core) embedded in
>
28 matches
Mail list logo