All of lore.kernel.org
 help / color / mirror / Atom feed
From: Archit Taneja <archit@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [RFC v2 2/5] OMAPDSS: DT: Get source endpoint by matching reg-id
Date: Tue, 27 May 2014 16:21:47 +0530	[thread overview]
Message-ID: <53846E43.7000808@ti.com> (raw)
In-Reply-To: <538467E0.2000305@ti.com>

On Tuesday 27 May 2014 03:54 PM, Tomi Valkeinen wrote:
> On 27/05/14 12:49, Archit Taneja wrote:
>> On Tuesday 27 May 2014 02:04 PM, Tomi Valkeinen wrote:
>
>>> Hmm, maybe the above function, and the helper functions, should be
>>> changed a bit more, so that this function would do:
>>>
>>> ep = omapdss_of_get_first_endpoint(node);
>>> src_port = omapdss_of_get_remote_port(ep);
>>> src = omap_dss_find_output_by_port_node(src_port);
>>
>> src_port will be just on level up(the parent node), the source node will
>> be still a couple of hops up.
>>
>> Getting the source node would require us to do some DT related hopping
>> in omap_dss_find_output_by_port_node(). And it'll also require parsing
>> of the dss output_list in output.c. I'm worried it'll be a bit messy,
>> and we might end up adding some DT parsing in output.c
>
> But now the function above is messy =).
>
> Well, I haven't thought what the code would actually be. I just thought
> the functions I wrote would be logical in this context. As the output
> omap_dss_device more or less is a "port", it would feel logical to ask
> for the omap_dss_device by giving the port node.
>
> But you're right, the function in output.c would need to do a bit more
> than now. Then again, we could add helper functions to dss-of.c, so that
> output.c wouldn't need to do them manually.
>
> I guess the helper funcs in this case would be:
>
> struct device_node *dss_of_port_get_parent_device(struct device_node *port);
>
> int dss_of_port_get_port_number(struct device_node *port);

These look fine. I'll update the patch.

Archit


  reply	other threads:[~2014-05-27 10:53 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08  9:15 [RFC 1/6] omapdss: remove check for simpler port/endpoint binding Archit Taneja
2014-05-08  9:27 ` Archit Taneja
2014-05-08  9:15 ` [RFC 2/6] omapdss: add init port functions for different omap revs Archit Taneja
2014-05-08  9:27   ` Archit Taneja
2014-05-20  8:04   ` Tomi Valkeinen
2014-05-20  8:04     ` Tomi Valkeinen
2014-05-20  9:31     ` Archit Taneja
2014-05-20  9:43       ` Archit Taneja
2014-05-08  9:15 ` [RFC 3/6] omapdss: DT: Get source endpoint by matching reg-id Archit Taneja
2014-05-08  9:27   ` Archit Taneja
2014-05-08  9:15 ` [RFC 4/6] omapdss: DPI: support multiple DPI instances Archit Taneja
2014-05-08  9:27   ` Archit Taneja
2014-05-08  9:15 ` [RFC 5/6] omapdss: DPI: make dpi_get_channel take DPI reg-id Archit Taneja
2014-05-08  9:27   ` Archit Taneja
2014-05-08  9:15 ` [RFC 6/6] omapdss: DSS: add reg-id param to dpi_select_source Archit Taneja
2014-05-08  9:27   ` Archit Taneja
2014-05-09  9:59 ` [RFC 1/6] omapdss: remove check for simpler port/endpoint binding Tomi Valkeinen
2014-05-09  9:59   ` Tomi Valkeinen
2014-05-26  9:28 ` [RFC v2 1/5] OMAPDSS: DSS: init dss ports cleanly Archit Taneja
2014-05-26  9:28   ` [RFC v2 2/5] OMAPDSS: DT: Get source endpoint by matching reg-id Archit Taneja
2014-05-27  8:34     ` Tomi Valkeinen
2014-05-27  9:49       ` Archit Taneja
2014-05-27 10:24         ` Tomi Valkeinen
2014-05-27 10:51           ` Archit Taneja [this message]
2014-05-26  9:28   ` [RFC v2 3/5] OMAPDSS: DPI: support multiple DPI instances Archit Taneja
2014-05-27  9:04     ` Tomi Valkeinen
2014-05-27  9:27       ` Archit Taneja
2014-05-26  9:28   ` [RFC v2 4/5] OMAPDSS: DPI: make dpi_get_channel take DPI reg-id Archit Taneja
2014-05-26  9:28   ` [RFC v2 5/5] OMAPDSS: DSS: add reg-id param to dpi_select_source Archit Taneja
2014-05-27  8:24   ` [RFC v2 1/5] OMAPDSS: DSS: init dss ports cleanly Tomi Valkeinen
2014-05-27 11:42     ` Archit Taneja
2014-06-04  6:40   ` [PATCH v3 0/7] OMAPDSS: Support multiple DPI instances Archit Taneja
2014-06-04  6:52     ` Archit Taneja
2014-06-04  6:40     ` [PATCH v3 1/7] OMAPDSS: DPI: Use DPI driver data Archit Taneja
2014-06-04  6:52       ` Archit Taneja
2014-06-04  6:40     ` [PATCH v3 2/7] OMAPDSS: DPI: Allocate " Archit Taneja
2014-06-04  6:52       ` Archit Taneja
2014-06-04  6:40     ` [PATCH v3 3/7] OMAPDSS: DPI: Store dpi_data pointer in the DT port's data Archit Taneja
2014-06-04  6:52       ` Archit Taneja
2014-06-04  6:41     ` [PATCH v3 4/7] OMAPDSS: DSS: init dss ports cleanly Archit Taneja
2014-06-04  6:53       ` Archit Taneja
2014-06-26 12:16       ` Tomi Valkeinen
2014-06-26 12:16         ` Tomi Valkeinen
2014-06-04  6:41     ` [PATCH v3 5/7] OMAPDSS: DT: Get source endpoint by matching reg-id Archit Taneja
2014-06-04  6:53       ` Archit Taneja
2014-06-04  6:41     ` [PATCH v3 6/7] OMAPDSS: DPI: Add support for multiple instances Archit Taneja
2014-06-04  6:53       ` Archit Taneja
2014-06-26 12:15       ` Tomi Valkeinen
2014-06-26 12:15         ` Tomi Valkeinen
2014-06-04  6:41     ` [PATCH v3 7/7] omapdss: DSS: add reg-id param to dpi_select_source Archit Taneja
2014-06-04  6:53       ` Archit Taneja
2014-06-26 12:28     ` [PATCH v3 0/7] OMAPDSS: Support multiple DPI instances Tomi Valkeinen
2014-06-26 12:28       ` Tomi Valkeinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53846E43.7000808@ti.com \
    --to=archit@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tomi.valkeinen@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.