On Thu, Apr 17, 2014 at 09:43:40AM +0200, Arend van Spriel wrote:
> + linux-ser...@vger.kernel.org
>
> On 16/04/14 15:09, Hans de Goede wrote:
> >Hi,
> >
> >On 04/16/2014 12:39 PM, Chen-Yu Tsai wrote:
> >>Hi,
> >>
> >>On Wed, Apr 16, 2014 at 5:44 PM, Maxime Ripard
> >> wrote:
> >>>Hi,
> >>>
> >>>P
On Wed, Apr 16, 2014 at 06:39:28PM +0800, Chen-Yu Tsai wrote:
> Hi,
>
> On Wed, Apr 16, 2014 at 5:44 PM, Maxime Ripard
> wrote:
> > Hi,
> >
> > Please try to keep me in CC, even though the ML doesn't make it easy..
>
> Sorry about that.
>
> > On Wed, Apr 16, 2014 at 12:06:59AM +0800, Chen-Yu Ts
Hi,
On 04/16/2014 11:44 AM, Maxime Ripard wrote:
> Hi,
>
> Please try to keep me in CC, even though the ML doesn't make it easy..
>
> On Wed, Apr 16, 2014 at 12:06:59AM +0800, Chen-Yu Tsai wrote:
@@ -139,4 +152,16 @@
reg_usb2_vbus: usb2-vbus {
status = "okay";
Hi,
On Wed, Apr 16, 2014 at 5:44 PM, Maxime Ripard
wrote:
> Hi,
>
> Please try to keep me in CC, even though the ML doesn't make it easy..
Sorry about that.
> On Wed, Apr 16, 2014 at 12:06:59AM +0800, Chen-Yu Tsai wrote:
>> >> @@ -139,4 +152,16 @@
>> >> reg_usb2_vbus: usb2-vbus {
>> >>
Hi,
Please try to keep me in CC, even though the ML doesn't make it easy..
On Wed, Apr 16, 2014 at 12:06:59AM +0800, Chen-Yu Tsai wrote:
> >> @@ -139,4 +152,16 @@
> >> reg_usb2_vbus: usb2-vbus {
> >> status = "okay";
> >> };
> >> +
> >> + rfkill_bt {
> >> +
> For our use case here, which is a bluetooth chip connected on the UART,
> there is no in kernel representation or driver to tie them to. Same goes
> for UART based GPS chips. They just so happen to require toggling a GPIO,
> and maybe enabling a specific clock, to get it running. Afterwards,
> ac
On Tue, Apr 15, 2014 at 10:42 PM, Maxime Ripard
wrote:
> On Tue, Apr 15, 2014 at 02:41:41PM +0800, Chen-Yu Tsai wrote:
>> The CubieTruck has an AMPAK AP6210 WiFi+Bluetooth module. The Bluetooth
>> part is a BCM20710 device connected to UART2 in the A20 SoC.
>>
>> The IC requires a 32.768 KHz low p
