From: Sinan Kaya <okaya@codeaurora.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
linux-acpi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Hanjun Guo <hanjun.guo@linaro.org>,
Tomasz Nowicki <tn@semihalf.com>,
Nate Watterson <nwatters@codeaurora.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH] ACPI/IORT: Fix iort_node_get_id() mapping entries indexing
Date: Thu, 5 Jan 2017 13:37:22 -0500 [thread overview]
Message-ID: <8f8816bf-1a29-ca28-79f3-7bc1b9e9fb5c@codeaurora.org> (raw)
In-Reply-To: <20170105182921.8167-1-lorenzo.pieralisi@arm.com>
On 1/5/2017 1:29 PM, Lorenzo Pieralisi wrote:
> iort_node_get_id() takes an index as input to refer to a specific
> mapping entry in the mapping array to retrieve the id at a specific
> index provided the index is below the total mapping count; currently the
> index is used to retrieve the mapping value from the correct entry but
> not to dereference the correct entry while retrieving the mapping
> output_reference (ie IORT parent pointer), which consequently always
> resolves to the output_reference of the first entry in the mapping
> array.
Maybe, irrelevant but I'm going to throw it out.
Can we somehow break these multiple input and multiple output single
function into smaller and manageable pieces while we are fixing a bug
on it?
These functions seem to do N different things when an input is present
or not.
I got lost in these function when implementing ITS->SMMU->NC use case.
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-01-05 18:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 18:29 Lorenzo Pieralisi
2017-01-05 18:37 ` Sinan Kaya [this message]
2017-01-06 9:48 ` Lorenzo Pieralisi
2017-01-07 21:09 ` Sinan Kaya
2017-01-09 6:34 ` Hanjun Guo
2017-01-09 6:48 ` Hanjun Guo
2017-01-09 11:20 ` okaya
2017-01-09 8:01 ` Hanjun Guo
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=8f8816bf-1a29-ca28-79f3-7bc1b9e9fb5c@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=hanjun.guo@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=nwatters@codeaurora.org \
--cc=rjw@rjwysocki.net \
--cc=tn@semihalf.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
Powered by JetHome