Hi,
> From: Yoshihiro Shimoda
> Sent: Wednesday, May 24, 2017 9:04 PM
>
> The USB 3.0 PHY modules of R-Car Gen3 SoCs have:
> - Spread spectrum clock (ssc).
> - Using USB 2.0 EXTAL clock instead of USB 3.0 clock.
> - Enabling VBUS detection for usb3.0 peripheral.
>
> So, this driver supports
Hi Wolfram,
On Tue, Jun 21, 2016 at 3:11 PM, Geert Uytterhoeven
wrote:
> On Mon, Jun 20, 2016 at 8:40 AM, Wolfram Sang wrote:
>> On group configuration, bail out if setting one of the individual pins
>> fails. We don't need to roll-back, the pinctrl
Hi Geert,
Thank you for the patch.
On Wednesday 24 May 2017 13:43:34 Geert Uytterhoeven wrote:
> Configuration of the lcd0 pinmux group and GPIO hog for the external
> GPIO mux are done using a single device node, causing the "output-high"
> property to be applied to both. This will fail for
Configuration of the lcd0 pinmux group and GPIO hog for the external
GPIO mux are done using a single device node, causing the "output-high"
property to be applied to both. This will fail for the pinmux group,
but doesn't cause any harm, as the failure is ignored silently.
However, after
The USB 3.0 PHY modules of R-Car Gen3 SoCs have:
- Spread spectrum clock (ssc).
- Using USB 2.0 EXTAL clock instead of USB 3.0 clock.
- Enabling VBUS detection for usb3.0 peripheral.
So, this driver supports these features.
Signed-off-by: Yoshihiro Shimoda
The USB 3.0 PHY modules of R-Car Gen3 SoCs have:
- Spread spectrum clock (ssc).
- Using USB 2.0 EXTAL clock instead of USB 3.0 clock.
- Enabling VBUS detection for usb3.0 peripheral.
So, this driver supports these features.
Signed-off-by: Yoshihiro Shimoda
Hi Geert,
> This is caused by the "output-high" property for the GPIO hog.
> Due to both lcd0 pinmux and GPIO hog being part of the same device node,
> "output-high" is also applied to the lcd0 pins, which fails.
>
> RFC fix in "[PATCH/RFC] ARM: dts: armadillo800eva: Split LCD mux and gpio"
>
Hi Wolfram,
On Wed, May 24, 2017 at 2:21 PM, Wolfram Sang wrote:
>> This is caused by the "output-high" property for the GPIO hog.
>> Due to both lcd0 pinmux and GPIO hog being part of the same device node,
>> "output-high" is also applied to the lcd0 pins, which fails.
>>
>>
Hi Shimoda-san,
On Wed, May 24, 2017 at 2:17 PM, Yoshihiro Shimoda
wrote:
> The USB 3.0 PHY modules of R-Car Gen3 SoCs have:
> - Spread spectrum clock (ssc).
> - Using USB 2.0 EXTAL clock instead of USB 3.0 clock.
> - Enabling VBUS detection for usb3.0
Hi Niklas,
On Wed, May 24, 2017 at 02:09:06AM +0200, Niklas Söderlund wrote:
> From: Niklas Söderlund
>
> The optional operation can be used by entities to report how it maps its
> fwnode endpoints to media pad numbers. This is useful for devices which
>
Hi Niklas,
On Wed, May 24, 2017 at 02:09:07AM +0200, Niklas Söderlund wrote:
> From: Niklas Söderlund
>
> This is a wrapper around the media entity pad_from_fwnode operation.
>
> Signed-off-by: Niklas Söderlund
>
On Wed, May 24, 2017 at 02:07:26AM +0200, Niklas Söderlund wrote:
> From: Niklas Söderlund
>
> Add a check for v4l2_dev to v4l2_async_notifier_register() as to fail as
> early as possible since this will fail later in v4l2_async_test_notify().
>
>
Hi Sakari,
Thanks for your feedback.
On 2017-05-24 16:27:42 +0300, Sakari Ailus wrote:
> Hi Niklas,
>
> On Wed, May 24, 2017 at 02:09:07AM +0200, Niklas Söderlund wrote:
> > From: Niklas Söderlund
> >
> > This is a wrapper around the media entity
Hi Sakari,
Thanks for your feedback.
On 2017-05-24 16:21:37 +0300, Sakari Ailus wrote:
> Hi Niklas,
>
> On Wed, May 24, 2017 at 02:09:06AM +0200, Niklas Söderlund wrote:
> > From: Niklas Söderlund
> >
> > The optional operation can be used by entities to
Hi Laurent,
On Wed, May 24, 2017 at 2:57 PM, Laurent Pinchart
wrote:
> On Wednesday 24 May 2017 13:43:34 Geert Uytterhoeven wrote:
>> Configuration of the lcd0 pinmux group and GPIO hog for the external
>> GPIO mux are done using a single device node, causing
The patch
ASoC: rsnd: SSI PIO adjust to 24bit mode
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
The patch
ASoC: hdmi-codec: remove multi detection support
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
On Thu, May 18, 2017 at 01:40:47AM +, Kuninori Morimoto wrote:
> ALSA SoC needs to know connected DAI ID for probing.
> It is not a big problem if device/driver was only for sound,
> but getting DAI ID will be difficult if device includes both
> Video/Sound, like HDMI.
As far as I understand
The patch
ASoC: hdmi-codec: add .get_dai_id support
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
The patch
ASoC: simple-card-utils: support snd_soc_get_dai_id()
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
The patch
ASoC: add snd_soc_get_dai_id() function
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
Hi Mark
Cc: DRM maintainer
> > ALSA SoC needs to know connected DAI ID for probing.
> > It is not a big problem if device/driver was only for sound,
> > but getting DAI ID will be difficult if device includes both
> > Video/Sound, like HDMI.
>
> As far as I understand what's going on with the
Hi Geert
Thank you for your check
> @@ -12,6 +12,9 @@
> x21-clock003300
> 0 0
> x12 1124576000
> 0 0
> clk_multiplier11
Hello Simon,
On Tue, May 23, 2017 at 09:25:40PM +0200, Geert Uytterhoeven wrote:
> On Tue, May 23, 2017 at 9:20 PM, Jacopo Mondi
> wrote:
> > Add device tree source for Renesas GR-Peach board.
> > GR-Peach is an RZ/A1H based board with 10MB of on-chip SRAM and 8MB
> >
Hi Morimoto-san,
On Wed, May 24, 2017 at 4:16 AM, Kuninori Morimoto
wrote:
> From: Kuninori Morimoto
>
> Current rcar_sound only has 11289600 (= for 44.1kHz) clock-frequency,
> but it needs 12288000 for 48kHz too.
> Otherwise,
Hello!
On 5/24/2017 3:15 AM, Niklas Söderlund wrote:
From: Niklas Söderlund
If the requested pixelformat is not supported fallback to the default
format, do not revert the entire format.
Signed-off-by: Niklas Söderlund
26 matches
Mail list logo