linux-pwm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-sh@vger.kernel.org, linux-pwm@vger.kernel.org,
	Thierry Reding <thierry.reding@gmail.com>,
	Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH v4 0/5] Renesas TPU PWM support
Date: Tue, 25 Jun 2013 08:40:03 +0900	[thread overview]
Message-ID: <20130624233959.GA11275@verge.net.au> (raw)
In-Reply-To: <13724411.JArtzQ6F7y@avalon>

On Fri, Jun 21, 2013 at 08:43:21AM +0200, Laurent Pinchart wrote:
> Hi Simon,
> 
> On Friday 21 June 2013 15:15:28 Simon Horman wrote:
> > On Thu, Jun 20, 2013 at 01:15:11PM +0200, Laurent Pinchart wrote:
> > > On Monday 17 June 2013 12:31:39 Laurent Pinchart wrote:
> > > > On Monday 17 June 2013 13:25:49 Simon Horman wrote:
> > > > > Hi Laurent,
> > > > > 
> > > > > I am having a little trouble testing this.
> > > > > I am wondering if you could guide me as to what .config options I
> > > > > should have enabled and what values I should be looking for in /sys ?
> > > > 
> > > > Sure. You need to enable CONFIG_LEDS_PWM and CONFIG_PWM_RENESAS_TPU).
> > > > You should then be able to control the LEDs through /sys/class/leds/*.
> > > 
> > > Any luck ?
> > 
> > Hi Laurent,
> > 
> > I have confirmed that I can toggle the G H and J LEDs.
> 
> Thank you.
> 
> > Should I queue-up this patchset?
> 
> Given that it's too late to push this to v3.11 through the ARM SoC tree 
> (please correct me if I'm wrong), what about pushing 1/5 through the PWM tree 
> for v3.11 and 2/5 to 5/5 through ARM SoC for v3.12 ? Thierry, would you be 
> able to pick patch 1/5 for v3.11 ?

Yes, it is a bit late for v3.11 for arm-soc - I apologise for
being partly responsible for the lateness.

I am quite happy with your proposal for patches 1/5.

> > On the way I noticed the following:
> > 
> > sh-pfc pfc-sh73a0: pin PORT163 already requested by renesas-tpu-pwm.3;
> > cannot claim for sh-sci.8 sh-pfc pfc-sh73a0: pin-163 (sh-sci.8) status -22
> 
> Pin 163 was used for both TPU LEDs and SCIFB RTS in the original board code, 
> hence the conflict. That's most probably a mistake. Do you have the kota2 
> schematics ? If so, could you please confirm that pin 163 is used for the LED 
> only, not for SCIFB RTS ? I'll then send a patch to fix this.

I do not have the kota2 schematics.

> > sh-pfc pfc-sh73a0: pin 1195 is not registered so it cannot be requested
> > sh-pfc pfc-sh73a0: pin-1195 (sh_keysc.0) status -22
> > sh-pfc pfc-sh73a0: could not request pin 1195 on device sh-pfc
> > sh_keysc sh_keysc.0: Error applying setting, reverse things back
> 
> I'll work on that.
> 
> > My personal feeling is that if these are trivial to fix then it would be
> > worth doing so. Otherwise a discussion needs to be had about support for the
> > kota2.
> 
> -- 
> Regards,
> 
> Laurent Pinchart
> 

      parent reply	other threads:[~2013-06-24 23:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13 16:54 [PATCH v4 0/5] Renesas TPU PWM support Laurent Pinchart
2013-06-13 16:54 ` [PATCH v4 1/5] pwm: Add Renesas TPU PWM driver Laurent Pinchart
2013-06-13 18:31   ` Thierry Reding
2013-06-21  9:31   ` Thierry Reding
2013-06-21 12:20     ` Laurent Pinchart
2013-06-13 16:54 ` [PATCH v4 2/5] ARM: mach-shmobile: armadillo800eva: Add backlight support Laurent Pinchart
2013-06-13 16:54 ` [PATCH v4 3/5] ARM: mach-shmobile: kota2: Use leds-pwm + pwm-rmob Laurent Pinchart
2013-06-13 16:54 ` [PATCH v4 4/5] ARM: shmobile: sh73a0: Remove all GPIOs Laurent Pinchart
2013-06-13 16:54 ` [PATCH v4 5/5] leds: Remove leds-renesas-tpu driver Laurent Pinchart
2013-06-13 21:36 ` [PATCH v4 0/5] Renesas TPU PWM support Laurent Pinchart
2013-06-14  1:01   ` Simon Horman
2013-06-17  4:25     ` Simon Horman
2013-06-17 10:31       ` Laurent Pinchart
2013-06-20 11:15         ` Laurent Pinchart
2013-06-20 13:21           ` Simon Horman
2013-06-21  6:15           ` Simon Horman
2013-06-21  6:43             ` Laurent Pinchart
2013-06-21  9:30               ` Thierry Reding
2013-06-24 23:40               ` Simon Horman [this message]

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=20130624233959.GA11275@verge.net.au \
    --to=horms@verge.net.au \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-pwm@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=thierry.reding@gmail.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).