android/android_kernel_xiaomi_sm8450
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
1,012,954 Commits 2 Branches 0 Tags 2.3 GiB
C 97.8%
Assembly 1.2%
Shell 0.3%
Makefile 0.3%
Python 0.2%
Other 0.1%
4a9c90b0b7
Go to file
Visweswara Tanuku 4a9c90b0b7 serial: msm_geni_serial: Enable the clock divider in probe time 
Currently we will enable the clock and clock divider once UART port
is open and baud rate is set. But during boot time if we don't open
UART port and go for runtime suspend operation then we will get the
NOC issue, since we are reading register without turning on the clk.
To avoid NOC issue enable the clock and configure the clock divider
during probe time.

Change-Id: Ie907bf76c2257b31933a48a4c1fcfff2f9baceb7
Signed-off-by: Visweswara Tanuku <quic_vtanuku@quicinc.com>
2022-06-20 21:00:50 +05:30
android Merge keystone/android12-5.10-keystone-qcom-release.101+ (ac14ef0) into msm-5.10 2022-06-03 14:05:35 +05:30
arch Merge "neo: Add bq27xxx_battery.ko to modules.list of neo le/la" 2022-06-19 11:59:41 -07:00
block Merge tag 'android12-5.10.101_r00' into android12-5.10 2022-03-21 14:29:02 +01:00
certs Merge keystone/android12-5.10-keystone-qcom-release.66+ (3499d10) into msm-5.10 2021-10-28 12:35:06 +05:30
crypto This is the 5.10.100 stable release 2022-02-11 09:19:01 +01:00
Documentation Merge keystone/android12-5.10-keystone-qcom-release.101+ (ac14ef0) into msm-5.10 2022-06-03 14:05:35 +05:30
drivers serial: msm_geni_serial: Enable the clock divider in probe time 2022-06-20 21:00:50 +05:30
fs Merge keystone/android12-5.10-keystone-qcom-release.101+ (ac14ef0) into msm-5.10 2022-06-03 14:05:35 +05:30
include Merge "cnss2: loads different fw binary per running mode" 2022-06-15 03:14:46 -07:00
init Merge keystone/android12-5.10-keystone-qcom-release.101+ (ac14ef0) into msm-5.10 2022-06-03 14:05:35 +05:30
ipc shm: extend forced shm destroy to support objects from several IPC nses 2021-12-01 09:19:10 +01:00
kernel sched: walt: add nested spinlock api 2022-06-10 11:34:00 +05:30
lib Merge keystone/android12-5.10-keystone-qcom-release.101+ (49a1520) into msm-5.10 2022-05-04 21:38:11 +05:30
LICENSES
mm Merge keystone/android12-5.10-keystone-qcom-release.101+ (ac14ef0) into msm-5.10 2022-06-03 14:05:35 +05:30
net Merge "net: qrtr: Use xa_load in qrtr_get_service_id" 2022-06-16 06:59:11 -07:00
samples Merge tag 'android12-5.10.81_r00' into android12-5.10 2022-01-21 09:35:04 +01:00
scripts Merge "Merge keystone/android12-5.10-keystone-qcom-release.101+ (49a1520) into msm-5.10" 2022-05-05 13:50:36 -07:00
security This is the 5.10.101 stable release 2022-02-16 15:16:06 +01:00
sound Merge keystone/android12-5.10-keystone-qcom-release.101+ (49a1520) into msm-5.10 2022-05-04 21:38:11 +05:30
techpack
tools UPSTREAM: selftests/damon: support watermarks 2022-04-28 23:09:16 +08:00
usr FROMLIST: kbuild: Add environment variables for userprogs flags 2022-05-10 16:09:36 +00:00
virt KVM: eventfd: Fix false positive RCU usage warning 2022-02-16 12:54:20 +01:00
.clang-format
.cocciconfig
.get_maintainer.ignore
.gitattributes
.gitignore ANDROID: Add build.config.msm.* to .gitignore 2021-07-07 19:14:24 +00:00
.mailmap
Android.bp Android.bp: headers_install.sh: Use environment for unifdef tool 2021-02-18 09:36:58 -08:00
build.config.aarch64 ANDROID: arm64: enable compat vdso 2021-05-13 09:14:25 -07:00
build.config.allmodconfig ANDROID: allmodconfig: drop openssl from ADDITIONAL_HOST_TOOLS 2021-03-04 20:48:17 +00:00
build.config.allmodconfig.aarch64
build.config.allmodconfig.arm
build.config.allmodconfig.x86_64
build.config.amlogic ANDROID: GKI: amlogic: add DTB overlays 2021-02-12 10:08:04 +01:00
build.config.anorak build.config: Enable DTB Overlay for Anorak 2022-03-16 08:38:51 +05:30
build.config.arm ANDROID: enable LLVM_IAS=1 for clang's integrated assembler for arm 2021-03-24 09:21:58 -07:00
build.config.common ANDROID: fix KCFLAGS override by __ANDROID_COMMON_KERNEL__ 2022-04-29 20:20:21 +00:00
build.config.db845c ANDROID: db845c: Use FRAGMENT_CONFIG 2021-02-10 06:08:17 +00:00
build.config.gki
build.config.gki_consolidate.aarch64 ANDROID: qki: Add consolidate config 2021-05-05 19:49:45 -07:00
build.config.gki_kasan ANDROID: build.config: Disable LTO for KASAN and Kprobes builds 2021-03-08 00:31:49 +00:00
build.config.gki_kasan.aarch64
build.config.gki_kasan.x86_64
build.config.gki_kprobes ANDROID: build.config: Disable LTO for KASAN and Kprobes builds 2021-03-08 00:31:49 +00:00
build.config.gki_kprobes.aarch64 ANDROID: Adding kprobes build configs for Cuttlefish 2021-03-03 02:03:02 +00:00
build.config.gki_kprobes.x86_64 ANDROID: Adding kprobes build configs for Cuttlefish 2021-03-03 02:03:02 +00:00
build.config.gki-debug.aarch64
build.config.gki-debug.x86_64
build.config.gki.aarch64 ANDROID: Add initial ASUS symbol list 2022-01-12 20:07:30 +00:00
build.config.gki.aarch64.fips140 ANDROID: ABI: add new symbols required by fips140.ko 2021-10-29 14:32:49 -07:00
build.config.gki.aarch64.fips140_eval_testing ANDROID: fips140: support "evaluation testing" builds via build.sh 2021-11-30 17:55:05 +00:00
build.config.gki.x86_64
build.config.hikey960 ANDROID: Add hikey960 build infrastructure file 2021-02-18 23:59:34 +00:00
build.config.khwasan ANDROID: Add a build config fragment for KHWASan. 2021-04-06 10:01:56 +00:00
build.config.msm.common build.config.anorak: Add build configs for Anorak 2022-02-11 10:40:47 +05:30
build.config.msm.gki build.config.msm.gki: Add other symbol lists 2021-10-07 11:36:14 -07:00
build.config.msm.lahaina build.config.msm.*: Add transition support to msm_kernel folder 2021-04-19 07:52:09 -07:00
build.config.msm.parrot build.config: Update default defconfig fragment for Parrot 2021-11-29 20:35:31 +05:30
build.config.msm.vm Merge "build.config: Enable hermetic toolchain on msm-kernel" 2021-10-27 19:23:46 -07:00
build.config.msm.waipio build.config.msm.waipio: Remove options to earlycon 2021-08-24 12:06:55 -07:00
build.config.msm.waipio.tuivm build.config.msm.waipio.tuivm: Update SVM build config for waipio 2022-02-21 11:44:02 +05:30
build.config.neo_la build: config: neo: Add support to compile neo la 2022-02-21 13:10:18 +05:30
build.config.neo_le build.config: neo: Add support to compile neo le 2022-03-08 14:09:19 +05:30
build.config.rockchip ANDROID: GKI: rockchip: Add build script 2021-10-25 08:57:33 +08:00
build.config.sxr.common build.config: Enable hermetic toolchain on msm-kernel 2021-10-19 09:00:06 -07:00
build.config.x86_64 ANDROID: build.config: Add vmlinux.symvers and modules.builtin to DIST_DIR 2021-04-15 10:24:17 +01:00
build.targets build: config: neo: Add support to compile neo la 2022-02-21 13:10:18 +05:30
COPYING
CREDITS
files_gki_aarch64.txt GKI: compare missed files to update files_gki_aarch64 2022-05-19 00:27:56 +05:30
Kbuild
Kconfig
kernel_headers.py
MAINTAINERS This is the 5.10.85 stable release 2021-12-14 15:11:46 +01:00
Makefile Merge "Merge keystone/android12-5.10-keystone-qcom-release.101+ (ac14ef0) into msm-5.10" 2022-06-07 07:33:37 -07:00
modules.list.anorak msm: qcom: Add hwspinlock, socinfo support anorak 2022-06-03 17:24:41 +05:30
modules.list.msm.lahaina modules.list: Add mindump to module list 2021-02-26 07:48:01 -08:00
modules.list.msm.parrot sched: Enable walt debug module in first stage 2022-05-23 08:34:02 +05:30
modules.list.msm.waipio modules.list.msm.waipio: Add thermal and BCL modules 2022-02-24 18:41:12 +05:30
modules.list.neo_la neo: Add bq27xxx_battery.ko to modules.list of neo le/la 2022-06-01 12:15:43 +05:30
modules.list.neo_le neo: Add bq27xxx_battery.ko to modules.list of neo le/la 2022-06-01 12:15:43 +05:30
modules.vendor_blocklist.msm.parrot modules.blocklist: Add blocklist for Parrot 2022-01-07 15:33:45 +05:30
modules.vendor_blocklist.msm.waipio modules.blocklist: Add limits_stat driver to block list 2022-03-15 22:07:36 +05:30
modules.vendor_blocklist.neo_la modules.blocklist: Add blocklist for NEO LA 2022-05-06 21:58:37 -07:00
modules.vendor_blocklist.neo_le modules.blocklist: Add blocklist for NEO LE 2022-06-14 12:26:46 +05:30
OWNERS ANDROID: Use authoritative Dr. No list from android-mainline 2021-07-22 15:25:25 +00:00
README
README.md

README.md

How do I submit patches to Android Common Kernels

  1. BEST: Make all of your changes to upstream Linux. If appropriate, backport to the stable releases. These patches will be merged automatically in the corresponding common kernels. If the patch is already in upstream Linux, post a backport of the patch that conforms to the patch requirements below.

    • Do not send patches upstream that contain only symbol exports. To be considered for upstream Linux, additions of EXPORT_SYMBOL_GPL() require an in-tree modular driver that uses the symbol -- so include the new driver or changes to an existing driver in the same patchset as the export.
    • When sending patches upstream, the commit message must contain a clear case for why the patch is needed and beneficial to the community. Enabling out-of-tree drivers or functionality is not not a persuasive case.

  2. LESS GOOD: Develop your patches out-of-tree (from an upstream Linux point-of-view). Unless these are fixing an Android-specific bug, these are very unlikely to be accepted unless they have been coordinated with kernel-team@android.com. If you want to proceed, post a patch that conforms to the patch requirements below.

Common Kernel patch requirements

  • All patches must conform to the Linux kernel coding standards and pass script/checkpatch.pl
  • Patches shall not break gki_defconfig or allmodconfig builds for arm, arm64, x86, x86_64 architectures (see https://source.android.com/setup/build/building-kernels)
  • If the patch is not merged from an upstream branch, the subject must be tagged with the type of patch: UPSTREAM:, BACKPORT:, FROMGIT:, FROMLIST:, or ANDROID:.
  • All patches must have a Change-Id: tag (see https://gerrit-review.googlesource.com/Documentation/user-changeid.html)
  • If an Android bug has been assigned, there must be a Bug: tag.
  • All patches must have a Signed-off-by: tag by the author and the submitter

Additional requirements are listed below based on patch type

Requirements for backports from mainline Linux: UPSTREAM:, BACKPORT:

  • If the patch is a cherry-pick from Linux mainline with no changes at all
    • tag the patch subject with UPSTREAM:.
    • add upstream commit information with a (cherry picked from commit ...) line
    • Example:
      • if the upstream commit message is
        important patch from upstream

        This is the detailed description of the important patch

        Signed-off-by: Fred Jones <fred.jones@foo.org>
  • then Joe Smith would upload the patch for the common kernel as
        UPSTREAM: important patch from upstream

        This is the detailed description of the important patch

        Signed-off-by: Fred Jones <fred.jones@foo.org>

        Bug: 135791357
        Change-Id: I4caaaa566ea080fa148c5e768bb1a0b6f7201c01
        (cherry picked from commit c31e73121f4c1ec41143423ac6ce3ce6dafdcec1)
        Signed-off-by: Joe Smith <joe.smith@foo.org>
  • If the patch requires any changes from the upstream version, tag the patch with BACKPORT: instead of UPSTREAM:.
    • use the same tags as UPSTREAM:
    • add comments about the changes under the (cherry picked from commit ...) line
    • Example:
        BACKPORT: important patch from upstream

        This is the detailed description of the important patch

        Signed-off-by: Fred Jones <fred.jones@foo.org>

        Bug: 135791357
        Change-Id: I4caaaa566ea080fa148c5e768bb1a0b6f7201c01
        (cherry picked from commit c31e73121f4c1ec41143423ac6ce3ce6dafdcec1)
        [joe: Resolved minor conflict in drivers/foo/bar.c ]
        Signed-off-by: Joe Smith <joe.smith@foo.org>

Requirements for other backports: FROMGIT:, FROMLIST:,

  • If the patch has been merged into an upstream maintainer tree, but has not yet been merged into Linux mainline
    • tag the patch subject with FROMGIT:
    • add info on where the patch came from as (cherry picked from commit <sha1> <repo> <branch>). This must be a stable maintainer branch (not rebased, so don't use linux-next for example).
    • if changes were required, use BACKPORT: FROMGIT:
    • Example:
      • if the commit message in the maintainer tree is
        important patch from upstream

        This is the detailed description of the important patch

        Signed-off-by: Fred Jones <fred.jones@foo.org>
  • then Joe Smith would upload the patch for the common kernel as
        FROMGIT: important patch from upstream

        This is the detailed description of the important patch

        Signed-off-by: Fred Jones <fred.jones@foo.org>

        Bug: 135791357
        (cherry picked from commit 878a2fd9de10b03d11d2f622250285c7e63deace
         https://git.kernel.org/pub/scm/linux/kernel/git/foo/bar.git test-branch)
        Change-Id: I4caaaa566ea080fa148c5e768bb1a0b6f7201c01
        Signed-off-by: Joe Smith <joe.smith@foo.org>
  • If the patch has been submitted to LKML, but not accepted into any maintainer tree
    • tag the patch subject with FROMLIST:
    • add a Link: tag with a link to the submittal on lore.kernel.org
    • add a Bug: tag with the Android bug (required for patches not accepted into a maintainer tree)
    • if changes were required, use BACKPORT: FROMLIST:
    • Example:
        FROMLIST: important patch from upstream

        This is the detailed description of the important patch

        Signed-off-by: Fred Jones <fred.jones@foo.org>

        Bug: 135791357
        Link: https://lore.kernel.org/lkml/20190619171517.GA17557@someone.com/
        Change-Id: I4caaaa566ea080fa148c5e768bb1a0b6f7201c01
        Signed-off-by: Joe Smith <joe.smith@foo.org>

Requirements for Android-specific patches: ANDROID:

  • If the patch is fixing a bug to Android-specific code
    • tag the patch subject with ANDROID:
    • add a Fixes: tag that cites the patch with the bug
    • Example:
        ANDROID: fix android-specific bug in foobar.c

        This is the detailed description of the important fix

        Fixes: 1234abcd2468 ("foobar: add cool feature")
        Change-Id: I4caaaa566ea080fa148c5e768bb1a0b6f7201c01
        Signed-off-by: Joe Smith <joe.smith@foo.org>
  • If the patch is a new feature
    • tag the patch subject with ANDROID:
    • add a Bug: tag with the Android bug (required for android-specific features)