Rework for AGL UCB integration

Changes include:
- The provided kernel patches have been reworked to not modify the
  salvator-x(s) devicetree source, but to introduce new files for the
  reference hardware instead.  There is some possibility that the
  reference hardware devicetree could be based off the the salvator-x
  with some work and perhaps splitting of the salvator-x source, but
  for now the aim is to avoid breaking the salvator-x(s) with the
  reference hardware changes.
- The modifications to the r8a7795 pinctrl driver have been replaced
  with a splitting of the USB interface OVC pins into their own pin
  groups, which has previously been done for other older Renesas
  hardware.  This allows booting the reference hardware off of the
  same kernel as other H3 boards, at the expense of minor devicetree
  modifications for them (e.g. h3ulcb).  There is likely some more
  work required if this needs to be upstreamed, as the ulcb.dtsi
  changes would mean that the pinctrl drivers for M3 would also need
  the new pin groups.
- All changes for the ST asm330lhh driver addtion have been moved to
  that patch to the kernel.
- A machine conf file has been added for "agl-refhw-h3", and the
  firmware documentation updated to document how to set up a build of
  the firmware using it.  This is required due to the firmware options
  from this layer's arm-trusted-firmware bbappend not being compatible
  with other H3 boards (eMMC versus Hyperflash boot).  A definition
  of the COMPATIBLE_MACHINE variable has been added to that bbappend
  to make sure that attempting to use it with another H3 machine will
  trigger an error.  In AGL, the bbappend will need to be masked out
  with BBMASK for now.
- The top-level README file has been updated to reflect the expected
  integration in AGL.

Bug-AGL: SPEC-3658

Signed-off-by: Scott Murray <scott.murray@konsulko.com>

1 files changed, 54 insertions, 4 deletions

diff --git a/meta-agl-refhw-gen3/docs/ReferenceHW_Rcar_gen3.md b/meta-agl-refhw-gen3/docs/ReferenceHW_Rcar_gen3.md
index 9e826dc..92d3642 100644
--- a/meta-agl-refhw-gen3/docs/ReferenceHW_Rcar_gen3.md
+++ b/meta-agl-refhw-gen3/docs/ReferenceHW_Rcar_gen3.md
@@ -1,4 +1,4 @@
-# Reference Hardware Board
+# Reference Hardware Board
 
 - [About](#about)
 - [Difference to Salvator-XS When Flashing Firmware](#difference-to-salvator-xs-when-flashing-firmware)
@@ -42,6 +42,56 @@ using serial download.
 Output the following image.
 ./AArch64_output/AArch64_Flash_writer_SCIF_DUMMY_CERT_E6300400_salvator-x.mot
 
+## How to build the Firmware
+
+1. In a temporary working directory, clone poky the poky repository and check out the dunfell branch:
+```
+	git clone git://git.yoctoproject.org/poky
+	cd poky
+	git checkout dunfell
+	..
+```
+2.  Clone the Renesas BSP and it's dependent layers:
+```
+	git clone https://github.com/renesas-rcar/meta-renesas
+	cd meta-renesas
+	git checkout dunfell-dev-4.14
+	cd ..
+	git clone git://git.openembedded.org/meta-openembedded
+	cd meta-openembedded
+	git checkout dunfell
+	cd ..
+```
+3. Clone the reference hardware BSP layer:
+```
+	git clone https://gerrit.automotivelinux.org/gerrit/AGL/meta-agl-refhw
+```
+4. Create a build environment:
+```
+	. ./poky/oe-init-build-env build
+```
+5. Add the layers to `conf/bblayers.conf`, the `BBLAYERS` variable definition should look like:
+```
+	BBLAYERS ?= " \
+	  /home/user/workdir/poky/meta \
+	  /home/user/workdir/poky/meta-poky \
+	  /home/user/poky/meta-yocto-bsp \
+	  /home/user/workdir/meta-openembedded/meta-oe \
+	  /home/user/workdir/meta-openembedded/meta-python \
+	  /home/user/workdir/meta-renesas/meta-rcar-gen3 \
+	  /home/user/workdir/meta-agl-refhw/meta-agl-refhw-gen3 \
+	  "
+```
+6. Add the machine setting to `conf/local.conf`, for example:
+```
+	echo MACHINE=agl-refhw-h3 >> conf/local.conf
+```
+7. Build the firmware:
+```
+	bitbake arm-trusted-firmware u-boot
+```
+8. Afterwards, the firmware files will be in the directory `tmp/deploy/images/agl-refhw-h3`.
+
 ## How to Flash Firmware
 
 1. Connect reference hardware board to the development PC by using USB serial
@@ -129,10 +179,10 @@ Output the following image.
   Name					| Load address		| eMMC partition 	| Flash address		| Description
   --------------------------------------|-----------------------|-----------------------|-----------------------|-----------------------------
   bootparam_sa0-4x2g.srec		| H'E6320000		| 1			| H'000000		| Boot parameter
-  bl2-salvator-x-4x2g.srec		| H'E6304000		| 1			| H'00001E		| bl2 loader
+  bl2-agl-refhw-h3-4x2g.srec		| H'E6304000		| 1			| H'00001E		| bl2 loader
   cert_header_sa6-4x2g.srec		| H'E6320000		| 1			| H'000180		| Certification
-  bl31-salvator-x-4x2g.srec		| H'44000000		| 1			| H'000200		| bl3 loader
-  tee-salvator-x.srec			| H'44100000		| 1			| H'001000		| OP-Tee
+  bl31-agl-refhw-h3-4x2g.srec		| H'44000000		| 1			| H'000200		| bl3 loader
+  tee-agl-refhw-h3.srec			| H'44100000		| 1			| H'001000		| OP-Tee
   u-boot-elf-salvator-xs-4x2g.srec	| H'50000000		| 2			| H'000000		| U-boot
 
   You can find these firmwares in the AGL build directory $AGL_TOP/build/tmp/deploy/images/salvator-x