On Wed, Feb 1, 2017 at 9:27 PM, Rob Herring wrote:
> On Thu, Jan 26, 2017 at 10:16:13PM +0100, Rask Ingemann Lambertsen wrote:
>> The AXP808 does not support address space extension, but is otherwise
>> identical to the AXP806, including the chip ID, so add a compatible
>> string
On Wed, Feb 1, 2017 at 9:27 PM, Rob Herring wrote:
> On Thu, Jan 26, 2017 at 10:16:13PM +0100, Rask Ingemann Lambertsen wrote:
>> The AXP808 does not support address space extension, but is otherwise
>> identical to the AXP806, including the chip ID, so add a compatible
>> string for it to the
On Thu, Jan 26, 2017 at 10:16:13PM +0100, Rask Ingemann Lambertsen wrote:
> The AXP808 does not support address space extension, but is otherwise
> identical to the AXP806, including the chip ID, so add a compatible
> string for it to the binding.
>
> Signed-off-by: Rask Ingemann Lambertsen
On Thu, Jan 26, 2017 at 10:16:13PM +0100, Rask Ingemann Lambertsen wrote:
> The AXP808 does not support address space extension, but is otherwise
> identical to the AXP806, including the chip ID, so add a compatible
> string for it to the binding.
>
> Signed-off-by: Rask Ingemann Lambertsen
>
The AXP808 does not support address space extension, but is otherwise
identical to the AXP806, including the chip ID, so add a compatible
string for it to the binding.
Signed-off-by: Rask Ingemann Lambertsen
---
Documentation/devicetree/bindings/mfd/axp20x.txt | 7 ---
1
The AXP808 does not support address space extension, but is otherwise
identical to the AXP806, including the chip ID, so add a compatible
string for it to the binding.
Signed-off-by: Rask Ingemann Lambertsen
---
Documentation/devicetree/bindings/mfd/axp20x.txt | 7 ---
1 file changed, 4
6 matches
Mail list logo