linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Figa <tfiga@chromium.org>
To: Vivek Gautam <vivek.gautam@codeaurora.org>
Cc: Joerg Roedel <joro@8bytes.org>, Rob Herring <robh+dt@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	"open list:IOMMU DRIVERS" <iommu@lists.linux-foundation.org>,
	devicetree@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Rob Clark <robdclark@gmail.com>,
	Sricharan R <sricharan@codeaurora.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Archit Taneja <architt@codeaurora.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v9 1/5] driver core: Find an existing link between two devices
Date: Tue, 13 Mar 2018 19:15:08 +0900	[thread overview]
Message-ID: <CAAFQd5DXvnjaFw4Ct1Xn90nQZ4F4dLtov0ymG-tycQt5oLNpiQ@mail.gmail.com> (raw)
In-Reply-To: <20180313085534.11650-2-vivek.gautam@codeaurora.org>

Hi Vivek,

Thanks for the patch.

On Tue, Mar 13, 2018 at 5:55 PM, Vivek Gautam
<vivek.gautam@codeaurora.org> wrote:
> The lists managing the device-links can be traversed to
> find the link between two devices. The device_link_add() APIs
> does traverse these lists to check if there's already a link
> setup between the two devices.
> So, add a new APIs, device_link_find(), to find an existing
> device link between two devices - suppliers and consumers.

I'm wondering if this API would be useful for anything else that the
problem we're trying to solve with deleting links without storing them
anywhere. Perhaps a device_link_del_dev(consumer, supplier) would be a
better alternative?

Best regards,
Tomasz

  parent reply	other threads:[~2018-03-13 10:15 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-13  8:55 [PATCH v9 0/5] iommu/arm-smmu: Add runtime pm/sleep support Vivek Gautam
2018-03-13  8:55 ` [PATCH v9 1/5] driver core: Find an existing link between two devices Vivek Gautam
2018-03-13  9:40   ` Rafael J. Wysocki
2018-03-13  9:55     ` Vivek Gautam
2018-03-13 12:49       ` Robin Murphy
2018-03-13 14:39         ` Vivek Gautam
2018-03-13  9:58   ` Vivek Gautam
2018-03-13 10:15   ` Tomasz Figa [this message]
2018-03-13 10:34     ` Vivek Gautam
2018-03-13 11:23       ` Tomasz Figa
2018-03-14 11:12         ` Rafael J. Wysocki
2018-03-14 11:50           ` Tomasz Figa
2018-03-14 11:57             ` Rafael J. Wysocki
2018-03-14 12:14               ` Robin Murphy
2018-03-14 12:27                 ` Lukas Wunner
2018-03-20  7:56                   ` Vivek Gautam
2018-03-14 12:23           ` Lukas Wunner
2018-03-13  8:55 ` [PATCH v9 2/5] iommu/arm-smmu: Add pm_runtime/sleep ops Vivek Gautam
2018-03-13  8:55 ` [PATCH v9 3/5] iommu/arm-smmu: Invoke pm_runtime during probe, add/remove device Vivek Gautam
2018-03-14 17:46   ` Robin Murphy
2018-03-15  7:17     ` Tomasz Figa
2018-03-20  9:49     ` Vivek Gautam
2018-03-13  8:55 ` [PATCH v9 4/5] iommu/arm-smmu: Add the device_link between masters and smmu Vivek Gautam
2018-03-14 17:50   ` Robin Murphy
2018-03-15  6:18     ` Tomasz Figa
2018-03-15 10:44       ` Robin Murphy
2018-03-15  8:57     ` Vivek Gautam
2018-03-15 11:12       ` Robin Murphy
2018-03-13  8:55 ` [PATCH v9 5/5] iommu/arm-smmu: Add support for qcom,smmu-v2 variant Vivek Gautam
     [not found]   ` <61d30fff-1bf8-d2c1-bbe9-f93de836ae77@huawei.com>
     [not found]     ` <7d5af071-ef98-8461-3ce9-e84fc0b3956a@codeaurora.org>
2018-03-28  6:11       ` Yisheng Xie
2018-04-10 13:14         ` Tomasz Figa
2018-04-11  1:22           ` Yisheng Xie
2018-04-11  5:15             ` Vivek Gautam
2018-04-12  1:55               ` Yisheng Xie

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=CAAFQd5DXvnjaFw4Ct1Xn90nQZ4F4dLtov0ymG-tycQt5oLNpiQ@mail.gmail.com \
    --to=tfiga@chromium.org \
    --cc=architt@codeaurora.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mark.rutland@arm.com \
    --cc=rjw@rjwysocki.net \
    --cc=robdclark@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=sricharan@codeaurora.org \
    --cc=vivek.gautam@codeaurora.org \
    --cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).