Add 'arch/arm64/boot/dts/vendor/' from tag 'LA.UM.9.12.r1-13500-SMxx50.0'

# Ignore camera directory

qcom/camera

vendor := $(srctree)/$(src)

ifneq "$(wildcard $(vendor)/qcom)" ""

	subdir-y += qcom

endif

This NOTICE file contains certain notices of software components included

with the software that Qualcomm Technologies, Inc. ("Qualcomm Technologies") is required to

provide you. Notwithstanding anything in the notices in this file, your use

of these software components together with the Qualcomm Technologies software (Qualcomm Technologies

software hereinafter referred to as "Software") is subject to the terms of

your license from Qualcomm Technologies. Compliance with all copyright laws and software

license agreements included in the notice section of this file are the

responsibility of the user. Except as may be granted by separate express

written agreement, this file provides no license to any patents,

trademarks, copyrights, or other intellectual property.

Copyright (c) 2021 Qualcomm Technologies, Inc. All rights reserved.

Qualcomm is a registered trademark and registered service mark of

QUALCOMM Incorporated. All other trademarks and service marks are the

property of their respective owners.

________________________________________

NOTICES

________________________________________

/*

 * Copyright (C) 2008 Shanghai awinic technology co.,ltd. All rights reserved.

 *

 * Permission is hereby granted, free of charge, to any person obtaining a

 * copy of this software and associated documentation files (the "Software"),

 * to deal in the Software without restriction, including without limitation

 * the rights to use, copy, modify, merge, publish, distribute, sublicense,

 * and/or sell copies of the Software, and to permit persons to whom the

 * Software is furnished to do so, subject to the following conditions:

 *

 * The above copyright notice and this permission notice shall be

 * included in all copies or substantial portions of the Software.

 *

 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR

 * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,

 * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL

 * THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER

 * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING

 * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER

 * DEALINGS

 * IN THE SOFTWARE.

 */

  Devicetree (DT) ABI

I. Regarding stable bindings/ABI, we quote from the 2013 ARM mini-summit

   summary document:

     "That still leaves the question of, what does a stable binding look

     like?  Certainly a stable binding means that a newer kernel will not

     break on an older device tree, but that doesn't mean the binding is

     frozen for all time. Grant said there are ways to change bindings that

     don't result in breakage. For instance, if a new property is added,

     then default to the previous behaviour if it is missing. If a binding

     truly needs an incompatible change, then change the compatible string

     at the same time.  The driver can bind against both the old and the

     new. These guidelines aren't new, but they desperately need to be

     documented."

II.  General binding rules

  1) Maintainers, don't let perfect be the enemy of good.  Don't hold up a

     binding because it isn't perfect.

  2) Use specific compatible strings so that if we need to add a feature (DMA)

     in the future, we can create a new compatible string.  See I.

  3) Bindings can be augmented, but the driver shouldn't break when given

     the old binding. ie. add additional properties, but don't change the

     meaning of an existing property. For drivers, default to the original

     behaviour when a newly added property is missing.

  4) Don't submit bindings for staging or unstable.  That will be decided by

     the devicetree maintainers *after* discussion on the mailinglist.

III. Notes

  1) This document is intended as a general familiarization with the process as

     decided at the 2013 Kernel Summit.  When in doubt, the current word of the

     devicetree maintainers overrules this document.  In that situation, a patch

     updating this document would be appreciated.

* ARC HS Performance Counters

The ARC HS can be configured with a pipeline performance monitor for counting

CPU and cache events like cache misses and hits. Like conventional PCT there

are 100+ hardware conditions dynamically mapped to up to 32 counters.

It also supports overflow interrupts.

Required properties:

- compatible : should contain

	"snps,archs-pct"

Example:

pmu {

        compatible = "snps,archs-pct";

};