From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ian Molton <ian@mnementh.co.uk>,
linux-mmc@vger.kernel.org, linux-sh@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@lists.codethink.co.uk,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Simon Horman <horms@verge.net.au>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: [PATCH v3 2/6] pinctrl: sh-pfc: Implement pinconf power-source param for voltage switching
Date: Mon, 29 Jun 2015 22:55:18 +0100 [thread overview]
Message-ID: <1435614918.23818.23.camel@codethink.co.uk> (raw)
In-Reply-To: <3056637.adr2b5Zij1@avalon>
On Mon, 2015-06-29 at 11:32 +0300, Laurent Pinchart wrote:
> Hi Ben,
>
> Thank you for the patch.
>
> On Friday 26 June 2015 16:23:24 Ben Hutchings wrote:
> > The pfc in the R8A7790 (and probably others in the R-Car gen 2 family)
> > supports switching SDHI signals between 3.3V and 1.8V voltage, and the
> > SD driver should do that when selecting a higher-speed mode.
> >
> > Add a flag for pins that support low voltage mode and SoC operations to
> > get and set it. Implement the pinconf power-source parameter using these
> > operations.
>
> As Geert has already pointed out, we should use an integer value instead of a
> boolean for voltages. How about expressing them in microvolts as done by the
> regulators API ?
I did consider doing that but it seemed like over-engineering. However,
given what Geert said about the other SoCs it seems worth doing.
However, pinconf arguments are limited to 16 bits so I think I will have
to make the units millivolts not microvolts.
[...]
> > diff --git a/drivers/pinctrl/sh-pfc/sh_pfc.h
> > b/drivers/pinctrl/sh-pfc/sh_pfc.h index c7508d5f6886..b95d60bf2f1b 100644
> > --- a/drivers/pinctrl/sh-pfc/sh_pfc.h
> > +++ b/drivers/pinctrl/sh-pfc/sh_pfc.h
> > @@ -13,6 +13,7 @@
> >
> > #include <linux/bug.h>
> > #include <linux/stringify.h>
> > +#include <linux/pinctrl/pinconf-generic.h>
>
> Could you please keep the headers alphabetically sorted ?
>
> >
> > enum {
> > PINMUX_TYPE_NONE,
> > @@ -26,8 +27,11 @@ enum {
> > #define SH_PFC_PIN_CFG_OUTPUT (1 << 1)
> > #define SH_PFC_PIN_CFG_PULL_UP (1 << 2)
> > #define SH_PFC_PIN_CFG_PULL_DOWN (1 << 3)
> > +#define SH_PFC_PIN_CFG_LOW_VOLTAGE (1 << 4)
>
> As we should move away from using a bool to represent the voltage, I would
> name this SH_PFC_PIN_CFG_IO_VOLTAGE, or possibly SH_PFC_PIN_CFG_POWER_SOURCE.
Right.
> > #define SH_PFC_PIN_CFG_NO_GPIO (1 << 31)
> >
> > +struct sh_pfc;
> > +
>
> I don't think this is needed, struct sh_pfc is already forward-declared right
> above struct sh_pfc_soc_operations.
Right, this is left over from the previous version where I added an
operation to struct sh_pfc_pin.
> > struct sh_pfc_pin {
> > u16 pin;
> > u16 enum_id;
> > @@ -121,6 +125,8 @@ struct sh_pfc_soc_operations {
> > unsigned int (*get_bias)(struct sh_pfc *pfc, unsigned int pin);
> > void (*set_bias)(struct sh_pfc *pfc, unsigned int pin,
> > unsigned int bias);
> > + bool (*get_low_voltage)(struct sh_pfc *pfc, unsigned int pin);
> > + void (*set_low_voltage)(struct sh_pfc *pfc, unsigned int pin, bool low);
>
> [gs]et_io_voltage() or [gs]et_power_source() ?
I prefer the former.
Ben.
next prev parent reply other threads:[~2015-06-29 21:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 15:21 [PATCH v3 0/6] UHS-I support for sh_mobile_sdhi Ben Hutchings
2015-06-26 15:22 ` [PATCH v3 1/6] mmc: tmio: Add UHS-I mode support Ben Hutchings
2015-06-26 15:23 ` [PATCH v3 2/6] pinctrl: sh-pfc: Implement pinconf power-source param for voltage switching Ben Hutchings
2015-06-29 8:17 ` Geert Uytterhoeven
2015-06-29 8:32 ` Laurent Pinchart
2015-06-29 21:55 ` Ben Hutchings [this message]
2015-06-26 15:23 ` [PATCH v3 3/6] pinctrl: sh-pfc: r8a7790: Implement voltage switching for SDHI Ben Hutchings
2015-06-29 8:50 ` Laurent Pinchart
2015-06-29 23:44 ` Ben Hutchings
2015-06-26 15:23 ` [PATCH v3 4/6] mmc: sh_mobile_sdhi: Add UHS-I mode support Ben Hutchings
2015-06-26 15:23 ` [PATCH v3 5/6] ARM: shmobile: lager: Set clock rates for SDHI Ben Hutchings
2015-06-29 6:23 ` Kuninori Morimoto
2015-06-30 0:02 ` Ben Hutchings
2015-06-30 1:29 ` Ben Hutchings
2015-06-30 1:31 ` Ben Hutchings
2015-06-30 1:45 ` Kuninori Morimoto
2015-06-30 2:06 ` Ben Hutchings
2015-06-30 4:43 ` Kuninori Morimoto
2015-06-26 15:23 ` [PATCH v3 6/6] ARM: shmobile: lager: Enable UHS-I SDR-50 Ben Hutchings
2015-06-26 15:25 ` [PATCH v3 0/6] UHS-I support for sh_mobile_sdhi Ben Hutchings
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=1435614918.23818.23.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=ian@mnementh.co.uk \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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).