1. 09 11月, 2017 1 次提交
  2. 28 10月, 2015 2 次提交
  3. 19 6月, 2015 1 次提交
  4. 17 4月, 2013 1 次提交
    • V
      ARC: [kbuild] Avoid DTB rebuilds if DTS are untouched · a89516b3
      Vineet Gupta 提交于
      Currently, for every ARC kernel build I see the following:
      
      --------------->8-----------------
        DTB    arch/arc/boot/dts/angel4.dtb.S
        AS      arch/arc/boot/dts/angel4.dtb.o
        LD      arch/arc/boot/dts/built-in.o
      rm arch/arc/boot/dts/angel4.dtb.S        <-- forces rebuild next iter
        CHK     kernel/config_data.h
      --------------->8-----------------
      
      This is because *.dts.S is intermediate file in dtb generation and is by
      default deleted by make which needs a ".SECONDARY" hint to NOT do so.
      
      This could have ideally been done in scripts/Makefile.lib - for benefit
      of all, however .SECONDARY doesn't seem to work with wildcards.
      
      Thanks to Stephen for suggesting .SECONDARY (vs .PRECIOUS) and making
      that work using a non wildcard version in arch makefile.
      
      Thanks to James Hogan for pointing out that *.dtb.S now needs to be
      added to clean-files
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NVineet Gupta <vgupta@synopsys.com>
      a89516b3
  5. 16 2月, 2013 2 次提交
    • V
      ARC: [plat-arcfpga]: Enabling DeviceTree for Angel4 board · abe11dde
      Vineet Gupta 提交于
      * arc-uart platform device now populated dynamically, using
        of_platform_populate() - applies to any other device whatsoever.
      
      * uart in turn requires incore arc-intc to be also present in DT
      
      * A irq-domain needs to be instantiated for IRQ requests by DT probed
        device (e.g. arc-uart)
      
      TODO: switch over to linear irq domain once all devs have been
            transitioned to DT
      Signed-off-by: NVineet Gupta <vgupta@synopsys.com>
      Cc: Grant Likely <grant.likely@secretlab.ca>
      Cc: Arnd Bergmann <arnd@arndb.de>
      abe11dde
    • V
      ARC: [DeviceTree] Basic support · 999159a5
      Vineet Gupta 提交于
      This is minimal infrastructure needed for devicetree work.
      It uses an a sample "skeleton" devicetree - embedded in kernel image -
      to print the board, manufacturer by parsing the top-level "compatible"
      string.
      
      As of now we don't need any additional "board" specific "machine_desc".
      
      TODO: support interpreting the command line as boot-loader passed dtb
      Signed-off-by: NVineet Gupta <vgupta@synopsys.com>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Grant Likely <grant.likely@secretlab.ca>
      Cc: devicetree-discuss@lists.ozlabs.org
      Cc: Rob Herring <rob.herring@calxeda.com>
      Cc: James Hogan <james.hogan@imgtec.com>
      Reviewed-by: NRob Herring <rob.herring@calxeda.com>
      Reviewed-by: NJames Hogan <james.hogan@imgtec.com>
      999159a5