Initial commit
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..3605a3a
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,2 @@
+/bazel-*
+*.swp
diff --git a/AUTHORS b/AUTHORS
new file mode 100644
index 0000000..49ae2cd
--- /dev/null
+++ b/AUTHORS
@@ -0,0 +1,9 @@
+# This is the list of Tensorflow's significant contributors.
+#
+# This does not necessarily list everyone who has contributed code,
+# especially since many employees of one corporation may be contributing.
+# To see the full list of contributors, see the revision history in
+# source control.
+
+Google LLC
+Yuan Tang <terrytangyuan@gmail.com>
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000..a1e4205
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,373 @@
+# How to Contribute
+
+We'd love to accept your patches and contributions to this project. There are
+just a few small guidelines you need to follow.
+
+## Contributor License Agreement
+
+Contributions to this project must be accompanied by a Contributor License
+Agreement (CLA). You (or your employer) retain the copyright to your
+contribution; this simply gives us permission to use and redistribute your
+contributions as part of the project. Head over to
+<https://cla.developers.google.com/> to see your current agreements on file or
+to sign a new one.
+
+You generally only need to submit a CLA once, so if you've already submitted one
+(even if it was for a different project), you probably don't need to do it
+again.
+
+## Community Guidelines
+
+This project follows
+[Google's Open Source Community Guidelines](https://opensource.google/conduct/).
+
+# Code Contribution Guidelines
+
+We provide some general guidelines with the goal of enabling community
+contributions while still maintaining code health, maintainability, and
+consistency in style.
+
+Please note that while these guidelines may seem onerous to some developers,
+they are derived from Google's software engineering best practices.
+
+Before we describe project-specific guidelines, we recommend that external
+contributors read these tips from the Google Testing Blog:
+
+* [Code Health: Providing Context with Commit Messages and Bug Reports](https://testing.googleblog.com/2017/09/code-health-providing-context-with.html)
+* [Code Health: Understanding Code In Review](https://testing.googleblog.com/2018/05/code-health-understanding-code-in-review.html)
+* [Code Health: Too Many Comments on Your Code Reviews?](https://testing.googleblog.com/2017/06/code-health-too-many-comments-on-your.html)
+* [Code Health: To Comment or Not to Comment?](https://testing.googleblog.com/2017/07/code-health-to-comment-or-not-to-comment.html)
+
+We also recommend that contributors take a look at the
+[Tensorflow Contributing Guidelines](https://github.com/tensorflow/tensorflow/blob/master/CONTRIBUTING.md).
+
+## General Pull Request Guidelines
+
+We strongly recommend that contributors:
+
+1. Initiate a conversation with the TFLM team via a
+ [TF Lite Micro Github issue](https://github.com/tensorflow/tensorflow/issues/new?labels=comp%3Amicro&template=70-tflite-micro-issue.md)
+ as early as possible.
+
+ * This enables us to give guidance on how to proceed, prevent duplicated
+ effort and also point to alternatives as well as context if we are not
+ able to accept a particular contribution at a given time.
+
+ * Ideally, you should make an issue ***before*** starting to work on a
+ pull request and provide context on both what you want to contribute and
+ why.
+
+1. Once step 1. is complete and it is determined that a PR from an external
+ contributor is the way to go, please follow these guidelines from
+ [Google's Engineering Practices documentation](https://google.github.io/eng-practices/):
+
+ * [Send Small Pull Requests](https://google.github.io/eng-practices/review/developer/small-cls.html)
+
+ * If a pull request is doing more than one thing, the reviewer will
+ request that it be broken up into two or more PRs.
+
+ * [Write Good Pull Request Descriptions](https://google.github.io/eng-practices/review/developer/cl-descriptions.html)
+
+ * We require that all PR descriptions link to the github issue created
+ in step 1.
+
+ * While github offers flexibility in linking
+ [commits and issues](https://github.blog/2011-04-09-issues-2-0-the-next-generation/#commits-issues),
+ we require that the PR description have a separate line with either
+ `Fixes #nn` (if the PR fixes the issue) or `Issue #nn` if the PR
+ addresses some aspect of an issue without fixing it.
+
+ * We will be adding internal checks that automate this requirement by
+ matching the PR description to the regexp: `(Fixes|Issue) #`
+
+1. Unit tests are critical to a healthy codebase. PRs without tests should be
+ the exception rather than the norm. And contributions to improve, simplify,
+ or make the unit tests more exhaustive are welcome! Please refer to
+ [this guideline](https://google.github.io/eng-practices/review/developer/small-cls.html#test_code)
+ on how test code and writing small PRs should be reconciled.
+
+## Guidelines for Specific Contribution Categories
+
+We provide some additional guidelines for different categories of contributions.
+
+### Bug Fixes
+
+Pull requests that fix bugs are always welcome and often uncontroversial, unless
+there is a conflict between different requirements from the platform, or if
+fixing a bug needs a bigger architectural change.
+
+1. Create a
+ [TF Lite Micro Github issue](https://github.com/tensorflow/tensorflow/issues/new?labels=comp%3Amicro&template=70-tflite-micro-issue.md)
+ to determine the scope of the bug fix.
+1. Send a PR (if that is determined to be the best path forward).
+1. Bugfix PRs should be accompanied by a test case that fails prior to the fix
+ and passes with the fix. This validates that the fix works as expected, and
+ helps prevent future regressions.
+
+### Reference Kernel Implementations
+
+Pull requests that port reference kernels from TF Lite Mobile to TF Lite Micro
+are welcome once we have enough context from the contributor on why the
+additional kernel is needed.
+
+1. Please create a
+ [TF Lite Micro Github issue](https://github.com/tensorflow/tensorflow/issues/new?labels=comp%3Amicro&template=70-tflite-micro-issue.md)
+ before starting on any such PRs with as much context as possible, such as:
+
+ * What is the model architecture?
+ * What is the application that you are targetting?
+ * What embedded target(s) are you planning to run on?
+ * Motivate your use-case and the need for adding support for this
+ additional OP.
+
+1. In the interest of having
+ [small pull requests](https://google.github.io/eng-practices/review/developer/small-cls.html),
+ limit each pull request to porting a single kernel (and the corresponding
+ test).
+
+1. TODO(b/165627437): Create and link to a guide to porting reference ops.
+
+### Optimized Kernel Implementations
+
+In order to have the TFLM codebase be a central repository of optimized kernel
+implementations, we would like to make some improvements to the current
+infrastructure to enable adding and maintaining optimized kernel implementations
+in a scalable way.
+
+Until that work is complete, we are requesting a ***pause*** on contributions that
+add new optimized kernel implementations. We plan to make these improvements by
+October 2020 and will provide additional guidelines at that time.
+
+* If you would like to have an exception to this pause, with the understanding
+ that your optimized kernels will break as we improve the underlying
+ framework, then please send an email to the [SIG Micro email
+ group](https://groups.google.com/a/tensorflow.org/g/micro) to figure out
+ a middle ground.
+
+* Every optimized kernel directory must have a README.md with the github IDs
+ of the maintainers and any other relevant documentation. PRs that add
+ maintainers to the existing optimized kernels are always welcome.
+
+### New Target / Platform / IDE / Examples
+
+As discussed in the
+[SIG-micro Aug 12, 2020 meeting](http://doc/1YHq9rmhrOUdcZnrEnVCWvd87s2wQbq4z17HbeRl-DBc),
+we are currently ***pausing*** accepting pull requests that add new targets,
+platforms, IDE integration or examples while we revisit some of the
+infrastructure to enable us to make this process easier and more scalable.
+
+In the meantime, snapshotting and/or forking the tensorflow repo could be a
+viable way to prototype platform support.
+
+Having said that, we still invite
+[TF Lite Micro Github issues](https://github.com/tensorflow/tensorflow/issues/new?labels=comp%3Amicro&template=70-tflite-micro-issue.md)
+on this topic as we would like to enable such integration in the future.
+
+### New Features
+
+As discussed in the
+[SIG-micro Aug 12, 2020 meeting](http://doc/1YHq9rmhrOUdcZnrEnVCWvd87s2wQbq4z17HbeRl-DBc),
+we are currently ***pausing*** accepting pull requests that add new features while
+we revisit some of the infrastructure to enable us to make this process easier
+and more scalable.
+
+Having said that, we still invite feature requests via
+[TF Lite Micro Github issues](https://github.com/tensorflow/tensorflow/issues/new?labels=comp%3Amicro&template=70-tflite-micro-issue.md)
+to determine if the requested feature aligns with the TFLM roadmap.
+
+# Development Workflow Notes
+
+## Initial Setup
+
+Below are some tips that might be useful and improve the development experience.
+
+* Add the [Refined GitHub](https://github.com/sindresorhus/refined-github)
+ plugin to make the github experience even better.
+
+* Code search the [TfLite Micro codebase](https://sourcegraph.com/github.com/tensorflow/tensorflow@master/-/tree/tensorflow/lite/micro)
+ on Sourcegraph. And optionally install the [plugin that enables GitHub integration](https://docs.sourcegraph.com/integration/github#github-integration-with-sourcegraph).
+
+* Install [bazel](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/tools/ci_build/install/install_bazel.sh) and [buildifier](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/tools/ci_build/install/install_buildifier.sh).
+
+* Install the latest clang and clang-format. For example,
+ [here](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/tools/ci_build/Dockerfile.micro)
+ is the what we do for the TFLM continuous integration Docker container.
+
+* Get a copy of [cpplint](https://github.com/google/styleguide/tree/gh-pages/cpplint)
+
+* Add a git hook to check for code style etc. prior to creating a pull request:
+ ```
+ cp tensorflow/lite/micro/tools/dev_setup/pre-push.tflm .git/hooks/pre-push
+ ```
+
+## Before submitting your PR
+
+1. Run in-place clang-format on all the files that are modified in your git
+ tree with
+
+ ```
+ clang-format -i -style=google `git ls-files -m | grep "\.cc"`
+ clang-format -i -style=google `git ls-files -m | grep "\.h"`
+ ```
+
+1. Make sure your code is lint-free.
+
+ ```
+ cpplint.py `git ls-files -m`
+ ```
+
+1. Run all the tests for x86, and any other platform that you are modifying.
+
+ ```
+ tensorflow/lite/micro/tools/ci_build/test_x86.sh
+ ```
+
+ Please check the READMEs in the optimized kernel directories for specific
+ instructions.
+
+1. Sometimes, bugs are caught by the sanitizers that can go unnoticed
+ via the Makefile. To run a test with the different sanitizers, use the
+ following commands (replace `micro_interpreter_test` with the target that you
+ want to test:
+
+ ```
+ CC=clang bazel run --config=asan tensorflow/lite/micro:micro_interpreter_test
+ CC=clang bazel run --config=msan tensorflow/lite/micro:micro_interpreter_test
+ CC=clang bazel run --config=ubsan tensorflow/lite/micro:micro_interpreter_test
+ ```
+
+## During the PR review
+
+1. Do not change the git version history.
+
+ * Always merge upstream/master (***do not rebase***) and no force-pushes
+ please.
+
+ * Having an extra merge commit it ok as the github review tool handles
+ that gracefully.
+
+ Assuming that you forked tensorflow and added a remote called upstream with:
+
+ `git remote add upstream https://github.com/tensorflow/tensorflow.git`
+
+ Fetch the latest changes from upstream and merge into your local branch.
+
+ ```
+ git fetch upstream
+ git merge upstream/master
+ ```
+
+ In case of a merge conflict, resolve via:
+
+ ```
+ git mergetool
+
+ # Use your favorite diff tools (e.g. meld) to resolve the conflicts.
+
+ git add <files that were manually resolved>
+
+ git commit
+ ```
+
+1. If a force push seems to be the only path forward, please stop and let your
+ PR reviewer know ***before*** force pushing. We will attempt to do the merge
+ for you. This will also help us better understand in what conditions a
+ force-push may be unavoidable.
+
+## Reviewer notes
+
+* [GIthub CLI](https://cli.github.com) can be useful to quickly checkout a PR
+ to test locally.
+
+ `gh pr checkout <PR number>`
+
+* Google engineers on the Tensorflow team will have the permissions to push
+ edits to most PRs. This can be useful to make some small fixes as a result
+ of errors due to internal checks that are not easily reproducible via
+ github.
+
+ One example of this is
+ [this comment](https://github.com/tensorflow/tensorflow/pull/38634#issuecomment-683190474).
+
+ And a sketch of the steps:
+
+ ```
+ git remote add <remote_name> git@github.com:<PR author>/tensorflow.git
+ git fetch <remote_name>
+
+ git checkout -b <local-branch-name> <remote_name>/<PR branch name>
+
+ # make changes and commit to local branch
+
+ # push changes to remove branch
+
+ git push <remote_name> <PR branch name>
+
+ # remove the temp remote to clean up your git environment.
+
+ git remote rm <remote_name>
+ ```
+
+## Python notes
+
+Most PRs for TensorFlow Lite Micro will be C++ only. Adding some notes on Python
+that can be expanded and improved as necessary.
+
+* [TensorFlow guide](https://www.tensorflow.org/community/contribute/code_style#python_style)
+ for Python development
+
+* [yapf](https://github.com/google/yapf/) should be used for formatting.
+
+ ```
+ yapf log_parser.py -i --style='{based_on_style: pep8, indent_width: 2}'
+ ```
+
+# Continuous Integration System
+
+* As a contributor, please make sure that the TfLite Micro build is green.
+ You can click on the details link to see what the errors are:
+
+[](https://storage.googleapis.com/tensorflow-kokoro-build-badges/tflite-micro.html)
+
+* Tests that are run as part of the CI are with the
+ [micro/tools/ci_build/test_all.sh](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/lite/micro/tools/ci_build/test_all.sh)
+ script when run with the `GITHUB_PRESUBMIT` command line parameter:
+ ```
+ tensorflow/lite/micro/tools/ci_build/test_all.sh GITHUB_PRESUBMIT
+ ```
+
+* If an error is not reproducible on your development machine, you can
+ recreate the docker container that is used on the CI servers.
+
+ * First, create a build a TFLM docker image with:
+ ```
+ tensorflow/tools/ci_build/ci_build.sh micro bash
+ ```
+ The second parameter to the ci_build.sh script is not important. It can
+ be any command.
+
+ * Next, mount the tensorflow repo on your machine to the docker container.
+ Please be careful (or make a separate clone of tensorflow) since any
+ changes docker container will also be reflected in the directory in the
+ host machine.
+ ```
+ docker run -v `pwd`:/tensorflow -it tf_ci.micro bash
+ # cd tensorflow
+ ```
+
+ * If you would prefer to not mount your local folder on the docker image,
+ you can also simply download the branch:
+ ```
+ docker run -it tf_ci.micro bash
+ # wget https://github.com/<github-username>/tensorflow/archive/<git-branch>.zip
+ # unzip <git-branch>.zip
+ # cd tensorflow-<git-branch>
+ ```
+
+ * Within the docker container, you can now run the TFLM test script, or
+ any other command that you would like to test. For example, the following
+ commands will run all of the TFLM checks:
+ ```
+ # tensorflow/lite/micro/tools/ci_build/test_all.sh GITHUB_PRESUBMIT
+ ```
+
diff --git a/LICENSE b/LICENSE
new file mode 100644
index 0000000..d645695
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,202 @@
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..a4de4ae
--- /dev/null
+++ b/README.md
@@ -0,0 +1,8 @@
+# TensorFlow Lite for Microcontrollers
+
+The TFLM code is currently in the process of being refactored out of the
+[Tensorflow github
+repository](https://github.com/tensorflow/tensorflow/tree/master/tensorflow/lite/micro)
+into a standalone repo. This refactoring is currently in the initial stages and
+is expected to be completed towards the end of June 2021.
+
