Hi Pavel,
Am 28.08.2015 um 09:02 schrieb Pavel Machek :
> Hi!
>
>> we (the developers of the hardware) have proposed an alternative
>> approach to Neil’s implementation - for the same device and solving
>> the same problem (notifying tty open/close and uart activity to the
>> slave device driver
Hi Linus,
Am 12.08.2015 um 01:20 schrieb NeilBrown :
> On Fri, 7 Aug 2015 15:01:47 +0200 Linus Walleij
> wrote:
>
>> Hi Neil,
>>
>> first, this is a *VERY* interesting and much needed patch series,
>> I intend to look closer at it, and if possible test it with some
>> (heh) board file device.
Hi all,
this patch series is our proposal to add hooks so that the driver for a device
connected to an UART can
monitor modem control lines and data activity of the connected chip.
It contains an example for such a device driver which needs such sophisticated
power control: wi2wi,w2sg0004
A rem
Hi Pavel,
Am 06.05.2015 um 11:27 schrieb Pavel Machek :
> On Wed 2015-05-06 07:19:31, Dr. H. Nikolaus Schaller wrote:
>> Hi Peter,
>>
>> Am 05.05.2015 um 21:54 schrieb Peter Hurley :
>>
>>> Hi Neil,
>>>
>>> On 03/18/2015 01:58 AM, Neil
Hi Pavel,
Am 27.04.2015 um 22:35 schrieb Pavel Machek :
> Hi!
>
>>> In my opinion making something a node in / is always the
>>> last resort and in my perspective it has been handled in such a way
>>> so far.
>>
>> But that contradicts some documents I have found and linked. Please
>> show me a
Hi Pavel,
Am 04.04.2015 um 10:16 schrieb Pavel Machek :
> Hi!
>
Please propose your own code doing that so that we can test if it is
better.
>>>
>>> So, how does this look?
>>>
>>> It looks to me like you have cca 0.1 Ohm resistance in your system,
>>
>> This is completely unknown.
Hi,
Am 01.04.2015 um 22:16 schrieb Pavel Machek :
> Hi!
>
>>> As I explained in some other mail, those tables should not be
>>> neccessary at all. They can be computed from li-ion characteristics
>>> and internal resistance, and assumed current during charge and
>>> discharge.
>>
>> I already e
Hi,
Am 01.04.2015 um 18:30 schrieb Rob Herring :
> On Tue, Mar 10, 2015 at 4:27 PM, Marek Belisko wrote:
>> Signed-off-by: Marek Belisko
>> ---
>> .../bindings/power_supply/twl4030_madc_battery.txt | 43
>> ++
>> 1 file changed, 43 insertions(+)
>> create mode 100644
>> Doc
Hi Pavel,
Am 31.03.2015 um 09:26 schrieb Pavel Machek :
> Hi!
>
> + io-channels = <&twl_madc 1>,
> + <&twl_madc 10>,
> + <&twl_madc 12>;
> + io-channel-names = "temp",
> +"ichg",
> +
Am 27.03.2015 um 17:31 schrieb Sebastian Reichel :
> Hi,
>
> On Fri, Mar 27, 2015 at 10:22:11AM +0100, Dr. H. Nikolaus Schaller wrote:
>>> Coming back at my sentence: I asked about a non-trivial, non-bus
>>> connected HW, which has a DT binding.
>>
>>
Hi,
Am 26.03.2015 um 19:08 schrieb Sebastian Reichel :
> Hi,
>
> On Wed, Mar 25, 2015 at 05:44:42PM +0100, Dr. H. Nikolaus Schaller wrote:
>> Am 25.03.2015 um 16:21 schrieb Sebastian Reichel :
>>> On Wed, Mar 25, 2015 at 08:59:14AM +0100, Dr. H. Nikolaus Schaller wrote:
Hi,
Am 26.03.2015 um 06:56 schrieb Pavel Machek :
> Hi!
>
> Main reason is, that I would need to go
> through the UART to “communicate" with the w2sg0004.
You can always "communicate” through the UART. Even without DT. As long as
the connected chip is powered up by any me
Am 25.03.2015 um 21:53 schrieb Pavel Machek :
> Hi!
>
AFAIK the chip simply starts to emit NMEA records if powered on.
There is no command going over the serial interface to address it
or control it.
>>>
>>> Right, since GPS basically doesn't need any configuration/control.
>>> T
Hi,
Am 25.03.2015 um 21:42 schrieb Pavel Machek :
> Hi!
>
>>> In the case of our GPS, it receives control over the serial connection from
>>> the UART,
>>
>> Ahem - does it?
>>
>> AFAIK the chip simply starts to emit NMEA records if powered on. There is no
>> command going over the serial inte
Hi,
Am 25.03.2015 um 16:21 schrieb Sebastian Reichel :
> Hi,
>
> On Wed, Mar 25, 2015 at 08:59:14AM +0100, Dr. H. Nikolaus Schaller wrote:
>> Am 25.03.2015 um 02:45 schrieb Sebastian Reichel :
>>> On Tue, Mar 24, 2015 at 06:58:15PM +0100, Dr. H. Nikolaus Schaller wrote:
Hi,
Am 25.03.2015 um 02:45 schrieb Sebastian Reichel :
> Hi,
>
> On Tue, Mar 24, 2015 at 06:58:15PM +0100, Dr. H. Nikolaus Schaller wrote:
>> So you propose that the parent->child relationship is “control”? I.e. some
>> channel which allows to address some bus client (
Hi,
Am 21.03.2015 um 00:31 schrieb NeilBrown :
> On Fri, 20 Mar 2015 10:34:18 +0100 "Dr. H. Nikolaus Schaller"
> wrote:
>
>>
>> Am 20.03.2015 um 09:54 schrieb NeilBrown :
>
>>> There needs to be one device-node for each device, and that device-node
Hi,
Am 20.03.2015 um 14:08 schrieb Sebastian Reichel :
> Hi,
>
> On Fri, Mar 20, 2015 at 09:54:21AM +0100, Dr. H. Nikolaus Schaller wrote:
>> [...]
>> And we do not write a driver for the w2sg0004 but the regulator inside that
>> chip.
>
> DT describes the har
Am 20.03.2015 um 09:54 schrieb NeilBrown :
> On Fri, 20 Mar 2015 08:54:38 +0100 "Dr. H. Nikolaus Schaller"
> wrote:
>
>>
>> Am 18.03.2015 um 06:58 schrieb NeilBrown :
>>
>>> If a platform has a particular device permanently attached to a UART,
&g
Hi,
Am 20.03.2015 um 09:43 schrieb NeilBrown :
> On Fri, 20 Mar 2015 08:54:35 +0100 "Dr. H. Nikolaus Schaller"
> wrote:
>
>> Hi Neil,
>>
>> Am 18.03.2015 um 06:58 schrieb NeilBrown :
>>
>>> Hi again,
>>> here is version 3 of suppo
Hi Neil,
Am 18.03.2015 um 06:58 schrieb NeilBrown :
> Hi again,
> here is version 3 of support for tty-slaves.
>
> This version introduces a new bus-type for tty-slaves,
Hm. I am still not convinced that a tty is a „bus“ and
that this is a solution for a wide-spread problem.
> and causes
> a
Am 18.03.2015 um 06:58 schrieb NeilBrown :
> If a platform has a particular device permanently attached to a UART,
> there may be out-of-band signaling necessary to power the device
> on and off.
>
> This driver controls that signalling for a number of different devices.
> It can
> - enable/disa
Hi Pavel,
Am 17.03.2015 um 14:59 schrieb Pavel Machek :
> Hi!
>
>>> to introduce coefficients for temperature and discharge rate?
>> What do you mean? Nothing like that is used in current driver why do
>> we need to add it?
>
> Well, conversion between Li-ion's voltage and s
Hi Pavel,
Am 17.03.2015 um 11:37 schrieb Pavel Machek :
> Hi!
>
> to introduce coefficients for temperature and discharge rate?
What do you mean? Nothing like that is used in current driver why do
we need to add it?
>>>
>>> Well, conversion between Li-ion's voltage and state of ch
Am 17.03.2015 um 09:47 schrieb Pavel Machek :
> Hi!
>
diff --git
a/Documentation/devicetree/bindings/power_supply/twl4030_madc_battery.txt
b/Documentation/devicetree/bindings/power_supply/twl4030_madc_battery.txt
new file mode 100644
index 000..bb3580c
--- /de
Am 17.03.2015 um 09:48 schrieb Pavel Machek :
>>
>> Temperature calibration should have already been done in the underlaying
>> twl4030 iio driver.
>>
>> Discharge rate is the real current flow reported in uA. Also
>> reported by iio.
>
> Ack, but there's rather severe temperature dependency
Hi,
Am 17.03.2015 um 09:47 schrieb Pavel Machek :
> Hi!
>
diff --git
a/Documentation/devicetree/bindings/power_supply/twl4030_madc_battery.txt
b/Documentation/devicetree/bindings/power_supply/twl4030_madc_battery.txt
new file mode 100644
index 000..bb3580c
---
Am 16.03.2015 um 22:20 schrieb Belisko Marek :
> On Mon, Mar 16, 2015 at 10:05 PM, Pavel Machek wrote:
>> On Wed 2015-02-04 23:14:32, Marek Belisko wrote:
>>> Signed-off-by: Marek Belisko
>>> ---
>>> .../bindings/power_supply/twl4030_madc_battery.txt | 43
>>> ++
>>> 1 file
Am 11.03.2015 um 17:44 schrieb Tony Lindgren :
> * Dr. H. Nikolaus Schaller [150311 09:17]:
>> Hi,
>>
>> Am 11.03.2015 um 16:24 schrieb Tony Lindgren :
>>
>>> Hi,
>>>
>>> * Marek Belisko [150310 14:28]:
>>>> Sig
Hi,
Am 11.03.2015 um 16:24 schrieb Tony Lindgren :
> Hi,
>
> * Marek Belisko [150310 14:28]:
>> Signed-off-by: Marek Belisko
>> ---
>> .../bindings/power_supply/twl4030_madc_battery.txt | 43
>> ++
>> 1 file changed, 43 insertions(+)
>> create mode 100644
>> Documentation/
Am 12.02.2015 um 18:47 schrieb Grazvydas Ignotas :
> On Thu, Feb 12, 2015 at 3:03 PM, Marek Belisko wrote:
>> From: "H. Nikolaus Schaller"
>>
>> This device tree allows to boot, supports the panel,
>> framebuffer, touch screen, as well as some more peripherals.
>> Since there is a OMAP3530 bas
Am 12.02.2015 um 17:03 schrieb Tony Lindgren :
> Hi,
>
> Few comments below.
>
> * Marek Belisko [150212 05:07]:
>> +
>> +&omap3_pmx_core {
>> +
>> +mmc1_pins: pinmux_mmc1_pins {
>> +pinctrl-single,pins = <
>> +OMAP3_CORE1_IOPAD(0x2144, PIN_INPUT_PULLUP | MU
Am 15.01.2015 um 19:16 schrieb Dmitry Torokhov :
> On Thu, Jan 15, 2015 at 05:14:38PM +0100, Dr. H. Nikolaus Schaller wrote:
>>
>> Am 15.01.2015 um 15:38 schrieb Sebastian Reichel :
>>
>>> Hi,
>>>
>>> On Thu, Jan 15, 2015 at 08:36:44AM +0100,
Am 15.01.2015 um 15:38 schrieb Sebastian Reichel :
> Hi,
>
> On Thu, Jan 15, 2015 at 08:36:44AM +0100, Dr. H. Nikolaus Schaller wrote:
>>> 1. Perform conversion in input core rather than individual drivers. I
>>> think we should allocate a new bitmaps for some trans
Hi,
Am 15.01.2015 um 15:38 schrieb Sebastian Reichel :
> Hi,
>
> On Thu, Jan 15, 2015 at 08:36:44AM +0100, Dr. H. Nikolaus Schaller wrote:
>>> 1. Perform conversion in input core rather than individual drivers. I
>>> think we should allocate a new bitmaps for so
Hi,
Am 15.01.2015 um 01:59 schrieb Dmitry Torokhov :
> On Sat, Jan 10, 2015 at 03:15:39PM +0100, Belisko Marek wrote:
>> Ping for input maintainer. DT changes was acked. Thanks.
>>
>> On Tue, Sep 30, 2014 at 10:17 PM, Marek Belisko wrote:
>>> This patch adds new parameters that allow to address
Hi Neil,
Am 02.12.2014 um 02:55 schrieb NeilBrown :
> On Fri, 28 Nov 2014 12:56:33 +0100 Ulf Hansson wrote:
>
>> On 8 November 2014 at 01:14, NeilBrown wrote:
>>> If the regulator supplying an SDIO device is shared
>>> with another device, the turning the regulator 'on' and 'off'
>>> will not
Am 13.11.2014 um 17:41 schrieb Tomi Valkeinen :
> On 13/11/14 18:25, Dr. H. Nikolaus Schaller wrote:
>> Hi,
>>
>> Am 13.11.2014 um 12:51 schrieb Tomi Valkeinen :
>>
>>> On 13/11/14 00:10, Marek Belisko wrote:
>>>> opa362 is amplifier for video an
Hi,
Am 13.11.2014 um 12:51 schrieb Tomi Valkeinen :
> On 13/11/14 00:10, Marek Belisko wrote:
>> opa362 is amplifier for video and can be connected to the tvout pads
>> of the OMAP3. It has one gpio control for enable/disable of the output
>> (high impedance).
>>
>> Signed-off-by: H. Nikolaus Sc
Am 10.11.2014 um 00:25 schrieb NeilBrown :
> On Sat, 8 Nov 2014 09:26:22 + Mark Brown wrote:
>
>> On Sat, Nov 08, 2014 at 11:38:03AM +1100, NeilBrown wrote:
>>
>>> If voice port on twl4030 is not connected to a McBSP (or similar)
>>> then we cannot configure the format the way we normally
ping (questions for directions at the end of the mail).
Am 24.10.2014 um 11:32 schrieb Dr. H. Nikolaus Schaller :
>
> Am 20.10.2014 um 19:26 schrieb Dr. H. Nikolaus Schaller :
>
>> Hi,
>>
>> Am 20.10.2014 um 11:35 schrieb Mark Rutland :
>>
>>> Hi,
&
Am 20.10.2014 um 19:26 schrieb Dr. H. Nikolaus Schaller :
> Hi,
>
> Am 20.10.2014 um 11:35 schrieb Mark Rutland :
>
>> Hi,
>>
>> On Fri, Oct 17, 2014 at 08:55:50PM +0100, Dr. H. Nikolaus Schaller wrote:
>>>
>>> Am 17.10.2014 um 13:00 schrieb
Hi,
Am 21.10.2014 um 12:49 schrieb Pavel Machek :
> Hi!
>
>> --- a/drivers/misc/Kconfig
>> +++ b/drivers/misc/Kconfig
>> @@ -515,6 +515,16 @@ config VEXPRESS_SYSCFG
>>bus. System Configuration interface is one of the possible means
>>of generating transactions on this bus.
>>
>>
Hi,
Am 20.10.2014 um 11:35 schrieb Mark Rutland :
> Hi,
>
> On Fri, Oct 17, 2014 at 08:55:50PM +0100, Dr. H. Nikolaus Schaller wrote:
>>
>> Am 17.10.2014 um 13:00 schrieb Mark Rutland :
>>
>>> On Fri, Oct 17, 2014 at 11:16:42AM +0100, Dr. H. Nikolaus Scha
Hi,
Am 19.10.2014 um 21:51 schrieb Arnd Bergmann :
> On Thursday 16 October 2014 22:26:22 Marek Belisko wrote:
>> This is a driver for the Wi2Wi GPS modules connected through an UART.
>> The tricky part is that the module is turned on or off by an impulse
>> on the control line - but it is only p
Am 17.10.2014 um 13:00 schrieb Mark Rutland :
> On Fri, Oct 17, 2014 at 11:16:42AM +0100, Dr. H. Nikolaus Schaller wrote:
>>
>> Am 17.10.2014 um 11:37 schrieb Mark Rutland :
>>
>>> On Thu, Oct 16, 2014 at 09:26:23PM +0100, Marek Belisko wrote:
>>&g
Am 17.10.2014 um 11:37 schrieb Mark Rutland :
> On Thu, Oct 16, 2014 at 09:26:23PM +0100, Marek Belisko wrote:
>> Signed-off-by: H. Nikolaus Schaller
>> Signed-off-by: Marek Belisko
>> ---
>> .../devicetree/bindings/misc/wi2wi,w2sg0004.txt| 44
>> ++
>> 1 file changed, 4
Hi,
Am 29.07.2014 um 14:41 schrieb Tony Lindgren:
> * Dr. H. Nikolaus Schaller [140728 13:45]:
>>
>> Yes,
>> the boot loader either loads gta04a3.dtb gta04.dtb or gta05.dtb
>> depending on board revision.
>>
>> Therefore we have multiple devic
Hi,
Am 28.07.2014 um 22:12 schrieb Michael Trimarchi:
> Hi
>
> Il 28/lug/2014 22:06 "Belisko Marek" ha scritto:
> >
> > On Mon, Jul 28, 2014 at 10:04 PM, Michael Trimarchi
> > wrote:
> > > Hi
> > >
> > > Il 28/lug/2014 22:02 "Belisko Marek" ha scritto:
> > >
> > >
> > >>
> > >> Hi Michael,
>
Hi all,
Am 18.07.2014 um 11:21 schrieb Javier Martinez Canillas:
> Hello Marek and Dr. H. Nikolaus,
>
> On Fri, Jul 18, 2014 at 8:55 AM, Joachim Eastwood wrote:
>> On 16 July 2014 09:17, Dr. H. Nikolaus Schaller wrote:
>>> Am 15.07.2014 um 14:45 schrieb Joachim East
Hi Joachim,
is there some policy for only having nodes for existing drivers in DT files?
If I understand the device tree concept correctly, it should not describe
drivers
(and hence nothing about the state of them being mainlined), but it should
statically
describe the given hardware in a way th
Am 10.02.2014 um 09:27 schrieb Johannes Berg:
> On Fri, 2014-02-07 at 20:48 +0100, Marek Belisko wrote:
>
>> +#define RFKILL_TYPE_ALL (0)
>> +#define RFKILL_TYPE_WLAN(1)
>> +#define RFKILL_TYPE_BLUETOOTH (2)
>> +#define RFKILL_TYPE_UWB (3)
>> +#define RFKILL_TYPE
Am 15.11.2013 um 14:58 schrieb Arnd Bergmann:
> On Thursday 14 November 2013, Marek Belisko wrote:
>> DT bindings contains more parameters to set so add them to platform data also
>> to have possibility to use on arch where DT isn't available yet.
>>
>> Signed-off-by: Marek Belisko
>
> Can you
53 matches
Mail list logo