linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Hoan Tran <hotran@apm.com>
Cc: Jassi Brar <jassisinghbrar@gmail.com>,
	Ashwin Chaugule <ashwin.chaugule@linaro.org>,
	Robert Moore <robert.moore@intel.com>,
	Alexey Klimov <alexey.klimov@arm.com>,
	lkml <linux-kernel@vger.kernel.org>,
	linux acpi <linux-acpi@vger.kernel.org>, Loc Ho <lho@apm.com>,
	Duc Dang <dhdang@apm.com>,
	"Prakash, Prashanth" <pprakash@codeaurora.org>
Subject: Re: [PATCH v3] mailbox: pcc: Support HW-Reduced Communication Subspace type 2
Date: Mon, 27 Jun 2016 23:32 +0200	[thread overview]
Message-ID: <4302600.LGpaGycv0T@vostro.rjw.lan> (raw)
In-Reply-To: <CAFHUOYzpeSw-6Tvj=ffwX7L+jgMDTd_2mVm5nOuormw7hmq9OA@mail.gmail.com>

On Monday, June 27, 2016 11:27:42 AM Hoan Tran wrote:
> Hi Jassi and Rafael,
> 
> On Wed, Jun 15, 2016 at 9:19 AM, Prakash, Prashanth
> <pprakash@codeaurora.org> wrote:
> >
> >
> > On 6/9/2016 4:43 PM, Hoan Tran wrote:
> >> Hi Prashanth,
> >>
> >> On Thu, Jun 9, 2016 at 3:25 PM, Prakash, Prashanth
> >> <pprakash@codeaurora.org> wrote:
> >>>
> >>> On 6/9/2016 2:47 PM, Hoan Tran wrote:
> >>>> Hi Ashwin and Prashanth,
> >>>>
> >>>> On Wed, Jun 8, 2016 at 5:41 PM, Hoan Tran <hotran@apm.com> wrote:
> >>>>> Hi Prashanth,
> >>>>>
> >>>>>
> >>>>> On Wed, Jun 8, 2016 at 5:32 PM, Prakash, Prashanth
> >>>>> <pprakash@codeaurora.org> wrote:
> >>>>>> On 6/8/2016 10:24 AM, Hoan Tran wrote:
> >>>>>>> Hi Ashwin,
> >>>>>>>
> >>>>>>> On Wed, Jun 8, 2016 at 5:18 AM, Ashwin Chaugule
> >>>>>>> <ashwin.chaugule@linaro.org> wrote:
> >>>>>>>> + Prashanth (Can you please have a look as well?)
> >>>>>>>>
> >>>>>>>> On 31 May 2016 at 15:35, Hoan Tran <hotran@apm.com> wrote:
> >>>>>>>>> Hi Ashwin,
> >>>>>>>> Hi,
> >>>>>>>>
> >>>>>>>> Sorry about the delay. I'm in the middle of switching jobs and
> >>>>>>>> locations, so its been a bit crazy lately.
> >>>>>>> It's ok and hope you're doing well.
> >>>>>>>
> >>>>>>>> I dont have any major
> >>>>>>>> concerns with this code, although there could be subtle issues with
> >>>>>>>> this IRQ thing. In this patchset, your intent is to add support for
> >>>>>>>> PCC subspace type 2. But you're also adding support for tx command
> >>>>>>>> completion which is not specific to Type 2. We could support that even
> >>>>>>>> in Type 1. Hence I wanted to separate the two, not just for review,
> >>>>>>>> but also the async IRQ completion has subtle issues esp. in the case
> >>>>>>>> of async platform notification, where you could have a PCC client in
> >>>>>>>> the OS writing to the cmd bit and the platform sending an async
> >>>>>>>> notification by writing to some bits in the same 8byte address as the
> >>>>>>>> cmd bit. So we need some mutual exclusivity there, otherwise the OS
> >>>>>>>> and platform could step on each other. Perhaps Prashanth has better
> >>>>>>>> insight into this.
> >>>>>>> I think, this mutual exclusivity could be in another patch.
> >>>>>> Ashwin,
> >>>>>> Sorry, I am not sure how we can prevent platform and OSPM from stepping on
> >>>>>> each other.  There is a line is spec that says "all operations on status field
> >>>>>> must be made using interlocked operations", but not sure what these
> >>>>>> interlocked operation translates to.
> >>>>> Yes, I had the same question about how to prevent it.
> >>>> For platform notification, if the hardware doesn't support interlocked
> >>>> operations. I think we can use a workaround that, platform triggers
> >>>> interrupt to OSPM without touching status field. The OSPM PCC client
> >>>> will decide what to do with this interrupt. For example, OSPM sends a
> >>>> consumer command to check it.
> >>> How do we decide which platform can support this interlocked operation?
> >>> and how do we decide between a completion notification and platform
> >>> notification?
> >> Truly, we should follow the specification. But I don't know if there's
> >> any hardware support this interlocked operation.
> >> For the decide between a completion notification and platform notification
> >>  - Completion notification: Bit "Command Complete" is set.
> >>  - Platform notification: Bit "Command Complete" is not set.
> >>
> >>> I think the ACPI spec on platform notification is quite ambiguous and it is
> >>> best to get the necessary clarification and/or correction before implementing
> >>> anything related to platform notification.
> >> Agreed, a clarification inside ACPI Specification is needed
> > This patch look good to me, as it doesn't deal with platform notification.
> > We can try to get some clarification from spec side before handling the platform
> > notification pieces.
> >
> > Reviewed-by: Prashanth Prakash <pprakash@codeaurora.org>
> 
> Do you have plan to apply this patch ?

Yes.

Thanks,
Rafael

  reply	other threads:[~2016-06-27 21:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-20  0:32 [PATCH v3] mailbox: pcc: Support HW-Reduced Communication Subspace type 2 Hoan Tran
2016-05-31 16:32 ` Hoan Tran
2016-05-31 19:05 ` Ashwin Chaugule
2016-05-31 19:35   ` Hoan Tran
2016-06-08 12:18     ` Ashwin Chaugule
2016-06-08 16:24       ` Hoan Tran
2016-06-09  0:32         ` Prakash, Prashanth
2016-06-09  0:41           ` Hoan Tran
2016-06-09 20:47             ` Hoan Tran
2016-06-09 22:25               ` Prakash, Prashanth
2016-06-09 22:43                 ` Hoan Tran
2016-06-15 16:19                   ` Prakash, Prashanth
2016-06-27 18:27                     ` Hoan Tran
2016-06-27 21:32                       ` Rafael J. Wysocki [this message]
2016-07-13 22:00                         ` Hoan Tran
2016-08-15 16:45                         ` Hoan Tran
2016-08-15 23:18                           ` Rafael J. Wysocki
2016-08-15 23:41                             ` Hoan Tran
2016-08-16 11:56                               ` Rafael J. Wysocki
2016-08-16 16:27                                 ` Hoan Tran

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=4302600.LGpaGycv0T@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=alexey.klimov@arm.com \
    --cc=ashwin.chaugule@linaro.org \
    --cc=dhdang@apm.com \
    --cc=hotran@apm.com \
    --cc=jassisinghbrar@gmail.com \
    --cc=lho@apm.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pprakash@codeaurora.org \
    --cc=robert.moore@intel.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).