Currently, only esdhc1 is described in vfxxx.dtsi. This quick patch
adds support for esdhc0 also.
Regards,
-Cory
Cory Tusar (1):
ARM: dts: vfxxx: Include support for esdhc0 functionality.
arch/arm/boot/dts/vfxxx.dtsi | 11 +++++++++++
1 file changed, 11 insertions(+)
--
2.3.6
Extend the existing Vybrid eSDHC devicetree implementation to also
describe the esdhc0 functional block.
Tested on a custom VF610-based board with a Toshiba THGBM1G5D2EBAI7 eMMC
module attached to esdhc0.
Signed-off-by: Cory Tusar <redacted>
---
arch/arm/boot/dts/vfxxx.dtsi | 11 +++++++++++
1 file changed, 11 insertions(+)
From: Stefan Agner <stefan@agner.ch> Date: 2015-07-09 06:16:33
On 2015-07-09 08:07, Holger Schurig wrote:
quoted
Cory Tusar (1):
ARM: dts: vfxxx: Include support for esdhc0 functionality.
arch/arm/boot/dts/vfxxx.dtsi | 11 +++++++++++
1 file changed, 11 insertions(+)
--
2.3.6
Your patch looks empty.
This is a cover letter which provides overview over a whole patchset.
The patch is a separate reply message of this mail (PATCH 1/1).
@Cory
However, it is unusual to use a cover letter when there is only a single
patch. If you want to add additional comments which should not be part
of the commit message, you can edit the patch and insert text after the
three dashes, just before the diffstat. This text won't be part of the
commit when applied later.
--
Stefan
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/09/2015 02:13 AM, Stefan Agner wrote:
On 2015-07-09 08:07, Holger Schurig wrote:
quoted
quoted
Cory Tusar (1):
ARM: dts: vfxxx: Include support for esdhc0 functionality.
arch/arm/boot/dts/vfxxx.dtsi | 11 +++++++++++
1 file changed, 11 insertions(+)
--
2.3.6
Your patch looks empty.
This is a cover letter which provides overview over a whole patchset.
The patch is a separate reply message of this mail (PATCH 1/1).
@Cory
However, it is unusual to use a cover letter when there is only a single
patch. If you want to add additional comments which should not be part
of the commit message, you can edit the patch and insert text after the
three dashes, just before the diffstat. This text won't be part of the
commit when applied later.
Hi Stefan,
Duly noted. Appreciate the feedback, and will keep in mind for next
time.
Best regards,
- -Cory
- --
Cory Tusar
Principal
PID 1 Solutions, Inc.
"There are two ways of constructing a software design. One way is to
make it so simple that there are obviously no deficiencies, and the
other way is to make it so complicated that there are no obvious
deficiencies." --Sir Charles Anthony Richard Hoare
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlWea6EACgkQHT1tsfGwHJ8CYACgqK20a6hhtl66aA+an5lWX4Ob
jTgAoKiygJTWpw9oYrmiZWk874tzkoZa
=YMvj
-----END PGP SIGNATURE-----
From: Stefan Agner <stefan@agner.ch> Date: 2015-07-09 15:10:38
On 2015-07-08 22:51, Cory Tusar wrote:
Extend the existing Vybrid eSDHC devicetree implementation to also
describe the esdhc0 functional block.
Tested on a custom VF610-based board with a Toshiba THGBM1G5D2EBAI7 eMMC
module attached to esdhc0.
Signed-off-by: Cory Tusar <redacted>
Looks good to me:
Acked-by: Stefan Agner <stefan@agner.ch>
On Wed, Jul 08, 2015 at 04:51:06PM -0400, Cory Tusar wrote:
Extend the existing Vybrid eSDHC devicetree implementation to also
describe the esdhc0 functional block.
Tested on a custom VF610-based board with a Toshiba THGBM1G5D2EBAI7 eMMC
module attached to esdhc0.
Signed-off-by: Cory Tusar <redacted>