From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BDC51C31E40 for ; Tue, 6 Aug 2019 06:41:32 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 94F932147A for ; Tue, 6 Aug 2019 06:41:32 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="PQB59KqE" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731908AbfHFGlb (ORCPT ); Tue, 6 Aug 2019 02:41:31 -0400 Received: from mail-pf1-f193.google.com ([209.85.210.193]:36548 "EHLO mail-pf1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731734AbfHFGlb (ORCPT ); Tue, 6 Aug 2019 02:41:31 -0400 Received: by mail-pf1-f193.google.com with SMTP id r7so40947402pfl.3; Mon, 05 Aug 2019 23:41:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=O7Wxe/wopuDLr6j5LeIpmGJxa41bzUArxht2aFk5QSM=; b=PQB59KqEEQ6y0YFrHhLO6+txcqFbBih2qQcVtibs659NMIAQoA/YBANqsk+eX0SCuW sbY5s48PsWRf99yFceRWzXQadQVb8U2KdQ8q5N/UC+OS70N9ZV3HvwGvO+3M/Xch9BlK anE08yqAnkcZ18O26SB/+Gjcpq4K06YY9aZnWnTdy+Wa0fG6zxZ9XbgvfBHtwfHLtab3 jt8HleZQrIUDKrcyd0EKiknFIxmyoeclUXM7WGS+onyhFtjlcA3xbvW/hYQGqUM1DSzg 4NZvoLpj01Kft8IYBqifjDaNJ0jIAe5TExtcC+IIoWzOyo6kpNrriZw+LRDwaIOTZ9AJ +UXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=O7Wxe/wopuDLr6j5LeIpmGJxa41bzUArxht2aFk5QSM=; b=DTbH6xCZGp9ZsdtS5MLdgsfwBvX+1BNfm2nS6RHCSJ2p0rMAp/tiOHpQcbwXSIIxv+ +3YCQwlsBe7JrO1PxjmbI4xojGRGA+eCKENUtR+Og2DhpNUDWPkPP12rqaKudMcybFmT H3ORoQwABq4iGCPIgJv/2hnW87Y7yo34S/cuh/mktK6y/Yf6Kz6jjUveVhvHvWyiMCDq VLIeQ84+S9M3yenc6TUCxfusJLGvHMV9o0kg1YfNp6RGt2GIscAXI6fbwCOoxhtSouzZ FDVI/pBzPlu1PRMiHkJk2fmlVwUhH6b3L8Eu0RO7I3MD5gS4TaVFXPMIvFRtJhBKMSNT T+ag== X-Gm-Message-State: APjAAAUR2yPpN/0IFFS6qcVnQy90L4dYUNg3+I3VH/no7weeIwQ/42MW sphu8uzfjh0RL8/7Q51htJFbBJIuO5GE5zWKTeE= X-Google-Smtp-Source: APXvYqwNrBeCBFk00MAwOwazzhjYBhn+KfLDMNZ9dnhN85lTl19ENdSbslLn8ga+DxdlH5db2IF4JBnKiLNcySs6fRY= X-Received: by 2002:a63:e54f:: with SMTP id z15mr1658530pgj.4.1565073690207; Mon, 05 Aug 2019 23:41:30 -0700 (PDT) MIME-Version: 1.0 References: <20190805233505.21167-1-slongerbeam@gmail.com> <20190805233505.21167-5-slongerbeam@gmail.com> In-Reply-To: <20190805233505.21167-5-slongerbeam@gmail.com> From: Andy Shevchenko Date: Tue, 6 Aug 2019 09:41:18 +0300 Message-ID: Subject: Re: [PATCH 04/22] media: Move v4l2_fwnode_parse_link from v4l2 to driver base To: Steve Longerbeam Cc: Linux Media Mailing List , Greg Kroah-Hartman , "Rafael J. Wysocki" , Hyun Kwon , Laurent Pinchart , Mauro Carvalho Chehab , Michal Simek , Philipp Zabel , Shawn Guo , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , NXP Linux Team , Len Brown , Sakari Ailus , Jacopo Mondi , Hans Verkuil , Heikki Krogerus , Andy Shevchenko , Enrico Weigelt , Thomas Gleixner , open list , "moderated list:ARM/ZYNQ ARCHITECTURE" , "open list:STAGING SUBSYSTEM" , "open list:ACPI" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 6, 2019 at 2:37 AM Steve Longerbeam wrote: > > There is nothing v4l2-specific about v4l2_fwnode_{parse|put}_link(). > Make these functions more generally available by moving them to driver > base, with the appropriate name changes to the functions and struct. > > In the process embed a 'struct fwnode_endpoint' in 'struct fwnode_link' > for both sides of the link, and make use of fwnode_graph_parse_endpoint() > to fully parse both endpoints. Rename members local_node and > remote_node to more descriptive local_port_parent and > remote_port_parent. > May I ask if it's going to be used outside of v4l2? Any user in mind? -- With Best Regards, Andy Shevchenko