Re: Sparse GPIO maps with pinctrl-msm.c?

[Andy Gross <andy.gross@xxxxxxxxxx>]

On 16 June 2017 at 12:17, Timur Tabi <timur@xxxxxxxxxxxxxx> wrote:
> On 6/16/17 11:06 AM, Bjorn Andersson wrote:
>>
>> Exposing a subset of GPIOs with a different numbering than what's in the
>> hardware documentation is going to be quite confusing for the users.
>
>
> I agree, and that's why I was hoping to expose only the qdss_tracedata pins.
>
>> Just to confirm, are the qdss_tracedata the only GPIOs that you want to
>> expose from the TLMM now? Are those consecutive?
>
>
> Well, ideally would like to expose only those pins that are:
>
> 1) Approved by the XPU

How do you know what this is?  And this changes based on the TZ load.

> and
>
> 2) Already set to function 0 on boot
>
> Unfortunately, doing both of these would require significant changes to
> pinctrl-msm.  Considering how unimportant this feature is (we don't need the
> TLMM any more for normal operations), I don't really want to invest too much
> time in it.
>
> So assuming I can get approval from all stakeholders, all I want to do is
> expose the qdss_tracedata[0..n-1] pins as gpios 0..n-1.
>
>
> --
> Sent by an employee of the Qualcomm Innovation Center, Inc.
> The Qualcomm Innovation Center, Inc. is a member of the
> Code Aurora Forum, hosted by The Linux Foundation.
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html