This patch adds extcon support to see VBUS/ID signal states.
Signed-off-by: Yoshihiro Shimoda
---
drivers/usb/gadget/udc/Kconfig| 1 +
drivers/usb/gadget/udc/renesas_usb3.c | 43 +--
2 files changed, 42 insertions(+), 2
This patch adds support for usb role swap via sysfs "role".
For example:
1) Connect a usb cable using 2 Salvator-X boards.
- For A-Device, the cable is connected to CN11 (USB3.0 ch0).
- For B-Device, the cable is connected to CN9 (USB2.0 ch0).
2) On A-Device, you input the following
This usb 3.0 peripheral controller has a register (USB_OTG_STA) to monitor
the USB ID signal. So, this patch adds the ID signal monitoring to change
the mode to host (A-Host) or peripheral (B-Peripheral).
This patch also removes hardcoded setting as B-Peripheral mode.
Signed-off-by: Yoshihiro
This patch set is based on the latest Felipe's usb.bit / testing/next branch
(commit id = 29986993f67341493988b6c5d68e0653061975b2).
The USB3.0 DRD controller on R-Car Gen3 can change the role via DRD_CON
register in the periperal side sadly, so this patch adds support
for usb role swap feature
From: Kuninori Morimoto
Current adg is calling of_clk_add_povider() multiple times,
but it is not correct usage. This patch fixup its parameter
and call it once.
Signed-off-by: Kuninori Morimoto
---
sound/soc/sh/rcar/adg.c |
Hi Mark
These are bugfix for Renesas R-Car sound clock.
The issue will happen if I do bind/unbind many times.
Kuninori Morimoto (2):
ASoC: rcar: fixup of_clk_add_provider() usage for multi clkout
ASoC: rcar: call missing of_clk_del_provider() when remove
sound/soc/sh/rcar/adg.c | 19
Hi
Sorry for my noise.
I could solve my issue.
> Now, I'm using devm_get_clk_from_child() (= linux/drivers/clk/clk-devres.c)
> and I got Oops if I do bind/unbind driver several times.
>
> [ 32.008847] Unable to handle kernel paging request at virtual
> address d503201faa1e03e0
>
Hi Geert-san,
> From: Geert Uytterhoeven, Sent: Wednesday, March 29, 2017 9:23 PM
>
> Hi Shimoda-san,
>
> On Wed, Mar 29, 2017 at 1:42 PM, Yoshihiro Shimoda
> wrote:
> > --- a/drivers/usb/gadget/udc/renesas_usb3.c
> > +++
On Wed, Mar 29, 2017 at 9:38 PM, Geert Uytterhoeven
wrote:
> Hi Arnd, Greg, Kevin, Magnus, Olof, Simon,
>
> This patch series contains two improvements for the SoC bus and
> soc_device_match(). The second one is a dependency for handling
> different SoC revisions
On Wed, Mar 29, 2017 at 08:43:49PM +0200, Niklas Söderlund wrote:
> Hi,
>
> This series adds support for hardware backed trip point windows. It is
> based on top of v4.11-rc1 and is tested on R-Car H3 and M3-W.
>
> The series starts out by fixing three issues (1/7, 2/7, 3/7) that should
> have
If soc_device_match() is called before the SoC bus has been registered,
bus_for_each_dev() returns -EINVAL, which is considered a match, as it
is non-zero.
While calling soc_device_match() too early can be considered an
integration mistake, returning a match is counter-intuitive:
Hi Arnd, Greg, Kevin, Magnus, Olof, Simon,
This patch series contains two improvements for the SoC bus and
soc_device_match(). The second one is a dependency for handling
different SoC revisions in the Renesas R-Car SYSC driver, which manages
PM Domains and thus needs to be initialized
Enable hardware trip points by implementing the set_trips callback. The
thermal core will take care of setting the initial trip point window and
to update it once the driver reports a TSC has moved outside it.
The interrupt structure for this device is a bit odd. There is not a
dedicated IRQ for
The .thermal_init needs to be delayed a short amount of time to allow
for the TEMP register to contain something useful. If it's not delayed
these warnings are common during boot:
thermal thermal_zone0: failed to read out thermal zone (-5)
thermal thermal_zone1: failed to read out thermal zone
Hi,
This series adds support for hardware backed trip point windows. It is
based on top of v4.11-rc1 and is tested on R-Car H3 and M3-W.
The series starts out by fixing three issues (1/7, 2/7, 3/7) that should
have been fixed by me before the initial driver where submitted to
upstream. Sorry for
There is no point in protecting a register read with a lock. This is
most likely a leftover from when the driver was reworked before being
submitted for upstream.
Signed-off-by: Niklas Söderlund
Reviewed-by: Geert Uytterhoeven
To restore operation it's easiest to reinitialise all TSCs. In order to
do this the current trip window needs to be stored in the TSC structure
so that it can be restored upon resume.
Signed-off-by: Niklas Söderlund
Reviewed-by: Wolfram Sang
Move the check for a TSC resource before allocating memory for a new
TSC. If no TSC is found there is little point in allocating memory for
it.
Signed-off-by: Niklas Söderlund
Reviewed-by: Geert Uytterhoeven
Reviewed-by: Wolfram
Record how many TSCs are found in struct rcar_gen3_thermal_priv, this is
needed to be able to add hardware interrupts for trip points later. Also
add a check to make sure at least one TSC is found.
Signed-off-by: Niklas Söderlund
Reviewed-by: Geert
Hello!
Ignore the postings of the single fix, I meant to post 2 patch series but
stupidly erred in the command line. :-<
MBR, Sergei
The R8A7791 PFC driver was apparently based on the preliminary revisions
of the user's manual, which omitted the DVC_MUTE signal altogether in
the PFC section. The modern manual has the signal described, so just add
the necassary data to the driver...
Fixes: 508845196238 ("pinctrl: sh-pfc:
The R8A7791 PFC driver was apparently based on the preliminary revisions
of the user's manual, which omitted the HSCIF1 group E signals in the
IPSR4 register description. This would cause HSCIF1's probe to fail with
the messages like below:
sh-pfc e606.pfc: cannot locate data/mark
Hello!
Here's a set of 2 patches against the 'fixes' branch of Linus Walleij's
'linux-pinctrl.git'. The patches add support for (1) the HSCIF1 configured to
use signal group E (which is currently broken) and for (2) the DVC_MUTE signal.
[1/2] pinctrl: sh-pfc: r8a7791: add missing HSCIF1
The R8A7791 PFC driver was apparently based on the preliminary revisions
of the user's manual, which omitted the HSCIF1 group E signals in the
IPSR4 register description. This would cause HSCIF1's probe to fail with
the messages like below:
sh-pfc e606.pfc: cannot locate data/mark
Hello!
Here's a set of 2 patches against the 'fixes' branch of Linus Walleij's
'linux-pinctrl.git'. The patches add support for (1) the HSCIF1 configured to
use signal group E (which is currently broken) and for (2) the DVC_MUTE signal.
[1/2] pinctrl: sh-pfc: r8a7791: add missing HSCIF1
The R8A7791 PFC driver was apparently based on the preliminary revisions
of the user's manual, which omitted the HSCIF1 group E signals in the
IPSR4 register description. This would cause HSCIF1's probe to fail with
the messages like below:
sh-pfc e606.pfc: cannot locate data/mark
Hello!
Here's a set of 2 patches against the 'fixes' branch of Linus Walleij's
'linux-pinctrl.git'. The patches add support for (1) the HSCIF1 configured to
use signal group E (which is currently broken) and for (2) the DVC_MUTE signal.
[1/2] pinctrl: sh-pfc: r8a7791: add missing HSCIF1
Enable the 32.768 kHz RTC_X1 clock by setting the frequency value to
non-zero.
Signed-off-by: Chris Brandt
---
arch/arm/boot/dts/r7s72100-rskrza1.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/r7s72100-rskrza1.dts
Basically, the same RTC that was used in SuperH devices is now used in
RZ/A1 devices. Therefore with some slight changes, that driver can be
reused.
Additionally, since ARM architectures require Device Tree configurations,
device tree support has been added.
This was tested on RZ/A1H RSK board.
Add the binding documentation for rtc-sh which is an RTC for
SuperH and RZ/A SoCs.
Signed-off-by: Chris Brandt
---
v3:
* remove 'power-domains' from example
* update commit message subject and body
v2:
* added interrupt-names and clock-names
* clocks now include
Add the RTC clocks to device tree. The frequencies must be fixed values
according to the hardware manual.
Signed-off-by: Chris Brandt
---
arch/arm/boot/dts/r7s72100.dtsi | 14 ++
1 file changed, 14 insertions(+)
diff --git a/arch/arm/boot/dts/r7s72100.dtsi
Add the realtime clock device node.
Signed-off-by: Chris Brandt
Reviewed-by: Geert Uytterhoeven
---
v2:
* added interrupt-names
* added clock counting sources
* added clock-names "fck", "rtc_x1", "rtc_x3", "extal"
---
Add the realtime clock functional clock source.
Signed-off-by: Chris Brandt
Reviewed-by: Geert Uytterhoeven
---
v2:
* changed "rtc0" to "rtc"
* added Reviewed-by
---
arch/arm/boot/dts/r7s72100.dtsi| 9 +
Enable the realtime clock.
Signed-off-by: Chris Brandt
---
arch/arm/boot/dts/r7s72100-rskrza1.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/r7s72100-rskrza1.dts
b/arch/arm/boot/dts/r7s72100-rskrza1.dts
index cab5857bfb41..72df20a04320
This same RTC is used in RZ/A series MPUs, therefore with some slight
changes, this driver can be reused. Additionally, since ARM architectures
require Device Tree configurations, device tree support has been added.
Signed-off-by: Chris Brandt
Reviewed-by: Geert
Hi Linus,
another reply to your email, please don't feel assaulted :)
On Wed, Mar 29, 2017 at 03:22:23PM +0200, Linus Walleij wrote:
> On Fri, Mar 24, 2017 at 4:22 PM, Jacopo Mondi
> wrote:
>
> > Add dt-bindings for Renesas r7s72100 pin controller header file.
>
On Wednesday, March 29, 2017, Chris Brandt wrote:
> On Wednesday, March 29, 2017, Geert Uytterhoeven wrote:
> > > But, what do we do for Ethernet? All the pins are "normal" except
> > > just the MDIO pin needs to be bidirectional.
> > > That's the part I'm confused by.
> > > How do we flag that
Hi Geert,
On Wednesday, March 29, 2017, Geert Uytterhoeven wrote:
> > But, what do we do for Ethernet? All the pins are "normal" except just
> > the MDIO pin needs to be bidirectional.
> > That's the part I'm confused by.
> > How do we flag that just the ET_MDIO needs "bidirectional"?
>
> You
Hi Chris,
On Wed, Mar 29, 2017 at 4:55 PM, Chris Brandt wrote:
> On Wednesday, March 29, 2017, Linus Walleij wrote:
>> On Fri, Mar 24, 2017 at 4:22 PM, Jacopo Mondi
>> wrote:
>> > +/*
>> > + * Flags used to ask software to drive the pin I/O
On Wednesday, March 29, 2017, Linus Walleij wrote:
> On Fri, Mar 24, 2017 at 4:22 PM, Jacopo Mondi
> wrote:
>
> > Add dt-bindings for Renesas r7s72100 pin controller header file.
> >
> > Signed-off-by: Jacopo Mondi
>
> > +/*
> > + * Pin is
On Wednesday, March 29, 2017, Linus Walleij:
> If you prefer to use preprocessor macros or whatever to make the bitmasks
> or how you want to organize the constants in your include files is not my
> concern, do whatever you seem fit, just pack it into a 32bit thing somehow
> which makes sense from
On Wednesday, March 29, 2017, Geert Uytterhoeven wrote:
> >> +Example:
> >> +rtc: rtc@fcff1000 {
> >> + compatible = "renesas,r7s72100-rtc", "renesas,sh-rtc";
> >> + reg = <0xfcff1000 0x2e>;
> >> + interrupts = >> + GIC_SPI 277 IRQ_TYPE_EDGE_RISING
> >> +
Hi Geert,
On 2017-03-29 14:31:33 +0200, Geert Uytterhoeven wrote:
> Hi Niklas,
>
> On Wed, Mar 29, 2017 at 12:40 AM, Niklas Söderlund
> wrote:
> > This fixes a race condition where the channel resources could be freed
> > before the ISR had finished
Hi Chris,
On Mon, Mar 27, 2017 at 05:12:04PM +, Chris Brandt wrote:
> Hi Jacopo,
>
>
> On Friday, March 24, 2017, Jacopo Mondi
> > + pinctrl: pinctrl@fcfe3000 {
> > + compatible = "renesas,r7s72100-ports";
> > +
> > + #pinctrl-cells = <1>;
> > +
> > + reg =
On Fri, Mar 24, 2017 at 4:22 PM, Jacopo Mondi wrote:
> Add dt-bindings for Renesas r7s72100 pin controller header file.
>
> Signed-off-by: Jacopo Mondi
> +/*
> + * Pin is bi-directional.
> + * An alternate function that needs both
On Wed, Mar 29, 2017 at 2:38 PM, Chris Brandt wrote:
>> I'm strongly in favour of something like
>> pinmux = , ;
>>
>> opposed to
>> pinmux = , ... ;
>
>
> I agree. I like "".
I
On Wed, Mar 29, 2017 at 1:20 PM, Geert Uytterhoeven
wrote:
>> I do not understand the notion of "flags" here. I hope that is not referring
>
> Flags refers to BI_DIR, SWIO_IN, and SWIO_OUT, from
> https://patchwork.kernel.org/patch/9643047/
Aha I will go in and review that
Adding my 2 cents here:
On Wednesday, March 29, 2017, jacopo wrote:
> > > If you really do we may need to go for u64 but ... really? Is there
> > > a rational reason for that other than "we did it like this first"?
> > >
> > > I do not understand the notion of "flags" here. I hope that is not
> >
Hi Niklas,
On Wed, Mar 29, 2017 at 12:40 AM, Niklas Söderlund
wrote:
> This fixes a race condition where the channel resources could be freed
> before the ISR had finished running resulting in a NULL pointer
> reference from the ISR.
>
> [ 167.148934]
Hi Shimoda-san,
On Wed, Mar 29, 2017 at 1:42 PM, Yoshihiro Shimoda
wrote:
> --- a/drivers/usb/gadget/udc/renesas_usb3.c
> +++ b/drivers/usb/gadget/udc/renesas_usb3.c
> @@ -568,12 +573,29 @@ static void usb3_mode_a_host(struct renesas_usb3 *usb3)
>
Hi Geert, Linus
On Wed, Mar 29, 2017 at 01:20:39PM +0200, Geert Uytterhoeven wrote:
> Hi Linus,
>
> On Wed, Mar 29, 2017 at 12:15 PM, Linus Walleij
> wrote:
> > On Wed, Mar 29, 2017 at 9:35 AM, Geert Uytterhoeven
> > wrote:
> >>> See for example:
This patch adds support for usb role swap via sysfs "role".
For example:
1) Connect a usb cable using 2 Salvator-X boards.
- For A-Device, the cable is connected to CN11 (USB3.0 ch0).
- For B-Device, the cable is connected to CN9 (USB2.0 ch0).
2) On A-Device, you input the following
This patch adds extcon support to see VBUS/ID signal states.
Signed-off-by: Yoshihiro Shimoda
---
drivers/usb/gadget/udc/Kconfig| 1 +
drivers/usb/gadget/udc/renesas_usb3.c | 43 +--
2 files changed, 42 insertions(+), 2
This usb 3.0 peripheral controller has a register (USB_OTG_STA) to monitor
the USB ID signal. So, this patch adds the ID signal monitoring to change
the mode to host (A-Device) or peripheral (B-Device).
Signed-off-by: Yoshihiro Shimoda
---
This patch set is based on the latest Felipe's usb.bit / testing/next branch
(commit id = 29986993f67341493988b6c5d68e0653061975b2).
The USB3.0 DRD controller on R-Car Gen3 can change the role via DRD_CON
register in the periperal side sadly, so this patch adds support
for usb role swap feature
Hi Linus,
On Wed, Mar 29, 2017 at 12:15 PM, Linus Walleij
wrote:
> On Wed, Mar 29, 2017 at 9:35 AM, Geert Uytterhoeven
> wrote:
>>> See for example:
>>> include/dt-bindings/pinctrl/mt65xx.h
>>>
>>> And how that is used in:
>>>
The patch
ASoC: rcar: remove rsnd_kctrl_remove()
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus
On Wed, Mar 29, 2017 at 9:35 AM, Geert Uytterhoeven
wrote:
> Me:
>> See for example:
>> include/dt-bindings/pinctrl/mt65xx.h
>>
>> And how that is used in:
>> arch/arm/boot/dts/mt2701-pinfunc.h
>> arch/arm/boot/dts/mt2701-evb.dts
>>
>> The docs are here:
>>
On Wed, Mar 29, 2017 at 9:30 AM, Geert Uytterhoeven
wrote:
> On Fri, Mar 24, 2017 at 4:42 PM, Linus Walleij
> wrote:
>> On Fri, Mar 24, 2017 at 4:22 PM, Jacopo Mondi
>> wrote:
>>
>> I assume Geert will queue this
Hi Geert
> > Current ALSA SoC Sound Card basically consists of CPU/Codec/Platform
> > drivers. If system uses Kernel modules, we can disable these drivers
> > by using rmmod command. In such case, we can't disable
> > CPU/Codec/Platform driver without disabling Sound Card driver.
> >
> > But on
On Wed, Mar 29, 2017 at 10:31:02AM +0200, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Wed, Mar 29, 2017 at 10:13 AM, Simon Horman wrote:
> > On Mon, Mar 27, 2017 at 11:48:12AM +0300, Laurent Pinchart wrote:
> >> On Friday 24 Mar 2017 14:37:44 Geert Uytterhoeven wrote:
> >> >
Hi Felipe-san,
> From: Felipe Balbi, Sent: Wednesday, March 29, 2017 5:03 PM
>
> Yoshihiro-san
>
> Yoshihiro Shimoda writes:
> >> >> Yoshihiro Shimoda writes:
> >> >> > Sadly, to change the role ("host" and "peripheral") of
On Mon, Mar 27, 2017 at 11:48:12AM +0300, Laurent Pinchart wrote:
> Hi Geert,
>
> Thank you for the patch.
>
> On Friday 24 Mar 2017 14:37:44 Geert Uytterhoeven wrote:
> > Update r8a7795.dtsi so it corresponds to R-Car H3 ES2.0 or later:
> > - The following devices no longer exist on ES2.0,
Yoshihiro-san
Yoshihiro Shimoda writes:
>> >> Yoshihiro Shimoda writes:
>> >> > Sadly, to change the role ("host" and "peripheral") of USB3.0 DRD
>> >> > controller on R-Car Gen3, software has to set the DRD_CON register
>> >>
On Tue, Mar 21, 2017 at 11:14:43PM +0300, Sergei Shtylyov wrote:
> On 03/21/2017 11:08 PM, Sergei Shtylyov wrote:
>
> >Still not cover letter but I think it's better now, so I won't retry...
> >The patches are against Simon Horman's 'renesas.git' repo,
> >'renesas-devel-20170321-v4.11-rc3' tag.
>
Hi Linus,
On Wed, Mar 29, 2017 at 4:30 AM, Linus Walleij wrote:
> On Tue, Mar 28, 2017 at 4:38 PM, wrote:
>>> The fact that historically all the early adopters of pinctrl in device
>>> tree
>>> have these funky custom bindings is unfortunate but
Hi Linus,
On Fri, Mar 24, 2017 at 4:42 PM, Linus Walleij wrote:
> On Fri, Mar 24, 2017 at 4:22 PM, Jacopo Mondi
> wrote:
>
> I assume Geert will queue this driver even if it is outside of sh-pfc?
OK for me, thanks. I was actually wondering
Hi Morimoto-san,
On Wed, Mar 29, 2017 at 4:45 AM, Kuninori Morimoto
wrote:
> Current ALSA SoC Sound Card basically consists of CPU/Codec/Platform
> drivers. If system uses Kernel modules, we can disable these drivers
> by using rmmod command. In such case, we
Hi,
> -Original Message-
> From: Felipe Balbi, Sent: Wednesday, March 29, 2017 2:52 PM
>
> Hi,
>
> Yoshihiro Shimoda writes:
> > Hi Felipe-san,
> >
> >> From: Felipe Balbi, Sent: Tuesday, March 28, 2017 9:06 PM
> >>
> >> Hi,
> >>
> >> Yoshihiro Shimoda
Hi Rob,
On Wed, Mar 29, 2017 at 3:24 AM, Rob Herring wrote:
> On Wed, Mar 22, 2017 at 10:27:49AM -0400, Chris Brandt wrote:
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/rtc/rtc-sh.txt
>> @@ -0,0 +1,29 @@
>> +* Real Time Clock for Renesas SH and ARM SoCs
>> +
>>
70 matches
Mail list logo