All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ashwin Chaugule <ashwin.chaugule@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "rwells@codeaurora.org" <rwells@codeaurora.org>,
	Linda Knippers <linda.knippers@hp.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Catalin Marinas <Catalin.Marinas@arm.com>,
	Patch Tracking <patches@linaro.org>,
	Linaro ACPI Mailman List <linaro-acpi@lists.linaro.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Jaswinder Singh <jaswinder.singh@linaro.org>,
	Mark Brown <broonie@kernel.org>,
	Arnd Bergmann <arnd.bergmann@linaro.org>
Subject: Re: [PATCH v4 1/2] Mailbox: Restructure and simplify PCC mailbox code
Date: Thu, 19 Mar 2015 19:11:42 -0400	[thread overview]
Message-ID: <CAJ5Y-eZaQP0GRzfZQC8o4BaF34UWCTFCAKNaYMb=nUJmFq7Tew@mail.gmail.com> (raw)
In-Reply-To: <1993436.YrcLMSCsYF@vostro.rjw.lan>

On 12 March 2015 at 19:28, Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
> On Friday, February 13, 2015 07:01:30 PM Ashwin Chaugule wrote:
>> On 13 February 2015 at 18:31, Ashwin Chaugule
>> <ashwin.chaugule@linaro.org> wrote:
>> > Hi Rafael,
>> >
>> > On 13 February 2015 at 09:38, Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
>> >> On Friday, February 13, 2015 08:07:44 AM Ashwin Chaugule wrote:
>> >>> Hello,
>> >>>
>> >>> On 27 January 2015 at 16:03, Ashwin Chaugule <ashwin.chaugule@linaro.org> wrote:
>> >>> > Previously the PCC driver depended on the client
>> >>> > side to map the communication space base address. This region
>> >>> > was was then used in the PCC driver and the client side.
>> >>> > The client side used this region to read and write its data
>> >>> > and the PCC driver used it to only write the PCC command.
>> >>> > Removing this split simplifies the PCC driver a lot. This patch
>> >>> > moves all communication region read/writes to the client side.
>> >>> > The PCC clients can now drive the PCC mailbox controller via the
>> >>> > mbox_client_txdone() method.
>> >>> >
>> >>> > Signed-off-by: Ashwin Chaugule <ashwin.chaugule@linaro.org>
>> >>> > ---
>> >>> >  drivers/mailbox/pcc.c | 122 +++++++++++++++-----------------------------------
>> >>> >  1 file changed, 37 insertions(+), 85 deletions(-)
>> >>>
>> >>> Gentle reminder for this patch specifically. It can be pulled in by
>> >>> itself separately from the CPPC patch[2/2], which understandably may
>> >>> need more time for review. Apart from the simplification done here,
>> >>> there is one more change based on a comment I got from Rafael tow
>> >>> convert a pr_err() in the init function to pr_debug(). The "PCC Probe
>> >>> failed" message seems to be raising false positives on X86 test
>> >>> reports. Please let me know if there are any other suggestions, before
>> >>> I respin another version for this.
>> >>
>> >> The patch changing the pr_err() to pr_debug() is in the Linus' tree already
>> >> as far as I can say.
>> >
>> > Thanks for that.
>> >
>> >>
>> >> Besides, this should be To: the maintainer of the mailbox susbsystem (not
>> >> me) or if you want me to pick it up, I need and ACK from that maintainer
>> >> anyway.
>> >
>> > Is there a way to do that separately for each patch in a patchset?
>> > Anyway, I'll rebase this patch to tip and send it separately To:
>> > Jassi.
>>
>> Rebasing to tip and applying this patch didnt cause any merge
>> conflicts. So I think instead of generating more patch traffic just
>> yet, its probably better to review this as is. Let me know if anyone
>> thinks otherwise. I'll try to ping Jassi offline.
>
> Can you please remind me what the status here is?  Is this the final version
> I'm supposed to review or are you going to submit a new one?

As a heads up, Jassi had already picked up this patch in his tree:

https://git.linaro.org/landing-teams/working/fujitsu/integration.git/shortlog/refs/heads/mailbox-devel

Thanks,
Ashwin.

  parent reply	other threads:[~2015-03-19 23:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27 21:03 [PATCH v4 0/2] CPUFreq driver using CPPC methods Ashwin Chaugule
2015-01-27 21:03 ` [PATCH v4 1/2] Mailbox: Restructure and simplify PCC mailbox code Ashwin Chaugule
2015-02-13 13:07   ` Ashwin Chaugule
2015-02-13 14:38     ` Rafael J. Wysocki
2015-02-13 23:31       ` Ashwin Chaugule
2015-02-14  0:01         ` Ashwin Chaugule
2015-03-12 23:28           ` Rafael J. Wysocki
2015-03-13  1:34             ` Ashwin Chaugule
2015-03-19 23:11             ` Ashwin Chaugule [this message]
2015-01-27 21:03 ` [PATCH v4 2/2] CPPC: Add CPUFreq driver based on CPPC methods Ashwin Chaugule
2015-02-03 22:33   ` Rafael J. Wysocki
2015-02-04  3:23     ` Ashwin Chaugule
2015-02-04 14:33       ` Rafael J. Wysocki
2015-02-04 15:18         ` Ashwin Chaugule
2015-04-01 15:38           ` Ashwin Chaugule
2015-05-08 22:30   ` Rafael J. Wysocki
2015-05-11 17:35     ` Ashwin Chaugule

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='CAJ5Y-eZaQP0GRzfZQC8o4BaF34UWCTFCAKNaYMb=nUJmFq7Tew@mail.gmail.com' \
    --to=ashwin.chaugule@linaro.org \
    --cc=Catalin.Marinas@arm.com \
    --cc=arnd.bergmann@linaro.org \
    --cc=broonie@kernel.org \
    --cc=jaswinder.singh@linaro.org \
    --cc=linaro-acpi@lists.linaro.org \
    --cc=linda.knippers@hp.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=patches@linaro.org \
    --cc=rjw@rjwysocki.net \
    --cc=rwells@codeaurora.org \
    --cc=viresh.kumar@linaro.org \
    /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.