Addition of Policy and Caution to Porting Guide
# Porting Guide
## Contents
-> [Policy & Causion](policy--causion)
+> [Policy & Caution](policy--caution)
> [Kernel & System](#kernel--system)
> [File System](#file-system)
> [Network](#network)
> [Audio](#audio)
> [Confirmation of Porting](#confirmation-of-porting)
-## Policy & Causion
-1. Use driver, framework and system call APIs.
+## Policy & Caution
+1. Driver Implementation Recommendation
+Instead of hooking the default driver interface code (which is a part of SoC package) to the platform,
+it is advisable to include the drivers according the TizenRT platform driver model.
+
+2. New Application Inclusion
+It is a good practise to add the Kconfig entry. All application configurations and dependencies should be included properly.
+
+3. Use driver, framework and system call APIs
Don't call architecture codes from application directly. When protected build enables, it will be blocked.
+Application must call TizenRT driver interface to talk to underlying driver.
+
+4. Maintain TizenRT Code Structure
+It is not advised if addition of peripherals, new interfaces, new open source code etc are done by aligning to default board package structure.
+Understanding the TizenRT code structure and adhering to the structure helps in better architecture desgin and portability.
+
## Kernel & System
1. [How to add new board](HowToAddnewBoard.md)
