On 5 January 2016 at 13:05, Andre Przywara wrote:
> Hi Michal,
>
> thanks for your input!
>
> On 04/01/16 21:36, Michal Suchanek wrote:
>> Hello,
>>
>> On 4 January 2016 at 18:27, Vishnu Patekar
>> wrote:
>>> Hello Andre,
>>> This is
Hi Michal,
thanks for your input!
On 04/01/16 21:36, Michal Suchanek wrote:
> Hello,
>
> On 4 January 2016 at 18:27, Vishnu Patekar
> wrote:
>> Hello Andre,
>> This is something we can do for future SOCs.
>>
>> On 4 Jan 2016 19:02, "Andre Przywara"
Hi,
while looking at the Allwinner A64 SoC support, I was wondering why we
would actually need a pinctrl driver (file) for each and every Allwinner
SoC that we support.
Looking at both the A20 and the A64 doc I don't see any differences in
the port controller implementation apart from the actual
Hello,
On 4 January 2016 at 18:27, Vishnu Patekar wrote:
> Hello Andre,
> This is something we can do for future SOCs.
>
> On 4 Jan 2016 19:02, "Andre Przywara" wrote:
>>
>> Hi,
>>
>> while looking at the Allwinner A64 SoC support, I was
Hi Andre,
On Mon, Jan 4, 2016 at 10:02 PM, Andre Przywara wrote:
> Hi,
>
> while looking at the Allwinner A64 SoC support, I was wondering why we
> would actually need a pinctrl driver (file) for each and every Allwinner
> SoC that we support.
> Looking at both the A20
On Mon, Jan 4, 2016 at 7:02 PM, Andre Przywara wrote:
> Hi,
>
> while looking at the Allwinner A64 SoC support, I was wondering why we
> would actually need a pinctrl driver (file) for each and every Allwinner
> SoC that we support.
> Looking at both the A20 and the A64
Hello Andre,
This is something we can do for future SOCs.
On 4 Jan 2016 19:02, "Andre Przywara" wrote:
>
> Hi,
>
> while looking at the Allwinner A64 SoC support, I was wondering why we
> would actually need a pinctrl driver (file) for each and every Allwinner
> SoC that